A focused single-lens code review that hunts correctness bugs only — logic errors, off-by-one, inverted conditions, broken invariants, wrong state transitions, null/None/nil mishandling, and the unhandled branch the author never ran. For each suspected bug it hand-traces (and reproduces where it can) before asserting, then reports it with file:line, severity, why-it-matters, and a concrete fix. Run it alone for a sharp pass, or compose it with security/performance/etc. — it deliberately does not duplicate grill's exhaustive all-lens sweep.
EnglishGuidelines (not strict rules) for writing an excellent Jira story. Use to suggest a rewrite and to review an existing story. PO-level — frame value and acceptance, stay out of technical implementation.
EnglishSummarize and assess a product story (Jira/Confluence) from a Product Owner lens — value, clarity, scope, and acceptance-criteria completeness. Stay at product altitude, not implementation.
EnglishMap a product story to the actual codebase — related repos/modules, functionalities touched, integration/contract points, data impact, and technical risks. Inspect the working directory; cite real file paths and line numbers.
EnglishSurface the fewest, sharpest clarifying questions that make a story unambiguous. High-leverage only, categorized, each with why it matters. Not over-defensive.
EnglishTurn a refined product story into a superpowers-style implementation plan — an ordered list of small, independently-verifiable tasks. Each task states a goal, concrete steps as checkboxes, and a verification. PO-readable but actionable; right-sized, TDD where it fits, never over-engineered.
EnglishDraft readable, right-sized test cases for a story — happy path plus meaningful validations and realistic errors. Not over-defensive. Plain language a PO can approve and a dev can implement against.
English
AGENT SKILLS ATLASIncludes Correctness Review, Jira Story Writer, Po Story Overview, and other workflows.
Claude Code
Codex
Cursor
GitHub Copilot
Gemini CLISupported by the Atlas install prompt. Skill-specific requirements vary.
Pack stats
What’s included
Correctness Review
A focused single-lens code review that hunts correctness bugs only — logic errors, off-by-one, inverted conditions, broken invariants, wrong state transitions, null/None/nil mishandling, and the unhandled branch the author never ran. For each suspected bug it hand-traces (and reproduces where it can) before asserting, then reports it with file:line, severity, why-it-matters, and a concrete fix. Run it alone for a sharp pass, or compose it with security/performance/etc. — it deliberately does not duplicate grill's exhaustive all-lens sweep.
Jira Story Writer
Guidelines (not strict rules) for writing an excellent Jira story. Use to suggest a rewrite and to review an existing story. PO-level — frame value and acceptance, stay out of technical implementation.
Po Story Overview
Summarize and assess a product story (Jira/Confluence) from a Product Owner lens — value, clarity, scope, and acceptance-criteria completeness. Stay at product altitude, not implementation.
Story Architecture Overview
Map a product story to the actual codebase — related repos/modules, functionalities touched, integration/contract points, data impact, and technical risks. Inspect the working directory; cite real file paths and line numbers.
Story Clarifying Questions
Surface the fewest, sharpest clarifying questions that make a story unambiguous. High-leverage only, categorized, each with why it matters. Not over-defensive.
Story Task Breakdown
Turn a refined product story into a superpowers-style implementation plan — an ordered list of small, independently-verifiable tasks. Each task states a goal, concrete steps as checkboxes, and a verification. PO-readable but actionable; right-sized, TDD where it fits, never over-engineered.
Story Test Cases
Draft readable, right-sized test cases for a story — happy path plus meaningful validations and realistic errors. Not over-defensive. Plain language a PO can approve and a dev can implement against.
Quick start
- Choose your skills. Select individual skills above, or choose the entire pack.
- Copy the install prompt. Use Copy install prompt above the list.
- Send it to your agent. Paste into your coding agent’s chat. Your agent reviews the source and guides the setup.
Try it with your agent
After installation, start with a request like:
Use the Correctness Review skill to help with my task.
Ask me for the context you need before getting started.Requirements & license
- A coding agent that can access your project files and install skills.
- Your agent checks each skill’s instructions, dependencies, and permissions during setup.
- Reported license for the skills shown: MIT. The author’s terms apply.