Menu
TDD-based workflow for fixing bugs and defects. Use when investigating, reproducing, and resolving reported issues or unexpected behavior.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Post-task checklist that runs after every agent task that makes essential changes to code, documentation, scripts, or configuration. Covers version bumping, release-notes update, and commit-text proposal. Applied automatically — the agent does not need to be asked.
REST API skill that provides naming conventions and best practices for REST API development.
Common rules for Angular code development. These guidelines apply to components, services, modules, dependency injection, and reactive patterns.
Common rules for TypeScript code development. These guidelines apply to interfaces, types, error handling, async patterns, dependency injection, and module structure.
Common rules for code development that apply across all project types (libraries, CLI tools, services, etc.). Covers development workflow, requirements clarity, bug-fix workflow, logging, coding style, testing discipline, version management, and commit conventions.
Workflow for implementing new features and processing issues. Use when adding new functionality, implementing requirements, or processing feature requests.
| name | bug-fixing |
| description | TDD-based workflow for fixing bugs and defects. Use when investigating, reproducing, and resolving reported issues or unexpected behavior. |
| metadata | {"author":"vsirotin","version":"1.0"} |
Note: This skill is based on common-development. Read the origin document first for complete development rules.
When fixing a bug, always follow this order:
Write a failing unit test — Create a test that fails because of the bug.
Confirm the test fails — Run the test to verify it fails, ensuring the test correctly captures the defect.
Fix the code — Implement the minimal fix to resolve the bug.
Confirm the test passes — Run the test to verify it passes. Small adjustments to the implementation or test may be needed, but reducing the number of tests or skipping them should be done only after careful consideration of the consequences.
Report the result — Document the fix.
These rules from common-development also apply:
