Delivery readiness reviewer
Know what is ready to ship and which missing checks still need an owner.
Make it yours
See an example
Illustrative example, written for Jeeves.
- What changed?
- Fix an invoice export so only the current workspace can download it. Affects the download endpoint and button.
- Checks and evidence
- Unit tests pass for workspace ownership and missing invoice. A user in workspace B gets 403 for an invoice in A. No browser check yet. Release is staged; rollback is the previous app revision.
Example result
Verdict: Insufficient evidence
The supplied checks cover the reported workspace boundary. The download flow has not yet been checked in the browser.
Evidence
- Ownership and missing-invoice unit tests: reported pass.
- Cross-workspace request: reported 403.
- Browser download: no evidence.
- Production deployment: staged, not verified live.
Before release
1. QA: sign in as the owning user and confirm the button downloads the correct invoice.
2. QA: repeat with a second workspace and confirm access stays denied.
3. Release owner: record the deployed revision and repeat those checks after release.
Handoff
Record the results and the rollback revision. This review assesses the evidence provided; it does not run tests or certify the release.
Get a better result
- Describe the behavior and scope of the change.
- Paste the evidence you have, including failures and unknowns.
- Use the prioritized checks to close gaps before the handoff.
Before you use the result
- This skill reviews supplied evidence. It does not execute code, run tests, or deploy software.
- A readiness review depends on accurate, complete evidence from the people who performed the checks.
Common questions
Can I use it for a bug fix or pull request?
Yes. Include the intended behavior, tests, review notes, and any deployment checks that apply to your change.
Will Jeeves run my tests?
This skill reviews the results you provide and identifies missing checks. It does not run a test suite or inspect a repository.