ryan-mahoney/spec-branch
skills/spec-branch/SKILL.md
This skill should be used when the user asks to "create a spec branch", "make a spec branch", "start a branch", or "branch from spec". Creates a local branch from a spec, description, or issue/ticket reference without requiring GitHub.
tools
Updated Jun 12, 2026
$ install --global
skillsauthnpx skillsauth add ryan-mahoney/ryan-llm-skills spec-branchInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 12, 2026, 5:33 AM46.5s1 file scanned
SKILL.md
- name:
- spec-branch
- description:
- This skill should be used when the user asks to "create a spec branch", "make a spec branch", "start a branch", or "branch from spec". Creates a local branch from a spec, description, or issue/ticket reference without requiring GitHub.
- disable-model-invocation:
- true
- argument-hint:
- [description, feature-slug, or issue/ticket reference]
Spec Branch
Create a new local branch related to a spec-driven task.
Inputs
Use $ARGUMENTS as the branch topic. It may be:
- A
.specs/<feature-slug>/folder name. - A free-text work description.
- A ticket reference plus description, such as
PROJ-123 add invoice retry. - A GitHub issue number, only when the current repo is hosted on GitHub.
If $ARGUMENTS is empty, ask the user for a short description. Do not create a branch from an empty or bare identifier.
Resolve the Topic
- Confirm the current directory is a git repository:
git rev-parse --git-dir. - If
$ARGUMENTSnames.specs/<feature-slug>/, readspec.mdorproposal.mdand derive the branch topic from the feature slug and title. - If
$ARGUMENTSis only a number and the current repo has a GitHub remote, trygh issue view <number> --json title --jq .title. - If the GitHub lookup fails, or the repo is not GitHub-hosted, ask for a descriptive title. A bare number is not a valid branch name.
Derive the Branch Name
Parse the resolved topic into a valid branch name:
- Lowercase the entire string.
- Preserve a leading issue or ticket prefix when present (
123,PROJ-123, etc.). - Replace
/, spaces, underscores, and consecutive special characters with a single-. - Strip leading/trailing hyphens.
- Truncate to 60 characters max, trimming at the last full word boundary when possible.
Examples:
| Input | Branch |
|---|---|
| 1087 redesign dashboard onboarding | 1087-redesign-dashboard-onboarding |
| PROJ-123 add invoice retry | proj-123-add-invoice-retry |
| fix candidate stage seed data | fix-candidate-stage-seed-data |
| .specs/new-billing-export/ | new-billing-export |
Create the Branch
- Check whether the branch already exists:
git rev-parse --verify <branch-name>. - If it exists, switch to it with
git switch <branch-name>. - If it does not exist, create it from the current HEAD with
git switch -c <branch-name>. - Remove upstream tracking if present:
git branch --unset-upstream <branch-name> 2>/dev/null || true.
Report
Report:
- Branch name.
- Source topic: spec folder, GitHub issue, ticket reference, or free-text description.
- Tracking status: none.
Do not implement the spec after creating the branch.
Related Skills
ryan-mahoney/spec-write
documentation
VerifiedTrustedCommunity
This skill should be used when the user asks to "write a spec", "create a spec", "spec this out", "plan this feature", or "write an implementation plan" for a feature or change. Creates a structured implementation spec in .specs/<slug>/spec.md and mirrors it to GitHub only when the current repository is hosted on GitHub.
SKILL.mdUpdated Jun 12, 2026
ryan-mahoney/spec-run
data-ai
VerifiedTrustedCommunity
This skill should be used when the user asks to "execute the spec", "run the plan", "implement the spec", "implement the issue", "run all steps", or "run spec". Implements all steps from .specs/<slug>/spec.md, using a subagent per step when the harness supports subagents.
SKILL.mdUpdated Jun 12, 2026
ryan-mahoney/spec-review
testing
VerifiedTrustedCommunity
This skill should be used when the user asks to "review a spec", "review an issue", "check the plan", "review the implementation plan", "find gaps in the spec", or "review spec". Reviews .specs/<slug>/spec.md for gaps and viability, edits it when needed, and mirrors changes to GitHub only when a GitHub mirror exists.
SKILL.mdUpdated Jun 12, 2026
ryan-mahoney/spec-remediate
development
VerifiedTrustedCommunity
This skill should be used when the user asks to "remediate the audit findings", "fix the spec violations", "close the audit findings", "fix conformance violations", or "spec remediate". Reads a spec-audit report, drives one smart subagent per VIOLATION to converge the code back to the frozen spec, and re-audits until clean. Edits production code; never rewrites the spec.
SKILL.mdUpdated Jun 12, 2026