skills.rest
heaptracetechnology
heaptracetechnologyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

find-fix

Reproduce bugs, trace data flow, and verify fixes with regression tests.

13|3|Updated Mar 27, 2026
Search Tags:#debugging#trace#reproduce#root-cause#software-engineering#bug-fix#regression-testing
One-click install
npx skills add https://github.com/heaptracetechnology/heaptrace-skills --skill find-fix-heaptracetechnology
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: find-fix
Source: https://github.com/heaptracetechnology/heaptrace-skills/tree/main/find-fix
Command: npx skills add https://github.com/heaptracetechnology/heaptrace-skills --skill find-fix-heaptracetechnology

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Investigate and debug bugs with a structured flow that moves from understanding to reproduction, tracing root cause, implementing fixes, and verifying regression.

Core Features & Use Cases

  • Structured debugging flow: Understand → Reproduce → Trace → Fix → Verify → Prevent regression.
  • Phase-guided checklists and templates to collect facts, reproduce steps, trace data flow, and write regression tests.
  • Documentation templates for root cause, testing criteria, and prevention.

Quick Start

Follow the FIND & FIX flow to diagnose, reproduce, trace, and verify fixes for a reported bug.

Frequently Asked Questions about find-fix

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

FAQPage Schema
What is the best way to debug a software bug end-to-end?▼

Debugging a software bug end-to-end involves a structured workflow: understand the report, reproduce the issue, trace data flow from UI to database to locate the root cause, apply a minimal fix, and verify with regression tests.

How do I trace the root cause of a bug from the UI to the database?▼

To trace the root cause of a bug, follow the data flow from the UI down to the database. This identifies exactly where the logic breaks, allowing you to determine the minimal fix that preserves existing behavior.

How do I write regression tests after fixing a bug?▼

Write regression tests after fixing a bug by first documenting the exact reproduction steps and environment. Verify your fix against these criteria to ensure no new issues arise across related features before committing.

Can I use a structured debugging workflow for any reported error?▼

Yes, a structured debugging workflow can be applied to any reported error. It guides you from initial understanding and reproduction through to root cause analysis, fixing, and regression prevention using phase-specific checklists.

Why should I determine the minimal fix when resolving a bug?▼

Determining the minimal fix when resolving a bug is crucial because it preserves existing behavior and limits side effects. Verifying this fix with regression tests ensures no new issues are introduced across related features.

Related Skills

Explore More Software Engineering Skills→
Andreicr1Andreicr1

report-bug-ce

Collect bug details and create a GitHub issue for the compound-engineering plugin.

Community
Advanced
first-flukefirst-fluke
218

debug-agent

Diagnose software bugs and propose minimal regression-tested fixes.

Official
Advanced
majedsiefalnasrmajedsiefalnasr

gitnexus-debugging

Trace bugs in a knowledge graph-enabled codebase to identify error origins and affected components.

Community
Advanced
arakitakashiarakitakashi
1

analyze-errors

Delegate error analysis and fix generation to a sub-agent.

Community
Advanced