// Validate Jira/JPD ticket reference and create a feature branch
Migrate Infrahub docs feature pages from the legacy topic+guide pair into a cleaner structure (single merged page, hub+spokes, or tutorial extraction). Supports both single-feature migrations (one feature like Profiles or Webhooks) and section-wide migrations (a whole section like Branches & Change Control with multiple features migrated together) when the team has agreed on a section-wide restructure plan. Trigger when the user names a specific feature or section to migrate (e.g. "let's migrate profiles", "start the Resource Manager migration", "do the entire Branches & Change Control section"). Each migration is its own branch off `demo/groups-diataxis-example`, its own PR back to that branch.
Comprehensive guide for writing modern Neo4j Cypher read queries. Essential for text2cypher MCP tools and LLMs generating Cypher queries. Covers removed/deprecated syntax, modern replacements, CALL subqueries for reads, COLLECT patterns, sorting best practices, and Quantified Path Patterns (QPP) for efficient graph traversal.
| 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