Menu
Checklist for detecting regressions after changes
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
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
Systematic approach to identifying, analyzing, and fixing bugs
| name | regression-checklist |
| description | Checklist for detecting regressions after changes |
| license | MIT |
## Regression Check: [PR/Change]
### Tests Run
- [ ] Unit tests: X passing
- [ ] Integration tests: X passing
- [ ] E2E tests: X passing
### Issues Found
| Issue | Severity | Status |
|-------|----------|--------|
| [Description] | [High/Med/Low] | [Fixed/Open] |
### Sign-off
- [ ] All regressions addressed
- [ ] Ready for merge