do-issue-fix

Guide software issue fixes with minimal changes and design oversight.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/purefunctions/my-agent-config --skill do-issue-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: do-issue-fix
Source: https://github.com/purefunctions/my-agent-config/tree/main/skills/skills/do-issue-fix
Command: npx skills add https://github.com/purefunctions/my-agent-config --skill do-issue-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the process of fixing bugs or issues while ensuring changes are minimal and design-impacting fixes are escalated through the appropriate workflow.

Core Features & Use Cases

  • Problem Description: Users can input a detailed description of the issue they need to fix.
  • Design Discipline: The Skill guides users through understanding the problem, classifying design risk, creating a fix plan, implementing the fix, validating, and maintaining the fix.
  • Use Case: A developer can use this Skill to address a bug in the codebase, following a structured process that includes understanding the problem, classifying the risk, and ensuring the fix adheres to design principles.

Quick Start

Use the 'do-issue-fix' skill to describe the issue you need to fix in the codebase.

Frequently Asked Questions about do-issue-fix

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

FAQPage Schema
How do I fix a software bug with minimal changes to the codebase?

To fix a software bug with minimal changes, you should follow a structured process of understanding the problem, classifying design risk, planning the fix, implementing, and validating the results to ensure focused code maintenance.

What is the best way to resolve software issues while maintaining design oversight?

The best way to resolve software issues while maintaining design oversight is to classify the design risk of your fix and escalate design-impacting changes through the appropriate workflow before implementation.

How do I classify design risk when planning a bug fix?

You classify design risk when planning a bug fix by evaluating whether the required code maintenance impacts the broader system architecture, ensuring that design-impacting fixes are escalated through the proper workflow.

Do I need to provide a detailed problem description for issue resolution?

Yes, you need to provide a detailed problem description for issue resolution because understanding the problem accurately is the first required step before classifying risk and creating a focused fix plan.

When should I escalate a bug fix instead of implementing it directly?

You should escalate a bug fix instead of implementing it directly when the issue resolution requires changes that impact the system design, requiring escalation through the appropriate workflow to maintain design discipline.