MoAI Worktree Management
modu-ai/moai-adk
Gives each SPEC its own Git worktree with a registry of active workspaces, base-branch sync and cleanup of merged ones, inside the MoAI-ADK workflow.
Validate Jira/JPD ticket reference and create a feature branch
$ npx skills add opsmill/infrahub --skill speckit-git-feature -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install opsmill/infrahub speckit-git-feature --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/opsmill/infrahub.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/speckit-git-feature .claude/skills/speckit-git-feature && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "speckit-git-feature" agent skill from https://github.com/opsmill/infrahub/tree/stable/.agents/skills/speckit-git-feature into .claude/skills/speckit-git-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "speckit-git-feature", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/opsmill/infrahub/tree/stable/.agents/skills/speckit-git-featureType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add opsmill/infrahub --skill speckit-git-feature -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install opsmill/infrahub speckit-git-feature --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/opsmill/infrahub.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/speckit-git-feature .agents/skills/speckit-git-feature && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "speckit-git-feature" agent skill from https://github.com/opsmill/infrahub/tree/stable/.agents/skills/speckit-git-feature into .agents/skills/speckit-git-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "speckit-git-feature", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add opsmill/infrahub --skill speckit-git-feature -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install opsmill/infrahub speckit-git-feature --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/opsmill/infrahub.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/speckit-git-feature .cursor/skills/speckit-git-feature && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "speckit-git-feature" agent skill from https://github.com/opsmill/infrahub/tree/stable/.agents/skills/speckit-git-feature into .cursor/skills/speckit-git-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "speckit-git-feature", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/opsmill/infrahub.git --path .agents/skills/speckit-git-feature--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add opsmill/infrahub --skill speckit-git-feature -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install opsmill/infrahub speckit-git-feature --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/opsmill/infrahub.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/speckit-git-feature .gemini/skills/speckit-git-feature && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "speckit-git-feature" agent skill from https://github.com/opsmill/infrahub/tree/stable/.agents/skills/speckit-git-feature into .gemini/skills/speckit-git-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "speckit-git-feature", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install opsmill/infrahub speckit-git-featureInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add opsmill/infrahub --skill speckit-git-feature -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/opsmill/infrahub.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/speckit-git-feature .github/skills/speckit-git-feature && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "speckit-git-feature" agent skill from https://github.com/opsmill/infrahub/tree/stable/.agents/skills/speckit-git-feature into .github/skills/speckit-git-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "speckit-git-feature", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add opsmill/infrahub --skill speckit-git-feature -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install opsmill/infrahub speckit-git-feature --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/opsmill/infrahub.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/speckit-git-feature .opencode/skills/speckit-git-feature && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "speckit-git-feature" agent skill from https://github.com/opsmill/infrahub/tree/stable/.agents/skills/speckit-git-feature into .opencode/skills/speckit-git-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "speckit-git-feature", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
speckit-git-featureValidate Jira/JPD ticket reference and create a feature branch
Speckit Git Feature is an agent skill from opsmill/infrahub. Validate Jira/JPD ticket reference and create a feature branch
Its SKILL.md is about 640 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Requires spec-kit project structure with .specify/ directory
It sits in Development, covering Spec-driven development and Git workflow. It works with Git and Jira. The repository describes itself as: Infrahub is a graph-based data management platform with built-in version control, CI workflows, peer review, and API access. It’s purpose-built to power reliable infrastructure… The licence is Apache-2.0.
3 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 460d724. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
gitFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Requires spec-kit project structure with .specify/ directory
From compatibility in the SKILL.md frontmatter.
Speckit Git Feature loads about 638 tokens when it runs. Until then it costs about 21 tokens; SKILL.md has 263 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from opsmill/infrahub at commit 460d724, republished under its Apache-2.0 licence (© opsmill). 263 words, ~638 tokens.
.claude/skills/speckit-git-feature/SKILL.md (or your agent's skills folder).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.
$ARGUMENTSgit 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© opsmill, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .agents/skills/speckit-git-feature of opsmill/infrahub.
Open the folder on GitHubat commit 460d724
Speckit Git Feature next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Speckit Git Feature this skillopsmill/infrahub | 531 | — | ~638 | Automated safety check: Pass | Apache-2.0 | |
| MoAI Worktree Managementmodu-ai/moai-adk | 1.2k | — | ~3.9k | Automated safety check: Pass | Apache-2.0 | |
| Project Session ManagerYeachan-Heo/oh-my-claudecode | 40k | — | ~4k | Automated safety check: Pass | MIT | |
| Speckit Git Featurekunstmusik/blue | 154 | 5 repos | ~861 | Automated safety check: Pass | GPL-3.0 | |
| Speckit Git Validatekunstmusik/blue | 154 | 5 repos | ~489 | Automated safety check: Pass | GPL-3.0 | |
| Speckit Git Initializekunstmusik/blue | 154 | 6 repos | ~438 | Automated safety check: Pass | GPL-3.0 |
modu-ai/moai-adk
Gives each SPEC its own Git worktree with a registry of active workspaces, base-branch sync and cleanup of merged ones, inside the MoAI-ADK workflow.
Yeachan-Heo/oh-my-claudecode
Creates isolated git worktrees, with optional tmux sessions, for PR reviews, issue fixes and feature work across projects and repositories.
kunstmusik/blue
Create a feature branch with sequential or timestamp numbering
kunstmusik/blue
Validate current branch follows feature branch naming conventions
kunstmusik/blue
Initialize a Git repository with an initial commit. An agent skill from kunstmusik/blue.
kunstmusik/blue
Detect Git remote URL for GitHub integration. An agent skill from kunstmusik/blue.
opsmill/infrahub
Analyzes recent CI failures on pull requests to identify flaky tests, using retry outcomes (failed attempt → green re-run) and cross-PR recurrence as evidence, and maintains a local longitudinal…
opsmill/infrahub
Audits internal (dev/) and external (docs/) documentation completeness for a feature, subject, or set of existing docs, maps changes indicated by the user, across Infrahub's documentation layers…
opsmill/infrahub
Stages and commits the current changes onto a safe working branch, enforcing branch discipline and optionally pushing upstream.
opsmill/infrahub
A skill your agent uses when you've fixed a bug, added a feature, or made any user-facing change in a project that uses Towncrier and need to record it for the changelog — before committing or…
opsmill/infrahub
Turns a single feature idea, improvement, or bug into ONE well-structured GitHub issue.
opsmill/infrahub
Synthesises the current conversation context into a Product Requirements Document and publishes it to GitHub (as a comment on a referenced issue, or a new issue).
Categories
Validate Jira/JPD ticket reference and create a feature branch. Speckit Git Feature is an agent skill from opsmill/infrahub.
Speckit Git Feature fits situations like: tasks that involve Spec-driven development; tasks that involve Git workflow.
Run `npx skills add opsmill/infrahub --skill speckit-git-feature -a claude-code`. Or copy the skill folder (.agents/skills/speckit-git-feature in opsmill/infrahub) into .claude/skills/speckit-git-feature in your project. Claude Code loads it when a task matches its description.
Run `npx skills add opsmill/infrahub --skill speckit-git-feature -a codex`. Or copy the skill folder (.agents/skills/speckit-git-feature in opsmill/infrahub) into .agents/skills/speckit-git-feature in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add opsmill/infrahub --skill speckit-git-feature -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/speckit-git-feature, .gemini/skills/speckit-git-feature, .github/skills/speckit-git-feature and .opencode/skills/speckit-git-feature in your project.
Going by SKILL.md and its folder, Speckit Git Feature needs the command-line tools its instructions call (git). Compatibility (from SKILL.md): Requires spec-kit project structure with .specify/ directory.
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Speckit Git Feature is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 638 tokens (SKILL.md is roughly 2.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Speckit Git Feature: MoAI Worktree Management (modu-ai/moai-adk, 1.2k stars), Project Session Manager (Yeachan-Heo/oh-my-claudecode, 40k stars), Speckit Git Feature (kunstmusik/blue, 154 stars) and Speckit Git Validate (kunstmusik/blue, 154 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
opsmill (a GitHub organization) maintains it in opsmill/infrahub, which has 531 GitHub stars. The repository holds 32 skills in this directory. The repository was last updated on October 8, 2026.
Source: opsmill/infrahub on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.