bugfix

Fix P1/P2 bugs via TDD with pytest, coverage, mypy, and ruff quality gates.

19|Updated Dec 28, 2025
One-click install
npx skills add https://github.com/fall-out-bug/sdp --skill bugfix-fall-out-bug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bugfix
Source: https://github.com/fall-out-bug/sdp/tree/main/.claude/skills/bugfix
Command: npx skills add https://github.com/fall-out-bug/sdp --skill bugfix-fall-out-bug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured and quality-assured process for addressing P1 and P2 bugs, ensuring fixes are robust and well-tested before merging.

Core Features & Use Cases

  • TDD Cycle: Enforces a Test-Driven Development approach (write failing test, implement fix, refactor).
  • Quality Gates: Integrates pytest, code coverage (≥80%), type checking (mypy --strict), and linting (ruff).
  • Branching Strategy: Creates dedicated bugfix branches from develop or feature branches.
  • Use Case: A critical but non-production-impacting bug is reported (P2). This Skill will create a branch, write a test that reproduces the bug, implement the fix, run all quality checks, and prepare the fix for merging into the develop branch.

Quick Start

Use the bugfix skill to address issue ID 002 with the description "Fix login button alignment on mobile".

Frequently Asked Questions about bugfix

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

FAQPage Schema
How do I fix bugs using a TDD cycle with pytest and strict type checking?

To fix bugs with TDD and quality gates, this process writes a failing test to reproduce the issue, implements the fix, and enforces pytest, mypy strict type checking, and ruff linting before merging into the develop branch.

What is the best way to ensure my critical bug fix maintains code quality and passes linting?

The best way to ensure bug fix quality is enforcing quality gates that run pytest for tests, require 80% code coverage, apply mypy strict type checking, and execute ruff linting before the fix is merged.

Can I use this TDD bug fixing process for any priority level issue in my repository?

This TDD bug fixing process is specifically designed for P1 and P2 issues, creating dedicated bugfix branches from develop or feature branches to ensure critical fixes are merged with proper commit messages and issue status updates.

How do I structure my git workflow when fixing a P2 issue via test-driven development?

To structure your git workflow for fixing a P2 issue, the process creates a dedicated branch from develop, uses a TDD cycle to implement the fix, and prepares the merge with proper commit messages and issue status updates.

What happens if my bug fix does not reach 80% code coverage or fails mypy checks?

If a bug fix does not reach 80% code coverage or fails mypy checks, the quality gates will block the merge, requiring you to refactor the fix until pytest, mypy strict, and ruff linting all pass successfully.