Check a Proofpack release candidate before packaging by running tests, validating the candidate, and inspecting the package locally. Compare the source state and command results with the evidence log, then report passed, failed, or unknown checks.
Use when checking whether a Proofpack release candidate has complete local evidence before packaging.
Review the instructions the agent will receive before you install.
Work from the Proofpack project root. Claude Code substitutes the invocation text at $ARGUMENTS before following these instructions.
$ARGUMENTS is empty, set the candidate path to fixtures/release-ready.json.$ARGUMENTS value as one filesystem path. Do not evaluate it as a shell expression.node src/cli.mjs verify "<resolved-candidate-path>" with that literal path as one quoted argument.ISSUE.md and CLAUDE.md.npm test.npm run package:check only when tests and candidate verification pass.git rev-parse HEAD and git status --short. Compare that source state, the observed commands, exit statuses, and runtime version with evidence/PROOF-LOG.md.PASS, FAIL, or UNKNOWN. Name any check that did not run or any worktree change not covered by the recorded fingerprint.Do not run npm publish, docker push, or change the proof log. Package inspection is local. Publication requires a separate user decision and destination credentials.
Return this record:
RELEASE VERIFICATION
Candidate: <path>
Revision: <commit or UNKNOWN>
Tests: PASS | FAIL | UNKNOWN
Candidate contract: PASS | FAIL | UNKNOWN
Package dry run: PASS | FAIL | UNKNOWN
Evidence log match: PASS | FAIL | UNKNOWN
Final status: PASS | FAIL | UNKNOWN
Limits: <unverified runtime or external behavior>
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Evaluate Claude Code agents, skills, and commands with weighted quality criteria. Get scores, readiness grades, template comparisons, and practical improvement suggestions in Markdown or JSON reports to guide reviews before release.
Assess a codebase across seven areas, including exposed credentials, security, dependencies, structure, and tests. Receive category scores, findings tied to file locations, and a prioritized improvement plan with smaller tasks that can be completed quickly.
Measure code patterns such as casts to any or disabled lint rules, then run repeated, targeted edits. Keep changes that improve the chosen metric, revert unsuccessful changes, and track results for each improvement loop.
Generate several separate solutions, compare them against criteria fixed in advance, and verify the selected result through executable checks or an independent reviewer. Keep a proof log documenting candidates, evidence, failures, and remaining limits.
Monitor a live application after deployment and compare it with a saved baseline, a record of its earlier state. Check page responses, loading times, and new errors, flag persistent changes, and produce a per-page health report.
Rebuild project context after clearing a conversation or returning to work. Review recent Git history, uncommitted changes, and TODO markers to get a structured summary of project status and suggested next steps.