From episteme
Applies a strict review gate before merge, release, or project handoff, checking for correctness, regressions, missing tests, risky assumptions, and deployment issues.
How this skill is triggered — by the user, by Claude, or both
Slash command
/episteme:review-gateThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill after implementation or before a commit/merge boundary.
Use this skill after implementation or before a commit/merge boundary.
Focus on:
Present findings first. If there are no findings, state that clearly and note residual risk.
npx claudepluginhub junjslee/episteme --plugin epistemeReviews and verifies code before merge via triage-first checks (up to 16 parallel agents). Pipeline mode verifies vs plans; general mode for PRs/branches/staged changes. Flags findings only.
Performs code reviews using Codex MCP with severity-grouped findings and a merge gate. Supports fast (diff-only), full (diff + lint/build), and branch review variants.
Reviews code changes for correctness, readability, architecture, security, and performance. Checks lint, type safety, test coverage, and security issues. Use for PRs, audits, or pre-merge reviews.