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.
Best use case
review-by-opp:fix is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Address Codex review findings from the ledger. Shows open findings and guides resolution. Each finding must get an explicit resolution state.
Teams using review-by-opp:fix 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/fix/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How review-by-opp:fix Compares
| Feature / Agent | review-by-opp:fix | 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?
Address Codex review findings from the ledger. Shows open findings and guides resolution. Each finding must get an explicit resolution state.
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.
Related Guides
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
SKILL.md Source
You are addressing Codex review findings. You are the builder - fix what needs fixing.
## 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. **Show open findings:**
- List all findings with status `open`, grouped by severity (critical first)
- For each, show: ID, severity, category, title, file, line, description, suggested_fix
3. **Address findings one by one:**
For each finding, you MUST do one of these - no exceptions:
a. **Fix it** → Make the code change, then update the finding:
- Set `status` to `fixed`
- Set `resolution_note` to a brief description of what you changed
- The fix must be verifiable (actual file changes, not just claiming it's done)
b. **Mark as won't_fix** → If the finding is intentional or acceptable:
- Set `status` to `wont_fix`
- Set `resolution_note` explaining why
c. **Mark as not_reproducible** → If you cannot reproduce the issue:
- Set `status` to `not_reproducible`
- Set `resolution_note` with your investigation
d. **Mark as needs_context** → If you need more information:
- Set `status` to `needs_context`
- Set `resolution_note` describing what context is needed
e. **Mark as duplicate** → If this duplicates another finding:
- Set `status` to `duplicate`
- Set `duplicate_of` to the other finding's ID
4. **Update the ledger:**
- Write updated findings back to `reviews/current.json`
- Every finding must have a resolution state - you cannot skip any
5. **Report progress:**
- Show how many findings were resolved this pass
- Show remaining open findings
- If blocking findings remain: "Run `/review-by-opp:fix` again or `/review-by-opp:review` for another Codex pass"
- If no blocking findings: "Ready for another review round (`/review-by-opp:review`) or finalize (`/review-by-opp:finalize`)"
**CRITICAL:** You MUST NOT claim "all fixed" unless every finding has an explicit resolution state. The ledger enforces this - hand-waving is not allowed.
$ARGUMENTSRelated Skills
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.
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: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.
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.
gh-review-requests
Fetch unread GitHub notifications for open PRs where review is requested from a specified team or opened by a team member. Use when asked to "find PRs I need to review", "show my review requests", "what needs my review", "fetch GitHub review requests", or "check team review queue".