with one click
bugfix-playbook
Systematic approach to identifying, analyzing, and fixing bugs
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.
Menu
Systematic approach to identifying, analyzing, and fixing bugs
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
| name | bugfix-playbook |
| description | Systematic approach to identifying, analyzing, and fixing bugs |
| license | MIT |
## Bug Analysis: [Bug Title]
### Issue
[Description of the bug]
### Root Cause
[Explanation of why the bug occurs]
### Affected Code
- `file_path:line_number` - [Description]
### Fix Approach
[Description of how to fix]
### Tests to Add
1. [Test case 1]
2. [Test case 2]
Use when code changes require documentation updates. Ensures documentation stays synchronized with code, API, and feature changes. Detects doc drift and maintains consistency.
Use when working with GitHub issues, pull requests, releases, or repository operations. Provides systematic approach to GitHub API interactions via gh CLI.
Use when releasing a new version of the software. Automates version bumping, changelog updates, git tagging, and release creation. Supports both single and dual-repository release workflows.
Use when starting a new feature or project to systematically capture user requirements through Socratic questioning. Creates a requirements document that can be used for design and implementation planning.
Decompose complex tasks into GitHub sub-issues and coordinate workflow
Investigate CI failures systematically and find root causes