fix-issue

Implement GitHub issues using a strict TDD cycle with local validation.

2|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/vultuk/coding-agents --skill fix-issue-vultuk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-issue
Source: https://github.com/vultuk/coding-agents/tree/main/skills/fix-issue
Command: npx skills add https://github.com/vultuk/coding-agents --skill fix-issue-vultuk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of fixing GitHub issues by implementing a strict Test-Driven Development (TDD) workflow and performing local validation, ensuring code quality before user intervention.

Core Features & Use Cases

  • Issue Implementation: Addresses specific GitHub issues by writing and running tests, implementing code, and refactoring.
  • Local Validation: Ensures code changes pass tests, linting, type checks, and builds locally.
  • TDD Workflow: Follows a RED -> GREEN -> REFACTOR cycle for robust development.
  • Use Case: When a GitHub issue is reported, use this Skill to automatically implement the fix, test it thoroughly, and prepare it for your review without committing or creating a pull request.

Quick Start

Use the fix-issue skill to implement GitHub issue number 123.

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 Test-Driven Development automatically?

This workflow automates issue implementation by extracting requirements, mapping the codebase, and running a strict RED-GREEN-REFACTOR TDD cycle to ensure code passes tests, linting, type checks, and builds before manual Git handoff.

What is the RED-GREEN-REFACTOR cycle for implementing code from issues?

The RED-GREEN-REFACTOR cycle is a strict TDD methodology where you first write failing tests for the GitHub issue requirements, implement the code to make tests pass, and then refactor while ensuring local validation like linting and type checks succeed.

Does this TDD workflow automatically create pull requests for GitHub issues?

No, the TDD workflow does not automatically commit code or create pull requests. It performs local validation and provides a handoff summary for manual Git and PR operations, ensuring you maintain control over repository changes.

Can I run local validation like linting and type checks during issue implementation?

Yes, the issue implementation process includes local validation that ensures code changes pass tests, linting, type checks, and builds before providing a handoff summary for manual review.

What's the best way to ensure code quality when addressing GitHub issues?

The best way to ensure code quality is by following a strict TDD workflow that scans for secrets, enforces passing tests, linting, and type checks, and verifies builds locally before you manually commit the issue fix.

Do I need to provide issue details manually for TDD code implementation?

No, you do not need to provide issue details manually. The process automatically extracts requirements from the GitHub issue details and maps the existing codebase to understand the context before starting the TDD cycle.