opsmill/infrahub / .agents/skills/speckit-git-feature
speckit-git-feature
VerifiedValidate Jira/JPD ticket reference and create a feature branch
Create Feature Branch
Create and switch to a new git feature branch for the given specification, enforcing a Jira or JPD ticket reference as the branch name suffix.
User Input
$ARGUMENTS
Prerequisites
- Verify Git is available by running
git rev-parse --is-inside-work-tree 2>/dev/null - If Git is not available, warn the user and skip branch creation
Step 1: Resolve Ticket Reference
Parse $ARGUMENTS for a ticket ID matching either of these formats:
- JPD format:
infp-[0-9]+(e.g.,infp-460) - Jira epic format:
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.
Step 2: Generate Short Name
Generate a concise short name (2-4 words) from the feature description:
- Use action-noun format when possible (e.g.,
user-auth,fix-payment-timeout) - Preserve technical terms and acronyms (OAuth2, API, JWT, etc.)
- Examples:
- "Add user authentication" →
user-auth - "Implement OAuth2 integration for the API" →
oauth2-api-integration - "Fix payment processing timeout bug" →
fix-payment-timeout
- "Add user authentication" →
Step 3: Create Branch
Construct the branch name as <short-name>-<ticket-id> (e.g., user-auth-infp-460): the ticket ID is the suffix, and the name must be 244 bytes or fewer.
Create the branch and switch to it with one plain git command, written out, without an environment variable before it, so that permission rules can match it:
git checkout -b "<short-name>-<ticket-id>"
If the branch already exists, do not switch to it and do not create another one: stop and tell the user.
The git extension's branch script is not used: it only takes an exact branch name through the GIT_BRANCH_NAME environment variable, which keeps permission rules from matching the command.
Output
Report, as JSON:
BRANCH_NAME: the branch name (e.g.,user-auth-infp-460)FEATURE_NUM: the ticket ID resolved in Step 1 (e.g.,infp-460)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 117k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |