resolve-issues

Automates GitHub issue resolution with isolated worktrees and a TDD cycle.

577|48|Updated Aug 4, 2025

Search Tags:#automation #git #TDD #github #worktree #atomic-commits #pull-request

Ready to run

npx skills add https://github.com/FradSer/dotclaude --skill resolve-issues

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: resolve-issues
Source: https://github.com/FradSer/dotclaude/tree/main/github/skills/resolve-issues
Command: npx skills add https://github.com/FradSer/dotclaude --skill resolve-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates GitHub issue resolution by coordinating isolated Git worktrees with a disciplined TDD workflow, reducing context switching and merge conflicts.

Core Features & Use Cases

Isolated worktrees for each issue to keep development separate from main branches.
Test-driven development cycle (red-green-refactor) with explicit review steps.
Atomic commits and PR messages that auto-reference and close issues.
Enforced conventional commit style and PR discipline to maintain code quality.

Quick Start

Activate the resolve-issues skill for a new issue, create a dedicated worktree, write a failing test, implement the fix, refactor, and push a PR that closes the issue.

Frequently Asked Questions about resolve-issues

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate GitHub issue resolution with isolated git worktrees?▼

Automating GitHub issue resolution with isolated git worktrees involves creating a dedicated worktree per issue, running a TDD cycle, and pushing an atomic commit PR. This keeps development separate from main branches and enforces conventional messaging.

What is the TDD red-green-refactor cycle for GitHub pull requests?▼

The TDD red-green-refactor cycle for GitHub pull requests is a process of writing a failing test, implementing the fix, and refactoring. It enforces atomic commits and conventional PR messaging that auto-reference and close the originating issue.

How do I keep GitHub issue changes isolated using git worktrees?▼

To keep GitHub issue changes isolated, use git worktrees to create a separate working directory for each issue. This prevents context switching and merge conflicts by keeping development separate from your main branch.

Does this issue resolution workflow require dependencies to manage atomic commits?▼

No dependencies are required to manage atomic commits in this workflow. The process guides developers through issuing worktrees, tests, and PR workflows natively using git and GitHub.

What is the best way to auto-close GitHub issues with pull request keywords?▼

The best way to auto-close GitHub issues is by enforcing conventional PR messaging and atomic commits with auto-closing keywords. The workflow applies these keywords automatically when pushing the PR that resolves the issue.