claude-toolkit

Everything is under **`acli jira workitem`** (there is no `issue` subcommand).

Quick reference for all available slash commands.

You are orchestrating the full development lifecycle for one or more Jira tickets: workspace setup, team handoff, and cleanup.

Runs Playwright tests across worktrees one at a time in a real browser window. Next worktree starts only when the previous finishes. Prints a pass/fail summary at the end.

Run passing E2E tests in headed or UI mode. Probes headlessly first to find which tests currently fail, then skips them so you only see green tests. Vite proxy noise (ECONNREFUSED) is filtered from output automatically.

You are reviewing patterns detected from tool usage analysis. Your goal is to identify valuable patterns and promote them to the right destination.

You are setting up an infrastructure workspace from a Jira ticket. This is like `/workspace-launch` but tailored for Terraform/infra work.

Analyze the structured review findings in `pr-learnings.json` (collected by `/scrape-pr-history`) to surface recurring patterns, identify what reviewers (human and AI) catch most often, and propose convention improvements.

ultrathink — this task requires deep analysis of existing code structures to produce concrete, actionable examples for ticket refinement.

ultrathink — this task requires deep reasoning to correctly classify learnings and route them to the right destination without duplicates.

Read `~/.claude/dtf-config.json` if it exists. Use:

Manage pre-configured GitHub reviewers per category. These are auto-assigned when Dream Team PRs are marked ready for human review.

Extract structured learnings from AI reviewer comments on Jira tickets. Analyzes how the AI reviewer pushes back, what it catches, what it misses, and how the team responds — to improve both `/ticket-refine` and the AI reviewer itself.

Extract review findings from merged GitHub PRs using parallel Haiku agents and store them as structured learnings.

Sync all Claude configuration files (commands, scripts, skills, settings) to the `~/Privat/shared-claude-files` git repo and push to GitHub.

Show cumulative service-e, achievements, and shoutouts for the Dream Team agents.

ultrathink — this task requires deep analysis of existing code structures to produce concrete, actionable examples for ticket implementation.

ultrathink — this task requires deep critical analysis of ticket quality, domain implications, UX flows, and consistency to produce actionable pushback.

ultrathink — this task requires reasoning across multiple tickets to assess relative complexity and assign fair story points.

Tear down a workspace that was created by `/workspace-launch`.

You are setting up a new development workspace from a Jira ticket.

Analyzes codebases and produces architecture plans, conventions summaries, and implementation strategies for Repo monorepo tickets.

Implements .NET backend features, API endpoints, EF Core migrations, and service logic for Repo microservices.

Handles data mapping, database queries, EF Core migrations, report generation, and data pipelines for Repo services.

Performs data exploration, SQL queries, notebook analysis, and visualization for Repo business insights.

Handles data mapping, database queries, EF Core migrations, report generation, and data pipelines for Repo services.

Generates business intelligence reports, dashboards specs, and data-driven narratives from analytical findings.

Designs and builds data pipelines — dbt models, ETL workflows, incremental processing, and data quality checks.

Designs component interfaces, design system tokens, and visual specifications for frontend implementation.

Conducts UX analysis, usability heuristics evaluation, user flow mapping, and accessibility review.

Designs REST API contracts, OpenAPI specs, endpoint naming, versioning, and request/response schemas.

Analyzes codebases and produces architecture plans, conventions summaries, and implementation strategies for Repo monorepo tickets.

Implements .NET backend features, API endpoints, EF Core migrations, and service logic for Repo microservices.

Implements React/TypeScript frontend features, components, pages, RTK Query integration, and Tailwind styling for Repo web app.

Plans safe database migrations, data transformations, and schema changes with rollback strategies.

Analyzes application performance — database queries, API response times, bundle sizes, and rendering bottlenecks.

Reviews code changes for convention violations, bugs, security issues, missing i18n, and broken patterns in Repo PRs.

Implements React/TypeScript frontend features, components, pages, RTK Query integration, and Tailwind styling for Repo web app.

Validates implementations work correctly via API testing, type checks, and consolidated test reports for Repo services.

Handles EF Core migrations, Docker Compose configuration, database schema issues, and service startup for Repo services.

Designs and maintains CI/CD pipelines — GitHub Actions workflows, deployment strategies, and build optimization.

Manages Terraform infrastructure, AWS resources, CI/CD pipelines, monitoring, and security hardening for Repo.

Audits infrastructure and application security — ServiceC policies, secrets management, vulnerability scanning, and compliance.

Creates blog posts, case studies, whitepapers, and thought leadership content with SEO optimization.

Creates marketing content, campaign briefs, SEO optimization, and content calendars for Repo marketing team.

Creates sales proposals, customer presentations, data-driven pitch materials, and competitive analysis for Repo sales team.

Plans social media content, LinkedIn posts, engagement strategies, and campaign calendars.

Handles customer onboarding, integration mappings, Fuse configurations, and ITSM support tickets for Repo operations.

Investigates support tickets, traces issues through logs and code, and recommends fixes or workarounds.

Reviews code changes for convention violations, bugs, security issues, missing i18n, and broken patterns in Repo PRs.

Analyzes requirements, refines Jira tickets, plans sprints, and bridges business needs with technical implementation for Repo.

Breaks down feature requests into detailed requirements with acceptance criteria, edge cases, and dependency mapping.

Prioritizes backlog items by business value, technical risk, and dependencies. Recommends sprint scope.

Dedicated OWASP-aligned security scanner for Repo PRs — injection, auth/authz, data exposure, path traversal, secrets, and insecure defaults.

Produces comprehensive PR summaries with overview, user flow, change breakdown, and how-to-test instructions for Repo PRs.

Tests API endpoints — request validation, response schemas, error handling, authentication, and performance.

Benchmarks application performance — load testing, response times, database query analysis, and bottleneck identification.

Plans and executes QA testing — E2E with Playwright, test case design, regression testing, and bug reporting for Repo.

Performs UAT testing in staging environments, writes structured bug reports, validates acceptance criteria, and documents permission/business rules for Repo.

Writes Playwright e2e tests that generate reproducible screenshots for visual verification of UI changes in Repo.

AWS infrastructure performance and cost optimization — CloudWatch, auto-scaling, RDS tuning, S3, caching, cost controls

Set up AWS CLI SSO for Repo and sync TranslationService translations to S3

Backend coding conventions for the Repo monorepo

Backend/.NET performance optimization — EF Core queries, API response times, caching, database tuning, memory profiling

Opt-in code review on your changed files — refactoring nudges with pros/cons, DTO insights with mermaid diagrams for PR descriptions

Marketing content workflows — blog posts, campaigns, SEO, email marketing for Repo

Switch between dev, review, and research mindsets — changes priorities, tool preferences, and output style

Data analysis workflows — SQL queries, Jupyter notebooks, visualization, and business intelligence for Repo

Data engineering conventions for the Repo monorepo

Generate multiple radically different interface designs for a module using parallel sub-agents. Use when designing an API, service contract, hook, or component interface — or when someone mentions "design it twice".

Frontend coding conventions for the Repo monorepo

Frontend performance optimization — Core Web Vitals, bundle analysis, React rendering, image optimization, caching strategies

Design exploration through relentless interviewing — flesh out ideas before writing a single line of code or ticket

Audit a service or module for agent-friendliness — identify confusing boundaries, tightly coupled code, and shallow modules that make AI implementation harder and less reliable

Infrastructure and DevOps conventions — Terraform, AWS, CI/CD, monitoring, and security for Repo

Review and clean up memory files to keep context costs low — triggered during cleanup, compact, or session end

Creates syntactically correct mermaid diagrams (flowchart, sequenceDiagram, classDiagram, stateDiagram, erDiagram, gantt, mindmap) following official specifications. Prevents common errors like special characters in labels, subgraph syntax, note misuse, and reserved words. Use when creating or editing mermaid diagrams in documentation or design files.

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

Product Owner workflows — ticket refinement, sprint planning, requirements analysis, impact assessment for Repo

Sales presentation and proposal workflows — customer pitches, ROI models, competitive analysis for Repo

Create a detailed refactor plan with tiny commits via user interview, then file it as a Jira ticket. Use when planning a refactor, creating a refactoring RFC, or breaking a refactor into safe incremental steps.

Proactive context management — suggests /compact at logical breakpoints to maintain quality in long sessions

Test-driven development loop — red-green-refactor with interface confirmation before writing any implementation

QA testing workflows — test planning, E2E with Playwright, regression testing, bug reporting for Repo

Triage a bug by exploring the codebase to find root cause, then create a Jira ticket with a TDD-based fix plan. Use when user reports a bug, mentions "triage", or wants to investigate and plan a fix.

UAT testing workflows — acceptance criteria validation, structured bug reporting, permission testing, and business rule verification for Repo

Write code, verify it visually in browser or iOS simulator, and iterate based on visual feedback until implementation matches expectations.