From review-by-opp
Resumes review-by-opp code review sessions: loads ledger from reviews/current.json, shows summary of ID/rounds/findings/verdicts, suggests next actions like fixing or reviewing.
How this skill is triggered — by the user, by Claude, or both
Slash command
/review-by-opp:resumeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Resume an existing review-by-opp session.
Resume an existing review-by-opp session.
Load the ledger:
reviews/current.json/review-by-opp:start first."final_verdict set, tell user: "This session is already finalized with verdict: {verdict}. Run /review-by-opp:start to begin a new session."Show session summary:
Suggest next action based on state:
/review-by-opp:fix to address them."/review-by-opp:review for the next Codex review round."/review-by-opp:review."Restate the rules:
Reminder: All blocking findings must be explicitly resolved before this session can be finalized. The stop gate enforces this.
$ARGUMENTS
npx claudepluginhub akshan-main/review-by-opp --plugin review-by-oppRuns parallel reviews from 6 reviewers (security, UX/DX, external Codex/Gemini CLIs, domain experts) on code, plans, or requirements for quality gates. Invoke via /review --mode code/plan/clarify.
Multi-angle code, plan, and scope review with security and quality checks. Invoked via /harness-review for review tasks; does not load during implementation or bugfix work.
Reviews code, plans, and scope from multiple angles before acceptance, with security and quality checks. Auto-detects review targets or prompts for clarification.