bug-fix-planner

Diagnose bug root causes and generate step-by-step TDD-based fix plans.

7|5|Updated Jun 2, 2023
One-click install
npx skills add https://github.com/sjmyuan/prompts --skill bug-fix-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-fix-planner
Source: https://github.com/sjmyuan/prompts/tree/main/skills/bug-fix-planner
Command: npx skills add https://github.com/sjmyuan/prompts --skill bug-fix-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps diagnose the root cause of bugs and generates a detailed, step-by-step plan to fix them using a Test-Driven Development (TDD) approach.

Core Features & Use Cases

  • Root Cause Analysis: Identifies the underlying reason for bugs by analyzing code, tests, and user input.
  • TDD-Based Planning: Creates a structured plan that includes writing tests, confirming failures, fixing code, and verifying the solution.
  • Adaptable TDD: Adjusts the TDD approach based on bug complexity (e.g., simple logic errors, type-related issues, configuration problems).
  • Use Case: When a user reports that a feature is broken, this Skill will analyze the problem, propose a fix strategy, and outline the exact steps to implement it using TDD principles.

Quick Start

Use the bug-fix-planner skill to diagnose and plan a fix for the reported issue with user authentication.

Frequently Asked Questions about bug-fix-planner

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

FAQPage Schema
How do I plan a TDD-based bug fix for unexpected behavior in existing functionality?

To plan a TDD-based bug fix, diagnose the root cause of the unexpected behavior and generate a step-by-step plan covering writing tests, confirming failures, fixing code, and verifying the solution.

What is the best way to diagnose root causes for software defects before fixing code?

The best way to diagnose root causes for software defects is to analyze code, tests, and user input to identify the underlying reason for the bug, then adapt the troubleshooting approach based on bug complexity like logic errors or configuration problems.

How do I structure a test-driven development workflow for troubleshooting reported bugs?

Structure a test-driven development workflow for troubleshooting bugs by creating a detailed plan that includes writing tests to reproduce the defect, confirming test failures, applying the code fix, and verifying the solution works.

Do I need a separate skill to implement code changes generated by this TDD bug fix planner?

Yes, you need a separate skill to implement code changes, because this planner diagnoses root causes and produces a detailed TDD-based fix plan but does not execute the actual code changes itself.

Can this bug fix planner adapt its TDD approach for different types of code defects?

Yes, the bug fix planner can adapt its TDD approach based on bug complexity, adjusting the troubleshooting strategy for simple logic errors, type-related issues, and configuration problems.

When do I need a TDD-based plan for debugging instead of directly patching code?

You need a TDD-based plan for debugging when you want to systematically fix defects by first writing tests to confirm failures, ensuring code quality, and verifying the solution rather than directly patching code blindly.