skills.rest
ab300819
ab300819COMMUNITY
Explore all skills by this author →
GitHub

devdocs-bugfix

Automate a test-first bug fixing workflow with regression tests and traceability.

Updated Aug 23, 2026
Search Tags:#workflow#logs#regression#traceability#bugfix#test-first
One-click install
npx skills add https://github.com/ab300819/skills --skill devdocs-bugfix
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: devdocs-bugfix
Source: https://github.com/ab300819/skills/tree/main/devdocs-bugfix
Command: npx skills add https://github.com/ab300819/skills --skill devdocs-bugfix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bug reports often lead to vague fixes and vague documentation. This Skill enforces a test-first bug fixing workflow that requires reproducing the issue with a failing test, implementing a minimal fix, and preserving a clear regression record.

Core Features & Use Cases

  • Failing tests drive fixes: Write a failing unit/integration/e2e test that reproduces the bug before making changes.
  • Regression protection: Add regression tests and update the bugfix log to prevent reintroductions.
  • End-to-end traceability: Link bug fixes to related features or requirements and document decisions.
  • Structured collaboration: Coordinate with testing, coding, and documentation tasks to close the bug efficiently.

Quick Start

Describe the bug to the Skill, generate a failing test, implement a minimal fix, and run the regression suite to verify.

Frequently Asked Questions about devdocs-bugfix

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

FAQPage Schema
How do I fix a bug using a test-first workflow?▼

A test-first workflow requires reproducing the issue with a failing test, implementing a minimal code fix, and adding regression tests to verify the solution and prevent future reintroductions.

How do I ensure traceability for bug fixes across multiple modules?▼

Bug fix traceability is maintained by linking fixes to related features and documenting decisions in a detailed log like 05-bugfix-log.md, ensuring every fix maps to BUG-XXX identifiers across single or multi-module projects.

What is the best way to prevent bug regressions after a fix?▼

Preventing regressions involves adding regression tests that verify the fix and updating the bugfix log, which preserves a clear record of the issue, the failing test, and the applied code changes.

Does this test-first bug fixing process work for multi-module projects?▼

Yes, the test-first bug fixing process applies to user-reported bugs across both single and multi-module projects, coordinating testing, coding, and documentation tasks to close the bug efficiently.

Why should I reproduce a bug with a failing test before fixing code?▼

Reproducing a bug with a failing test before fixing code enforces a structured workflow that proves the issue exists, guides the minimal fix, and provides automated regression protection against future reintroductions.

Related Skills

Explore More Software Engineering Skills→
greptileaigreptileai

reproduce-bug

Generate failing regression tests from Linear ticket bug reports.

Official
Advanced
leonanpereirapintoleonanpereirapinto
1

executar-bugfix

...

Community
Advanced
cubetribecubetribe
45

workflows

Coordinate multi-agent software development workflows for feature implementation, bug fixes, and API changes.

Community
Advanced
freedomw1987freedomw1987
2

regression-guard

Enforce regression tests, root cause documentation, and RG-XXX code markers for bug fixes.

Community
Advanced