Menu
Validate Jira/JPD ticket reference and create a feature branch
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Audits documentation completeness for a feature branch, subject, or set of existing docs — maps changes across Infrahub's documentation layers, reports gaps, and optionally applies the fixes. TRIGGER when: the user wants to audit or check documentation coverage, find doc gaps after a feature branch, or verify docs are still current for a subject or specific files. DO NOT TRIGGER when: authoring new documentation from scratch → use the add-docs flow; only linting/formatting Markdown → run `uv run invoke docs.lint`.
Perform a dual-lens critical review of the specification and plan from both product strategy and engineering risk perspectives before implementation.
General code quality review — project guideline compliance, bug detection, code quality analysis.
Code comment accuracy verification, documentation completeness assessment, comment rot detection.
Error handling review — silent failure detection, catch block analysis, error logging.
Comprehensive code review using specialized agents — orchestrates code, comments, tests, errors, types, and simplify agents sequentially.
| name | speckit-git-feature |
| description | Validate Jira/JPD ticket reference and create a feature branch |
| compatibility | Requires spec-kit project structure with .specify/ directory |
| metadata | {"author":"github-spec-kit","source":"preset:infrahub"} |
| user-invocable | true |
| disable-model-invocation | false |
Create and switch to a new git feature branch for the given specification, enforcing an Infrahub Jira or JPD ticket reference as the branch name suffix.
$ARGUMENTS
git rev-parse --is-inside-work-tree 2>/dev/nullParse $ARGUMENTS for a ticket ID matching either of these formats:
infp-[0-9]+ (e.g., infp-460)ifc-[0-9]+ (e.g., ifc-2140)If no ticket ID is found in the arguments, prompt the user:
"Please provide a Jira or JPD reference for this feature (e.g.,
infp-460for a JPD item orifc-2140for a Jira epic):"
Do not proceed until a valid ticket ID is provided. Never invent or skip it.
Generate a concise short name (2-4 words) from the feature description:
user-auth, fix-payment-timeout)user-authoauth2-api-integrationfix-payment-timeoutConstruct the branch name as <short-name>-<ticket-id> (e.g., user-auth-infp-460), then pass it as GIT_BRANCH_NAME to bypass the script's automatic numbering:
GIT_BRANCH_NAME="<short-name>-<ticket-id>" .specify/extensions/git/scripts/bash/create-new-feature.sh --json "<feature description>"
Example:
GIT_BRANCH_NAME="user-auth-infp-460" .specify/extensions/git/scripts/bash/create-new-feature.sh --json "Add user authentication"
IMPORTANT:
GIT_BRANCH_NAME as <short-name>-<ticket-id> — ticket ID is the suffix--json so output can be parsed reliably'I'\''m Groot'The script outputs JSON with:
BRANCH_NAME: The branch name (e.g., user-auth-infp-460)FEATURE_NUM: The ticket ID