Commands reference¶

Every slash command available in this workspace, grouped by role. Invoke a command by typing /<name> in the Claude Code chat. Descriptions are the authoritative one-liners from each command definition in .claude/commands/.

Pipeline lifecycle¶

These drive a task from idea to merged change, in order.

Command	What it does
`/create-task <description>`	Create an AI-tracked AISD ticket (or an Epic + child tasks). Decides the task shape with you, iterates the description in the terminal, then creates it in Jira. First approval gate.
`/start-task <KEY>`	Draft a spec for an existing AISD ticket and iterate it with you in the terminal before attaching it to Jira. Creates the working branch. Second approval gate.
`/approve-spec <KEY>`	Approve the spec and run the implementation through three in-terminal gates (code diff, test results, code review) before opening the PR. Branches from the repo default; opens the per-task PR to the integration branch (`stage`).
`/approve-pr <KEY>`	Move a ticket out of Human PR Review: verify a human approved the PR on GitHub (hard gate), merge it, then transition the ticket forward (`Stage QA` for stage repos, `Monitoring` for master-only / prd-only repos). The human counterpart to `/approve-spec`.
`/release <version>`	Open the release rollup PR for a Jira release: verify the 10-task readiness, cut a `release/<version>` branch from `stage`, open the PR to `master`, and link it on every task in the release.

Pipeline control and recovery¶

Command	What it does
`/sync-tasks [filter]`	Reconcile AISD ticket statuses against GitHub PR state + Jira comment sentinels, then move each ticket to its correct state (forward-only, behind a confirm gate).
`/rewind <KEY>`	Rewind an AISD ticket to a prior pipeline step. Preserves the prior artifact as Jira history, posts an audit comment, and re-enters the canonical gate loop for that step.
`/revert <PR>`	Revert a merged PR from stage or prod by opening a revert PR (`git revert` of the merge commit) -- never force-pushes. Posts a Jira audit sentinel and suggests the rework transition.
`/review-task <KEY>`	Read-only status view of a task's pipeline stage and local artifacts. Never prints file contents -- opens artifacts in PyCharm on request.
`/finalize-task <KEY>`	Finalize a task: refresh its artifacts, then (behind a Confirm gate) upload the folder to S3 and delete it locally.

Jira helpers¶

Thin wrappers over hq.jira.cli for day-to-day ticket work.

Command	What it does
`/get-task <KEY>`	Fetch a Jira issue by key (e.g. `/get-task AISD-1`).
`/list-tasks [filter]`	List AISD tickets matching a JQL filter (defaults to active work assigned to the current user).
`/comment-task <KEY> <body>`	Add a comment to a Jira issue. Also `/comment-task AISD-N --file <path>`.
`/update-task <KEY> <json-fields>`	Update Jira issue fields. `/update-task AISD-N <json-fields>`.
`/transition-task <KEY> "<status>"`	Move a Jira issue to a target status (e.g. `/transition-task AISD-1 "In Review"`).
`/close-task <KEY>`	Close a Jira issue (transitions to AI Done by default for AISD tickets).
`/attach-spec <KEY> <file>`	Upload a spec markdown file as an attachment on a Jira issue.
`/create-sprint`	Create a new sprint on a Jira Software board.
`/list-sprints`	List sprints on a Jira Software board.

Deploy and health¶

Command	What it does
`/check-deploy <KEY\\|repo> [stage\\|prd]`	Verify a repo's environment deploy across multiple aspects -- CodePipeline `Succeeded` plus a per-aspect probe (endpoint / nginx / docker / api / task) reported independently. Backed by the `hq.deploy` registry; run at Stage QA and in prod Monitoring.
`/check-health [target]`	Deploy-health dashboard: multi-aspect health for ALL targets (no args) or one target (with an arg), across every configured environment. Read-only; backed by `hq.deploy health`.

Dormant¶

Command	Status
`/start`	DORMANT (render UI). Opens the render UI as a pure chat with the agent. Not part of the active terminal-only flow.

Hard rules the commands enforce

Never merge or advance a ticket without a human GitHub approval -- only /approve-pr merges, and it hard-blocks on that approval.
Forward-only status changes -- /sync-tasks surfaces regressions as flags rather than moving tickets backward.
Never auto-assign a fixVersion or auto-set prod stages -- those are the user's call.