fix-issue

Automate GitHub issue resolution from planning through testing and merge.

Updated Feb 28, 2026
One-click install
npx skills add https://github.com/wfhanna1/Automated-obs-trigger --skill fix-issue-wfhanna1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-issue
Source: https://github.com/wfhanna1/Automated-obs-trigger/tree/main/.claude/skills/fix-issue
Command: npx skills add https://github.com/wfhanna1/Automated-obs-trigger --skill fix-issue-wfhanna1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates end-to-end GitHub issue resolution, guiding users to understand, plan, implement, test, review, and ship a fix without manual, repetitive steps.

Core Features & Use Cases

  • Understands the issue context by inspecting the GitHub issue with its labels, description, and comments.
  • Plans a minimal, maintainable fix across code, tests, and documentation, then generates a concrete implementation plan.
  • Implements the change in the repository, adheres to code ownership and 12-factor principles.
  • Validates the fix by running tests and ensuring the change meets acceptance criteria before shipping.
  • Facilitates code review and security checks, logging actions for traceability and audit.

Quick Start

Provide the GitHub issue key and run the fix workflow to resolve the issue end-to-end.

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 resolution end-to-end?

You can automate GitHub issue resolution by guiding an agent through understanding context, planning, implementing, testing, reviewing, and shipping a fix. This workflow handles bug fixes and feature improvements across code, tests, and documentation.

What is the best way to plan a minimal fix for a GitHub issue?

Planning a minimal GitHub issue fix involves inspecting issue context, labels, and comments, then generating a concrete implementation plan. The workflow ensures changes adhere to code ownership and 12-factor principles before applying modifications.

Do I need a structured workflow to fix GitHub issues across code and tests?

Yes, resolving GitHub issues with cross-functional changes requires a structured workflow. The process needs issue context, code search, plan generation, change application, test execution, and a formal review and merge process to ensure quality.

Can I enforce code ownership and security checks when automating GitHub issue fixes?

Yes, automating GitHub issue fixes can enforce code ownership and security considerations. The workflow facilitates code review and security checks while logging actions for traceability and audit before merging changes.

How does automated issue triage validate that a fix meets acceptance criteria?

Automated issue triage validates fixes by running tests and ensuring changes meet acceptance criteria before shipping. This testing phase follows implementation and precedes the formal code review and merge process.

What types of GitHub issues can be resolved using an automated fix workflow?

The automated fix workflow resolves software project issues on GitHub requiring cross-functional changes across code, tests, and documentation. Supported scenarios include bug fixes, feature improvements, and workflow optimizations.