This prompt guides users through a structured process of identifying, reproducing, and fixing bugs in software. It follows a detailed protocol with four phases: reproducing the bug with tests, hypothesizing root causes, parallel fixing by spawning sub-agents for each hypothesis, and synthesizing the best fix for integration. Ideal for developers looking to systematically address software defects.
Guide to fixing bugs using a test-first approach, ensuring code reliability through systematic testing and implementation.
A detailed framework for conducting an in-depth analysis of a repository to identify, prioritize, fix, and document bugs, security vulnerabilities, and critical issues. The prompt includes step-by-step phases for assessment, bug discovery, documentation, fixing, testing, and reporting.
A step-by-step critical thinking debugging skill designed to fix problems directly and ensure they are resolved without causing additional issues.
Full development lifecycle for a Jira ticket. Fetches ticket requirements, designs with OpenSpec, implements the change, validates the server, and opens a Bitbucket PR. Use when starting a new feature or bug fix driven by a Jira ticket.
Collects TODO, FIXME and HACK comments across your codebase, finds the old and risky ones, links them to issues and suggests which to fix, file or delete each sprint.
Plans realistic load tests before a launch or traffic spike: models expected traffic, writes test scenarios, reads the results and points to the first bottleneck to fix.
Watches crash reports for your iOS and Android apps, groups new crashes by root cause, ranks them by how many users and releases they hit, and drafts clear issues with stack traces and repro hints.
