resolve-issues_skill

Overview

This skill automates resolving GitHub issues using isolated git worktrees and a strict TDD cycle. It creates or reuses worktrees, runs failing tests, implements fixes with atomic commits, and opens a protected PR that auto-closes the issue. The workflow includes specialized review agents for architecture and code simplification and cleans up worktrees after merge.

How this skill works

The skill inspects repository state (git status, current branch, existing worktrees, open issues, and GitHub auth) to pick a target issue and determine whether to create a new worktree. It runs a test-first cycle (red → green → refactor) with coordinated sub-agents for tech-lead review and code simplification, executes lint/test/build checks, and pushes a branch with atomic, conventionally formatted commits. Finally it opens a PR referencing the issue with auto-closing keywords and removes the worktree once the change is merged.

When to use it

• Fixing a reproducible bug that has tests or can have tests added
• Implementing a small feature or refactor tied to a single issue
• When you need isolated development environments to avoid local branch conflicts
• When strict commit hygiene and conventional commits are required for CI/CD
• When PRs must reference and auto-close specific GitHub issues

Best practices

• Use an isolated worktree per issue with a descriptive branch name (e.g., fix/456-auth-redirect)
• Follow TDD: write a failing test, implement the change to pass tests, then refactor
• Make atomic commits: one cohesive change per commit with conventional commit title and a blank-line-separated body
• Title rules: lowercase, <50 chars, imperative, prefixed with conventional type and optional existing scope
• Body rules: start with uppercase letter, ≤72 chars per line, describe what changed and why (not how)
• Footer: optional, start uppercase, reference issues with "Closes #" or use BREAKING CHANGE: for breaking APIs

Example use cases

• Pick the highest-priority open issue, create worktree, add failing test, implement fix, and open PR that closes the issue
• Address regression by adding a regression test, fixing code, and committing with a clear, atomic conventional commit
• Refactor a module: add tests to lock behavior, simplify code with code-simplifier agent, keep tests green, then open a scoped refactor PR
• Add a small feature behind a feature flag with tests and a feature-scoped commit that links to the feature request issue