skills.rest
tercel
tercelCOMMUNITY
Explore all skills by this author →
Website𝕏@tercelyiGitHub

fixbug

Diagnose software bugs by tracing root causes across code, tasks, plans, and requirements.

5|Updated Feb 13, 2026
Search Tags:#tdd#debugging#documentation#root cause analysis#bug fixing#trace-back
One-click install
npx skills add https://github.com/tercel/code-forge --skill fixbug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fixbug
Source: https://github.com/tercel/code-forge/tree/main/skills/fixbug
Command: npx skills add https://github.com/tercel/code-forge --skill fixbug

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill systematically diagnoses and resolves bugs by tracing their root cause back to the originating document (code, task, plan, or requirement), ensuring fixes are comprehensive and documentation stays synchronized.

Core Features & Use Cases

  • Root Cause Analysis: Identifies if a bug stems from code, task descriptions, planning flaws, or requirement gaps.
  • Interactive Trace-back: Guides the user through confirming upstream document updates needed to fix the bug.
  • TDD Fixes: Implements code changes and regression tests using Test-Driven Development.
  • Document Synchronization: Updates affected tasks, plans, or feature documents to reflect the fix.
  • Use Case: A user reports a critical bug in the login feature. The skill identifies the root cause as a flaw in the original feature requirement document, updates the requirement, fixes the code, and ensures all related documentation is consistent.

Quick Start

Use the fixbug skill to debug the login page returning a 500 error.

Frequently Asked Questions about fixbug

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 across code and documentation?▼

Root cause analysis for software bugs is performed by interactively tracing the issue back to originating documents like code, task descriptions, plans, or requirements to identify the true source.

How do I fix bugs using Test-Driven Development principles?▼

Bug fixing with TDD involves implementing code changes alongside regression tests, verifying the test initially fails, and then confirming the fix resolves the test while synchronizing upstream documentation.

Why do recurring bugs happen after fixing the code without updating requirements?▼

Recurring bugs often happen because the root cause stems from flaws in task descriptions, planning, or requirement gaps, making interactive trace-back and document synchronization essential for a permanent fix.

What is the best way to synchronize upstream documentation after a bug fix?▼

The best way to synchronize documentation is through interactive trace-back, which identifies affected tasks, plans, and feature documents, updating them to reflect the code changes.

Can I trace a production error back to a specific feature requirement gap?▼

Yes, you can trace a production error back to a requirement gap by scanning project context, associating the error with a specific feature, and executing sub-agents to analyze the originating document.

Do I need to manually scan the entire project context to diagnose a critical bug?▼

No, diagnosing a critical bug requires automated project context scanning and feature association to identify the root cause across code and requirements without manual full-project review.

Related Skills

Explore More Software Engineering Skills→
openyakopenyak
704

project-planning

Decompose requirements documents into dependency-aware task lists with priorities and todo export.

Official
Intermediate
jaisonerickjaisonerick

fix-bugs

Reproduce QA-reported failures with failing tests and apply minimal code fixes.

Community
Advanced
kdlbskdlbs
562

fix

Reproduce bugs, identify root causes, and implement minimal fixes with regression tests.

Official
Intermediate
HiveSpaceTeamHiveSpaceTeam

gitnexus-debugging

Trace errors and analyze code flow with GitNexus.

Official
Intermediate