Reviews build validation, linting/type-checking, target database checks, clinical governance preflight approvals, and environment variables. Use before staging or production releases.
86%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Use this skill for explicitly requested staging or production release readiness. For routine development or PR handoff, use the canonical gate selector. Bare PR publication follows the separate publication route in AGENTS.md and does not invoke readiness work.
Follow AGENTS.md review throttling and docs/codex-review-protocol.md before starting. Do not review opportunistically or mutate files during pure review. After a completed PR review, post one Review record comment on the PR (see Records); never edit the frozen docs/branch-review-ledger.md table.
npm run verify:pr-local for PR handoff confidence. npm run verify:release is reserved for explicit release confidence and requires user approval because it includes provider-backed checks.npm run check:supabase-project is provider-backed. Run it only with explicit user approval, using the repository-designated environment without printing secrets, to confirm the target is PsychSift Production ref sjrfecxgysukkwxsowpy..github/pull_request_template.md..env.local), local debug logs, or keys are present in the git stage.npm run check:production-readiness:ci when readiness or configuration structure is in scope. Before production release or activation, run the bare npm run check:production-readiness in release mode with all applicable clinical, privacy, legal, security and provider approvals. Pending release approvals block release or activation.BigSimmo/PsychSift
0d5a97a
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.