resolve-issues
Resolves GitHub issues using isolated worktrees and test-driven development. This skill should be used when the user asks to "resolve an issue", "fix issue
Best use case
resolve-issues is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Resolves GitHub issues using isolated worktrees and test-driven development. This skill should be used when the user asks to "resolve an issue", "fix issue
Teams using resolve-issues should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/resolve-issues/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How resolve-issues Compares
| Feature / Agent | resolve-issues | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Resolves GitHub issues using isolated worktrees and test-driven development. This skill should be used when the user asks to "resolve an issue", "fix issue
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Resolve GitHub Issues Execute issue resolution workflow using isolated worktrees, TDD methodology, and agent collaboration. ## Context - Current git status: !`git status` - Current branch: !`git branch --show-current` - Existing worktrees: !`git worktree list` - Open issues: !`gh issue list --state open --limit 10` - GitHub authentication: !`gh auth status` ## Requirements Summary Use isolated worktrees to avoid disrupting main development. Follow TDD cycle (red → green → refactor) with agent support. Reference issues in commits using auto-closing keywords. See `references/requirements.md` for protected PR workflow and commit standards. ## Phase 1: Issue Selection and Worktree Setup **Goal**: Select target issue and prepare isolated development environment. **Actions**: 1. Review open issues from context and select based on priority and `$ARGUMENTS` 2. Check existing worktrees to determine if reuse is possible 3. Create new worktree with descriptive branch name (see `references/workflow-details.md` for naming) 4. Navigate to worktree directory for isolated development 5. Verify issue acceptance criteria and dependencies ## Phase 2: TDD Implementation **Goal**: Implement fix using test-driven development with agent collaboration. **Actions**: 1. Plan implementation approach and assess architectural impact 2. Write failing tests that verify issue is resolved (RED phase) 3. Implement minimal code to make tests pass (GREEN phase) 4. Refactor while keeping tests green (REFACTOR phase) 5. Run quality validation commands (see `references/workflow-details.md` for project-specific checks) ## Phase 3: PR Creation and Cleanup **Goal**: Create pull request, link issue, and clean up worktree after merge. **Actions**: 1. Push branch to remote with `git push -u origin <branch-name>` 2. Create PR using `gh pr create` with auto-closing keywords (e.g., "Closes #456") 3. Report PR URL and status to user 4. After successful merge: remove worktree and delete local branch 5. Document resolution and any follow-up tasks ## References - **Requirements**: `references/requirements.md` - Worktree setup, TDD, and commit standards - **Workflow Details**: `references/workflow-details.md` - Issue selection, TDD cycle, agent collaboration - **Examples**: `references/examples.md` - Commit message examples
Related Skills
create-issues
Creates GitHub issues following test-driven development principles and proper labeling conventions. This skill should be used when the user asks to "create an issue", "file a bug", or needs to document new requirements, epics, or PR-scoped tasks.
update-readme
Updates README.md and README.zh-CN.md to reflect the project's current state. Use this skill whenever the user asks to "update the README", "sync the docs", "update documentation", "reflect latest changes in README", or wants both the English and Chinese READMEs to match the current project. Always triggers when the user mentions updating or regenerating README files, especially for bilingual (EN/ZH) projects.
swiftui-review
Reviews SwiftUI code for best practices on modern APIs, maintainability, and performance. This skill should be used when the user asks to review SwiftUI code, check for deprecated iOS/macOS APIs, validate data flow patterns, or audit accessibility compliance in Swift projects.
writing-plans
Creates executable implementation plans that break down designs into detailed tasks. This skill should be used when the user has completed a brainstorming design and asks to "write an implementation plan" or "create step-by-step tasks" for execution.
systematic-debugging
Provides a systematic debugging methodology with a 4-phase root cause analysis process. This skill should be used when the user reports a bug, error, test failure, or unexpected behavior, ensuring thorough investigation precedes any code changes.
need-vet
This skill should be used when the user invokes /need-vet to enable work verification for the current task. Claude must verify completion and append the verified tag before the session can end.
executing-plans
Executes written implementation plans efficiently using agent teams or subagents. This skill should be used when the user has a completed plan.md, asks to "execute the plan", or is ready to run batches of independent tasks in parallel following BDD principles.
build-like-iphone-team
Applies Apple's Project Purple design philosophy for radical innovation. This skill should be used when the user wants to challenge industry conventions, approach open-ended problems requiring disruptive thinking, or when standard brainstorming needs a breakthrough approach.
brainstorming
Structures collaborative dialogue to turn rough ideas into implementation-ready designs. This skill should be used when the user has a new idea, feature request, ambiguous requirement, or asks to "brainstorm a solution" before implementation begins.
behavior-driven-development
Applies behavior-driven development principles including Gherkin scenarios and test-driven development. This skill should be used when the user asks to implement features, fix bugs, or when writing executable specifications and tests before writing production code.
agent-team-driven-development
Provides guidance on coordinating multiple specialized teammates working in parallel. This skill should be used when the user needs to execute complex implementation plans, resolve cross-cutting concerns, or coordinate independent work streams requiring communication.
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".