fix-issue

Reproduce, analyze, and fix software bugs with structured diagnostics and tests.

1|Updated Oct 19, 2025
One-click install
npx skills add https://github.com/AcidicSoil/lms-llmsTxt --skill fix-issue-acidicsoil
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fix-issue
Source: https://github.com/AcidicSoil/lms-llmsTxt/tree/main/.claude/skills/fix-issue
Command: npx skills add https://github.com/AcidicSoil/lms-llmsTxt --skill fix-issue-acidicsoil

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill guides teams to reproduce, diagnose, and fix bugs through a structured, evidence-based workflow that reduces time to resolution and minimizes regressions.

Core Features & Use Cases

  • Reproduction planning: convert a bug report into a repeatable failing scenario.
  • Root-cause analysis: identify the underlying cause with structured diagnostics and tests.
  • Safe fixes & validation: implement minimal changes and verify with targeted tests, then document the changes.

Quick Start

Reproduce a reported bug and craft a minimal failing test to guide the fix.

Frequently Asked Questions about fix-issue

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

FAQPage Schema
How do I find the root cause of a software bug?▼

To find the root cause of a software bug, you need a structured workflow that reproduces the issue and applies evidence-based diagnostics. This approach systematically isolates the underlying failure point to guide accurate fixes.

What is the best way to reproduce a reported test failure?▼

The best way to reproduce a test failure is to convert the bug report into a repeatable failing scenario. This structured reproduction planning ensures the issue is consistently replicated before attempting any code changes.

How do I implement a minimal fix for a production bug?▼

To implement a minimal fix for a production bug, apply safe fixes that change only what is necessary after root-cause analysis. This minimizes regressions by validating the targeted changes with specific tests.

Can I use this approach for investigating production bugs?▼

Yes, you can use this approach for investigating production bugs. The structured workflow applies to resolving reported issues and analyzing test failures, supporting thorough root-cause analysis in production environments.

Why do I need to document changes after debugging?▼

You need to document changes after debugging to record the root-cause analysis and the minimal fixes applied. This maintains team context, reduces future debugging time, and provides references for validation.