valasubramanian-kr

update-jira

Update JIRA issue status and add PR link comment after push

branch

Create development branch with standardized naming convention (dcppay-<number>-<title>). Must be run after /plan (approved plan recommended).

checkout-jira

Switch between JIRA issues by checking out workflow artifacts from Claude home directory to the project directory. Takes JIRA key or number as argument.

Web & Frontend Listed

citrus-migrate

Migrate a single React component from vanilla/legacy UI to Citrus design system, following established patterns and maintaining existing functionality.

code

Execute the implementation plan and write code following project-specific patterns. Must be run after /branch. Supports re-running after plan updates.

explore

Gather comprehensive context from external sources (Figma, Confluence), codebase patterns, and human input to inform implementation planning. Must be run after /pull.

jira-to-github

Execute the complete JIRA-to-GitHub workflow from analysis to PR creation with approval checkpoints at each stage. Takes a JIRA key as argument (e.g., DRT-17270).

plan

Design implementation approach with human-in-the-loop architectural decisions. Presents 2-3 options with trade-offs for user selection. Must be run after /explore.

pull

Fetch and analyze JIRA issue details, detect target repository, extract requirements, retrieve Confluence docs, and download attachments. Takes a JIRA key as argument (e.g., DRT-17270).

push

Commit changes, push to GitHub, and create pull request using repo-specific PR template. Must be run after /code (ideally after /test and /validate).

resolve-review-comments

Fetch, analyze, group, and resolve code review comments from GitHub PRs. Implements fixes, responds to questions, and updates PR threads. Can be run after /push or standalone.

review

Provide human-in-the-loop feedback on implementation plan. Accept review comments, questions, or approval. Supports unlimited iterations. Can be run after /plan or /code.

stash-jira

Preserve current workflow artifacts by moving them from project directory to Claude home directory, enabling context switching between JIRA issues.

upgrade-hpp

Automate HPP version upgrade to Esperanto by extracting review version from HPP PR and creating upgrade PR in Esperanto. Optionally takes HPP PR number as argument.

validate

Run linting, type checking, and unit tests to validate changes before pushing to GitHub. Uses repo-specific validation commands from CLAUDE.md.

auto-deploy-esperanto-review-app

Automate deployment of HPP review versions to Esperanto QA stage environment by extracting review version from HPP PR and creating/updating Esperanto PR. Optionally takes HPP PR number.