skills.rest
jammindev
jammindevOFFICIAL
Explore all skills by this author →
GitHub

bug

Reproduce software bugs, add failing regression tests, and verify fixes.

Updated Sep 21, 2025
Search Tags:#debugging#root cause#react#bug fixing#django#github issue#regression test
One-click install
npx skills add https://github.com/jammindev/house --skill bug-jammindev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug
Source: https://github.com/jammindev/house/tree/main/.claude/skills/bug
Command: npx skills add https://github.com/jammindev/house --skill bug-jammindev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you handle software bugs end to end: reproduce the issue, isolate the root cause, prevent regressions with a test, and ship a verified fix without masking the underlying problem.

Core Features & Use Cases

  • Deterministic Reproduction: Confirms the bug with a focused test, shell repro, log trace, or browser flow before any code changes.
  • Regression Guardrail: Requires a failing test first so the fix is proven and protected from reoccurrence.
  • Issue-Driven Delivery: Creates and closes a GitHub issue for tracking, then verifies the fix globally before delivery.
  • Use Case: A Django API returns the wrong result after a recent change; this Skill investigates the behavior, adds a failing regression test, applies the minimal fix, and confirms the suite stays green.

Quick Start

Use the bug skill to reproduce the issue, write a failing regression test, fix the root cause, and verify the result end to end.

Frequently Asked Questions about bug

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

FAQPage Schema
How do I fix a Django API bug by finding the root cause instead of just masking it?▼

To fix a React bug and prevent regression, you reproduce the browser flow, write a failing regression test that captures the defect, apply the minimal fix, and verify the build and linters pass globally.

What is the best way to manage GitHub issues when fixing software bugs end to end?▼

The best way to manage GitHub issues during bug fixing is issue-driven delivery: create an issue for tracking, reproduce the defect, push a verified fix with a regression test, and close the issue after global validation.

Why do I need a failing regression test before fixing a bug?▼

You need a failing regression test before fixing a bug because it acts as a guardrail, proving the defect exists deterministically and ensuring the fix is validated and protected from future reoccurrence.

Does this bug fixing workflow work for both frontend and backend defects?▼

Yes, this bug fixing workflow applies to backend, frontend, and full-stack defect workflows by isolating the root cause using focused tests, shell repros, log traces, or browser flows before applying a safe fix.

How do I reproduce a software bug deterministically before changing code?▼

To reproduce a software bug deterministically, confirm the issue with a focused test, shell repro, log trace, or browser flow before making any code changes, ensuring the root cause is accurately isolated.

Related Skills

Explore More Software Engineering Skills→
dropseeddropseed
1.0k

plain-bug

Collect bug details and create a GitHub issue via gh CLI.

Official
Intermediate
softmgsoftmg

refactor-workflow

Orchestrate symbol-aware refactors with linter and test verification.

Official
Advanced
summarybotngsummarybotng
2

regression-testing

Automate change-based and risk-based regression test selection with impact analysis.

Official
Advanced
mwathibenmwathiben

typescript-review

Review TypeScript and JavaScript diffs against Metabase coding standards.

Community
Intermediate