fix-issue

Automate GitHub issue resolution with a test-driven development workflow.

4|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/kazhou/agents-toolkit --skill fix-issue-kazhou
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-issue
Source: https://github.com/kazhou/agents-toolkit/tree/main/.claude/skills/fix-issue
Command: npx skills add https://github.com/kazhou/agents-toolkit --skill fix-issue-kazhou

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes addressing GitHub issues by driving development with tests first. It helps ensure features are implemented correctly and with verifiable tests before merging.

Core Features & Use Cases

  • Reproduces a GitHub issue workflow by viewing issue details, creating a feature branch, writing tests first, implementing code, and submitting a PR.
  • Enforces test-driven development, ensuring changes are validated by tests before code completion.
  • Applies to bug fixes and feature work started from issues, providing clear traceability and documentation updates.

Quick Start

Use this sequence to fix an issue using TDD: view the issue with gh issue view $ARGUMENTS, create a feature branch with git checkout -b feature/$ARGUMENTS, write tests in tests/, run tests with uv run pytest tests/ -v, implement code to pass tests, prepend session notes to agent_logs/LOG.md, commit and create a PR with git add -A; git commit -m "feat: implement issue #$ARGUMENTS" and gh pr create --fill

Frequently Asked Questions about fix-issue

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

FAQPage Schema
How do I fix GitHub issues using a TDD workflow?

Fixing GitHub issues using TDD involves viewing the issue, creating a feature branch, writing tests first, implementing code to pass, and submitting a pull request for reliable feature delivery.

How do I automate bug fixes from GitHub issues with pytest?

Automating bug fixes with pytest starts by creating a feature branch using the issue number, writing failing tests in the tests directory, running uv run pytest, and implementing code until tests pass before opening a PR.

Do I need Git and GitHub CLI installed to automate issue resolution?

Yes, automating issue resolution requires tooling for Git, GitHub, and test runners like pytest. You need these dependencies to create branches, view issues, run tests, and submit pull requests successfully.

What is the best way to ensure code changes are validated before merging a pull request?

The best way to validate changes before merging is enforcing test-driven development. By writing tests first and implementing code to pass them, you ensure features are verified and documented before completion.

Can I use this TDD approach for both feature work and bug fixes?

Yes, this test-driven development approach applies to both bug fixes and feature work started from GitHub issues, providing clear traceability and documentation updates throughout the branch and pull request lifecycle.