review-by-opp:status
Show current review ledger status including round count, open findings, blocking items, agent configuration, and whether the session can be finalized.
Best use case
review-by-opp:status is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Show current review ledger status including round count, open findings, blocking items, agent configuration, and whether the session can be finalized.
Teams using review-by-opp:status should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/status/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How review-by-opp:status Compares
| Feature / Agent | review-by-opp:status | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Show current review ledger status including round count, open findings, blocking items, agent configuration, and whether the session can be finalized.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
Show the current review-by-opp session status.
## What to do
1. **Load the ledger:**
- Read `reviews/current.json`
- If missing, tell user: "No active session. Run `/review-by-opp:start` first."
2. **Display status table:**
| Field | Value |
|-------|-------|
| Session | `{session_id short}` |
| Round | {current_round} / {max_rounds} |
| Total findings | {count} |
| Open | {open count} |
| Blocking open | {blocking count} |
| Resolved | {resolved count} |
| Review scope | {scope} |
| Can finalize | Yes/No |
| Verdict | {verdict or "in progress"} |
3. **Display agent configuration:**
| Agent | Setting | Value |
|-------|---------|-------|
| Claude | Model | user-controlled |
| Claude | Effort | user-controlled |
| Codex | Config mode | inherited/overridden |
| Codex | Model | {effective model or "default"} |
| Codex | Reasoning | {reasoning effort or "default"} |
4. **If there are blocking reasons, list them.**
5. **Show open findings in compact format:**
- `[open] f-1-abc123 high/bug: Null pointer (src/main.ts:42)`
6. **Show next actions:**
- If can finalize: "Ready to finalize. Run `/review-by-opp:finalize`"
- If blocking findings exist: "Resolve blocking findings with `/review-by-opp:fix`"
- If no review has been run yet: "Run `/review-by-opp:review` to start the first review"
$ARGUMENTSRelated Skills
review-by-opp:start
Start a guarded implementation + review session. Use when beginning work that should be reviewed by Codex before completion. Initializes the review ledger and configures the stop gate.
review-by-opp:review
Run Codex as an independent reviewer against the current diff or changed files. Parses findings into the ledger. Use after making code changes.
review-by-opp:resume
Resume an existing review-by-opp session. Use when returning to a previous review session.
review-by-opp:help
Learn about review-by-opp - what it does, how to use it, and available commands
review-by-opp:fix
Address Codex review findings from the ledger. Shows open findings and guides resolution. Each finding must get an explicit resolution state.
review-by-opp:finalize
Finalize the review session. Only succeeds if all blocking findings are resolved. Emits final verdict.
flutter-dart-code-review
库无关的Flutter/Dart代码审查清单，涵盖Widget最佳实践、状态管理模式（BLoC、Riverpod、Provider、GetX、MobX、Signals）、Dart惯用法、性能、可访问性、安全性和整洁架构。
security-review
Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns.
addressing-pr-review-comments
Address all valid review comments on a PR for the current branch in the streamlit/streamlit repo. Covers both inline review comments and general PR (issue) comments. Use when a PR has reviewer feedback to address, including code changes, style fixes, and documentation updates.
lightning-architecture-review
Review Bitcoin Lightning Network protocol designs, compare channel factory approaches, and analyze Layer 2 scaling tradeoffs. Covers trust models, on-chain footprint, consensus requirements, HTLC/PTLC compatibility, liveness, and watchtower support.
hig-components-status
Apple HIG guidance for status and progress UI components including progress indicators, status bars, and activity rings.
gha-security-review
Find exploitable vulnerabilities in GitHub Actions workflows. Every finding MUST include a concrete exploitation scenario — if you can't build the attack, don't report it.