fix-issue

Reads GitHub issue details, implements a minimal fix with tests, and commits referencing the issue number.

1|1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/bettercallzaal/ZAOOS --skill fix-issue-bettercallzaal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fix-issue
Source: https://github.com/bettercallzaal/ZAOOS/tree/main/.claude/skills/fix-issue
Command: npx skills add https://github.com/bettercallzaal/ZAOOS --skill fix-issue-bettercallzaal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reads a GitHub issue, implements a minimal, safe fix, writes tests, and commits referencing the issue number to streamline issue resolution.

Core Features & Use Cases

  • Read issue details and comments to understand the root cause.
  • Propose and apply a minimal fix that aligns with project conventions.
  • Run lint/build/tests and prepare a clean, conventional commit referencing the issue.

Quick Start

Call the fix-issue skill with the issue number to fix; it reads the issue, implements the fix, writes tests, and prepares a commit referencing the issue.

Frequently Asked Questions about fix-issue

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

FAQPage Schema
How do I automate GitHub issue fixes with tests and commits?▼

To automate GitHub issue fixes, this skill reads issue details and comments, applies a minimal code change, runs lint and tests, and prepares a conventional commit referencing the issue number. It streamlines resolving bug or feature requests across common codebases.

Can I use this to generate conventional commits that close GitHub issues?▼

Yes, you can generate conventional commits that close GitHub issues. The skill prepares a clean commit message formatted as fix(feature): description (closes #123), ensuring the patch directly references the original issue number for automated tracking and resolution.

Do I need to provide issue details manually for the fix to work?▼

No, you do not need to provide issue details manually. The skill automatically reads the GitHub issue details and its comments to understand the root cause, then proposes and applies a minimal fix that aligns with your project conventions.

What's the best way to ensure a code fix passes lint and tests before committing?▼

The best way to ensure a code fix passes lint and tests is to run them before committing. This skill automatically executes lint, build, and test checks after implementing the fix, preparing a clean commit only when validation succeeds to maintain codebase stability.

Does this approach work for both bug fixes and feature requests on GitHub?▼

Yes, this approach works for both bug fixes and feature requests on GitHub. It is applicable to any issue where a minimal, well-tested patch is preferred, reading the issue context to implement a safe code change across common codebases.