SkillsAdd

opsmill/infrahub · Archived

speckit-git-feature

Validate Jira/JPD ticket reference and create a feature branch

First seen May 16, 2026

Installation

$ npx skills add opsmill/infrahub --skill speckit-git-feature
View on skills.sh ↗ GitHub repository ↗

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

neo4j-cypher-guide Same source
opsmill/infrahub

Comprehensive guide for writing modern Neo4j Cypher queries.

3 installs
speckit-taskstoissues Same source
opsmill/infrahub

Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based …

2 installs
speckit-tasks Same source
opsmill/infrahub

Generate an actionable, dependency-ordered tasks.md for the feature based on available design a…

2 installs
speckit-specify Same source
opsmill/infrahub

Create or update the feature specification from a natural language feature description.

2 installs

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

speckit-specify Similar name
dceoy/speckit-agent-skills

Create or update the feature specification from a natural language feature description.

52 installs
speckit-plan Similar name
dceoy/speckit-agent-skills

Execute the implementation planning workflow using the plan template to generate design artifac…

52 installs
speckit-constitution Similar name
dceoy/speckit-agent-skills

Create or update the project constitution from interactive or provided principle inputs.

50 installs
speckit-tasks Similar name
dceoy/speckit-agent-skills

Generate an actionable, dependency-ordered tasks.md for the feature based on available design a…

50 installs
speckit-implement Similar name
dceoy/speckit-agent-skills

Execute the implementation plan by processing and executing all tasks defined in tasks.md

50 installs
speckit-clarify Similar name
dceoy/speckit-agent-skills

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted cla…

50 installs

Also in this package

Other skills from opsmill/infrahub · top by installs.

npx skills add opsmill/infrahub
neo4j-cypher-guide 3 speckit-taskstoissues 2 speckit-tasks 2 speckit-specify 2 speckit-review-types 2 speckit-plan 2 speckit-implement 2 speckit-git-validate 2 speckit-git-remote 2 speckit-git-initialize 2

Browse all from opsmill/infrahub

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 513
License LICENSE.txt
Default branch stable
Open issues 439
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

CompatibilityRequires spec-kit project structure with .specify/ directory
More metadata
author
github-spec-kit
source
preset:infrahub

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,559 B
  • docs SUMMARY.md 89 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 3 installs

SKILL.md

Speckit Git Feature Skill

Create Infrahub Feature Branch

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.

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-460 for a JPD item or ifc-2140 for 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

Step 3: Create Branch

Construct the branch name as <short-name>-<ticket-id> (e.g., user-auth-infp-460), then pass it as GITBRANCHNAME 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:

  • Always construct GITBRANCHNAME as <short-name>-<ticket-id> — ticket ID is the suffix
  • Always include --json so output can be parsed reliably
  • Run this script exactly once per feature
  • For single quotes in args, use escape syntax: 'I'\''m Groot'

Output

The script outputs JSON with:

  • BRANCH_NAME: The branch name (e.g., user-auth-infp-460)
  • FEATURE_NUM: The ticket ID