Dev Review
FHIR/fhir-codegen
Performs a two-track code-quality and QA review in the roles of a staff-level Engineering Lead and QA Lead, then synthesizes both critiques into a single analysis.md.
Resolve a spec issue end-to-end using sequential subagents. An agent skill from gittower/git-flow-next.
Install Resolve Issue
$ npx skills add gittower/git-flow-next --skill resolve-issue -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install gittower/git-flow-next resolve-issue --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/gittower/git-flow-next.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/resolve-issue .claude/skills/resolve-issue && 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 "resolve-issue" agent skill from https://github.com/gittower/git-flow-next/tree/main/.claude/skills/resolve-issue into .claude/skills/resolve-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resolve-issue", 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/gittower/git-flow-next/tree/main/.claude/skills/resolve-issueType 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 gittower/git-flow-next --skill resolve-issue -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install gittower/git-flow-next resolve-issue --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gittower/git-flow-next.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/resolve-issue .agents/skills/resolve-issue && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "resolve-issue" agent skill from https://github.com/gittower/git-flow-next/tree/main/.claude/skills/resolve-issue into .agents/skills/resolve-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resolve-issue", 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 gittower/git-flow-next --skill resolve-issue -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install gittower/git-flow-next resolve-issue --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gittower/git-flow-next.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/resolve-issue .cursor/skills/resolve-issue && 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 "resolve-issue" agent skill from https://github.com/gittower/git-flow-next/tree/main/.claude/skills/resolve-issue into .cursor/skills/resolve-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resolve-issue", 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/gittower/git-flow-next.git --path .claude/skills/resolve-issue--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 gittower/git-flow-next --skill resolve-issue -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install gittower/git-flow-next resolve-issue --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gittower/git-flow-next.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/resolve-issue .gemini/skills/resolve-issue && 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 "resolve-issue" agent skill from https://github.com/gittower/git-flow-next/tree/main/.claude/skills/resolve-issue into .gemini/skills/resolve-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resolve-issue", 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 gittower/git-flow-next resolve-issueInstalls 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 gittower/git-flow-next --skill resolve-issue -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/gittower/git-flow-next.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/resolve-issue .github/skills/resolve-issue && 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 "resolve-issue" agent skill from https://github.com/gittower/git-flow-next/tree/main/.claude/skills/resolve-issue into .github/skills/resolve-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resolve-issue", 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 gittower/git-flow-next --skill resolve-issue -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install gittower/git-flow-next resolve-issue --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gittower/git-flow-next.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/resolve-issue .opencode/skills/resolve-issue && 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 "resolve-issue" agent skill from https://github.com/gittower/git-flow-next/tree/main/.claude/skills/resolve-issue into .opencode/skills/resolve-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resolve-issue", 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.
Facts
- Skill name
resolve-issue- GitHub stars
- 458
- Token cost
- ~2.2k tokens
- SKILL.md length
- 1,088 words
- Files
- 1
- Skills in repo
- 25
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Resolve a spec issue end-to-end using sequential subagents. An agent skill from gittower/git-flow-next.
- Works in 10 steps: Analyze Spec Against Codebase → Create Feature Branch + Worktree → Create Test-First Plan → …
- Tasks that involve Subagents
- SKILL.md covers Arguments, Precondition: Spec Issue…, Workflow and Progress Reporting, plus 1 more section
- Calls git, gh and go
What it does
Resolve Issue is an agent skill from gittower/git-flow-next. Resolve a spec issue end-to-end using sequential subagents
Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering Subagents. The repository describes itself as: A modern reimplementation of git-flow in Go that offers greater flexibility while maintaining backward compatibility with the original git-flow and git-flow-avh.
When your agent uses it
- Tasks that involve Subagents
Example prompts
- “/resolve-issue”
Requirements
- Pre-approved tools (allowed-tools): Task, Bash, Read, Glob, Grep, Write, Agent, mcp__github__get_issue
Workflow steps
10 steps, taken from the step headings in SKILL.md.
- Analyze Spec Against Codebase
- Create Feature Branch + Worktree
- Create Test-First Plan
- Codex-Gate the Test Plan
- Implement
- Local Review
- Codex Code Review
- Implement Review Fixes
- PR Summary
- Publish Gate
What it can do on your machine
Read from SKILL.md and the folder at commit 00d1b4b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
TaskBashReadGlobGrepWriteAgentmcp__github__get_issue
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gitghgo
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Resolve Issue loads about 2.2k tokens when it runs. Until then it costs about 18 tokens; SKILL.md has 1,088 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.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Task, Bash, Read, Glob, Grep, Write, Agent, mcp__github__get_issue
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.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,088 words (~2,247 tokens).
“Resolve a GitHub spec issue end-to-end by orchestrating the full workflow. Each step runs in a fresh subagent context via the Task tool so that no single context becomes overloaded. Runs autonomously; the only user gates are abort conditions and…”
- name
- resolve-issue
- allowed-tools
- Task, Bash, Read, Glob, Grep, Write, Agent, mcp__github__get_issue
- argument-hint
- <issue-number>
Files
Just SKILL.md in .claude/skills/resolve-issue of gittower/git-flow-next.
Open the folder on GitHubat commit 00d1b4b
Compare with similar skills
Resolve Issue 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 |
|---|---|---|---|---|---|---|
| Resolve Issue this skillgittower/git-flow-next | 458 | — | ~2.2k | Automated safety check: Notes | Custom licence | |
| Dev ReviewFHIR/fhir-codegen | 154 | — | ~5k | Automated safety check: Pass | MIT | |
| Nv Implementnovuhq/novu | 40k | — | ~1.7k | Automated safety check: Pass | Custom licence | |
| Tapd Story ImplementTencentBlueKing/bk-bcs | 840 | — | ~1.2k | Automated safety check: Pass | Custom licence | |
| Implementopen-octo/octo-agent | 125 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Libreqos Review Subagents WorkflowLibreQoE/LibreQoS | 718 | — | ~1.2k | Automated safety check: Pass | GPL-2.0 |
Similar skills
Nv Implement
novuhq/novu
Implement planned work by fanning out parallel subagents on isolated worktrees — TDD at pre-agreed seams, per-slice nv-park-and-review, merge back, full suite once at the end.
Tapd Story Implement
TencentBlueKing/bk-bcs
迭代执行流水线代码实现阶段。基于 tasks.md 调用 /speckit.implement 以 TDD 模式完成全部任务。
Implement
open-octo/octo-agent
Implement a technical design by decomposing it into dependency-ordered vertical slices, executing each with TDD red-green, reviewing each via an isolated sub-agent, and persisting progress to a…
Libreqos Review Subagents Workflow
LibreQoE/LibreQoS
Project workflow for invoking the local review sub-agents Thomas, Helen, Beck, Jonas, The Reaper, and Heckler during LibreQoS coding sessions.
Testing Skills With Subagents
ed3dai/ed3d-plugins
A skill your agent uses when creating or editing skills, before deployment, to verify they work under pressure and resist rationalization - applies RED-GREEN-REFACTOR cycle to process documentation…
More from gittower/git-flow-next
All 25 skills in this repoGitHub Issue Analysis
gittower/git-flow-next
Analyzes a GitHub issue for the git-flow-next project and writes an analysis document under .ai/ that covers the affected code and proposes TODO comments.
PR Review Feedback Handler
gittower/git-flow-next
Fetches review comments on a pull request, judges each one, writes the evaluation to a plan file and implements accepted changes, waiting for approval before anything public.
Stale PR Review Check
gittower/git-flow-next
Scans open pull requests against the project's review response window and reports which ones need action, read-only unless you approve a reminder.
Local Code Review
gittower/git-flow-next
Reviews local commits, branch diffs or pull requests against project guidelines and writes the result to local files, never posting it to GitHub.
Commit with Project Guidelines
gittower/git-flow-next
Creates a commit that follows the project's COMMIT_GUIDELINES.md, choosing the type by what the change does and verifying the result.
Test-First Implementation Plan
gittower/git-flow-next
Builds a two-phase implementation plan from a spec issue, analysis or concept, writing a detailed test plan first and the implementation outline second.
Related
Categories
Questions about Resolve Issue
What does Resolve Issue do?
Resolve a spec issue end-to-end using sequential subagents. An agent skill from gittower/git-flow-next. Resolve Issue is an agent skill from gittower/git-flow-next.
When should I use Resolve Issue?
Resolve Issue fits situations like: tasks that involve Subagents.
How do I install Resolve Issue in Claude Code?
Run `npx skills add gittower/git-flow-next --skill resolve-issue -a claude-code`. Or copy the skill folder (.claude/skills/resolve-issue in gittower/git-flow-next) into .claude/skills/resolve-issue in your project. Claude Code loads it when a task matches its description.
How do I install Resolve Issue in Codex?
Run `npx skills add gittower/git-flow-next --skill resolve-issue -a codex`. Or copy the skill folder (.claude/skills/resolve-issue in gittower/git-flow-next) into .agents/skills/resolve-issue in your project. Codex loads it when a task matches its description.
Can I use Resolve Issue in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add gittower/git-flow-next --skill resolve-issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/resolve-issue, .gemini/skills/resolve-issue, .github/skills/resolve-issue and .opencode/skills/resolve-issue in your project.
What does Resolve Issue need to run?
Going by SKILL.md and its folder, Resolve Issue needs the command-line tools its instructions call (git, gh and go). Its frontmatter pre-approves these tools: Task, Bash, Read, Glob, Grep, Write, Agent, mcp__github__get_issue.
Does Resolve Issue access the network?
SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Resolve Issue safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Resolve Issue use?
Resolve Issue has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Resolve Issue use?
About 2.2k tokens (SKILL.md is roughly 9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Resolve Issue?
Skills that share tags, products or a category with Resolve Issue: Dev Review (FHIR/fhir-codegen, 154 stars), Nv Implement (novuhq/novu, 40k stars), Tapd Story Implement (TencentBlueKing/bk-bcs, 840 stars) and Implement (open-octo/octo-agent, 125 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Resolve Issue?
gittower (a GitHub organization) maintains it in gittower/git-flow-next, which has 458 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on September 8, 2026.
Source: gittower/git-flow-next on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.