skills.rest
JotJunior
JotJuniorCOMMUNITY
Explore all skills by this author →
𝕏@jotjrGitHub

bugfix

Map end-to-end data flow before implementing bug fixes.

21|4|Updated Jan 8, 2026
Search Tags:#workflow#debugging#tracing#end-to-end#bugfix#multi-service
One-click install
npx skills add https://github.com/JotJunior/claude-ai-tips --skill bugfix-jotjunior
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bugfix
Source: https://github.com/JotJunior/claude-ai-tips/tree/main/global/skills/bugfix
Command: npx skills add https://github.com/JotJunior/claude-ai-tips --skill bugfix-jotjunior

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structured bug fix protocol designed to eliminate cascading fix-reveal-fix cycles by mapping the full data flow before touching any layer. Stack-agnostic — adapt the commands and layer names to the project you are working in.

Core Features & Use Cases

  • End-to-end data-flow mapping across server and client layers before any change.
  • Parallel-agent investigation for multi-service bugs to coordinate root-cause analysis.
  • Guided steps (trace, verify, plan, implement) to prevent regressive fixes and ensure alignment.

Quick Start

Begin by outlining the affected data flow and perform a full end-to-end trace across all layers before implementing any fix.

Frequently Asked Questions about bugfix

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

FAQPage Schema
How do I stop cascading fix-reveal-fix cycles when debugging multi-service applications?▼

End-to-end tracing maps the full data flow from entry point to data persistence across every layer before touching any code. This systematic bug investigation maps multi-service scenarios and coordinates parallel-agent root-cause analysis to prevent incomplete fixes.

What is the best way to coordinate parallel-agent investigations for multi-service bugs?▼

Parallel-agent investigation coordinates root-cause analysis across multi-service bugs by mapping every layer from entry point to data persistence before applying changes. This guided workflow uses step-by-step tracing and risk-aware planning to prevent regressive fixes.

How do I trace data flow across server and client layers before implementing a bug fix?▼

Trace data flow across server and client layers by following guided steps: trace, verify, plan, and implement. Begin by outlining the affected data flow and performing a full end-to-end trace across all layers before implementing any fix to prevent regressive changes.

Does this debugging workflow work for any tech stack or only specific frameworks?▼

This debugging workflow is stack-agnostic, meaning you adapt the commands and layer names to the specific project you are working in. The structured protocol applies universally across different frameworks to ensure thorough multi-service debugging.

When should I use a systematic bug fix protocol instead of applying direct code patches?▼

Use a systematic bug fix protocol when investigating multi-service scenarios to prevent cascading fix-reveal-fix cycles. Mapping the full data flow from entry point to persistence before applying changes ensures risk-aware planning and thorough debugging.

Related Skills

Explore More Software Engineering Skills→
quangphu1912quangphu1912
1

trace-data-flows

Trace data flows through codebases to detect security vulnerabilities and integrity issues.

Community
Advanced
swghoshswghosh

review

Review bug fixes and tests against root cause and regression proof.

Community
Intermediate
ZpankzZpankz
7

parallel-debug-orchestrator

Coordinate parallel debugging agents to isolate root causes in multi-failure scenarios.

Community
Intermediate
zmh13928433602-syszmh13928433602-sys

agent-tracing

Inspect agent execution snapshots to debug step-by-step LLM interactions.

Community
Advanced