Shipping and code review
Requirement fidelity, useful tests, production readiness, and release communication.
Why this collection exists
Turn ‘the code is done’ into a release whose behavior and recovery path are understood.
Prompts
Use these directly when the moment calls for a focused process.
Review a pull request against its specification
Separate implementation quality from whether the change fulfills its actual contract.
Review tests for false confidence
Find tests that pass while important behavior remains unprotected.
Plan a controlled release
Sequence deployment, observation, rollback, and communication around a consequential change.
Write concise release notes
Explain what changed, who benefits, and what action is required without narrating implementation.
Skills
Install these when the discipline should remain available across sessions.
Code Review
Reviews a change independently for engineering standards and specification fidelity.
Test-Driven Development
Runs a focused red–green–refactor loop one vertical behavior at a time.
Handoff
Compacts active work into a continuation document another developer or agent can reliably resume.
Workflows
Follow these when the work spans several distinct stages.
Review a pull request thoroughly
Review the change on two axes—engineering quality and fidelity to the promised behavior.
Prepare a consequential production release
Coordinate compatibility, deployment, observation, rollback, communication, and follow-up before traffic is exposed.
Hand off long-running agent work
Preserve objective, authoritative progress, decisions, and verification so another session can continue without drift.