Skip to content
Back to skills

Opencode Review

ASecurity

Code review via OpenCode — review uncommitted changes, branches, or commits

  • 9 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added May 27, 2026
data-aibashsqlcode-reviewgitsecurity

Works with

  • claude code
  • cli

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add cukas/claudes-ai-buddies --skill opencode-review --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Opencode Review?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Opencode Review
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/cukas-opencode-review/badge)](https://www.skillsdirectory.com/skills/cukas-opencode-review)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: opencode-review
description: Code review via OpenCode — review uncommitted changes, branches, or commits
---

# /opencode-review — Code Review via OpenCode

Get a code review from OpenCode CLI. Reviews uncommitted changes by default, or specify a branch or commit.

## How to invoke

Run the wrapper script via Bash. **IMPORTANT:** OpenCode can take 3-6 minutes depending on the model and task complexity. You MUST set the Bash tool's `timeout` parameter to `420000` (7 minutes) to prevent Claude Code from killing the process before OpenCode finishes.

```bash
bash "${CLAUDE_PLUGIN_ROOT}/scripts/opencode-run.sh" \
  --prompt "Additional review instructions (optional)" \
  --cwd "/path/to/repo" \
  --mode review \
  --review-target "uncommitted"
```

Then read the output file and present the review to the user.

## Step-by-step workflow

1. **Determine what to review:**
   - No arguments → review uncommitted changes (`--review-target uncommitted`)
   - User specifies a branch → `--review-target branch:branch-name`
   - User specifies a commit → `--review-target commit:SHA`
2. **Determine working directory.** Must be inside a git repository.
3. **Build the prompt.** The wrapper automatically fetches the diff and builds a review prompt. If the user provides extra instructions (e.g., "focus on security"), pass them as `--prompt`.
4. **Run opencode-run.sh** with `--mode review` via the Bash tool.
5. **Read the output file** using the Read tool.
6. **Present the review** to the user. Frame it as "OpenCode's code review:" with clear sections.
7. **Add your own perspective** if you see issues OpenCode missed, or agree with specific points.

## Options

| Flag | Default | Description |
|------|---------|-------------|
| `--prompt` | (optional) | Extra review instructions |
| `--cwd` | current dir | Working directory (must be a git repo) |
| `--mode` | `review` | Always `review` for this skill |
| `--review-target` | `uncommitted` | What to review |
| `--timeout` | from config (360s) | Max seconds to wait |
| `--model` | from config | Override the model (format: `provider/model`) |

## Review targets

| Target | Flag | Example |
|--------|------|---------|
| Uncommitted changes | `--review-target uncommitted` | `/opencode-review` |
| Branch diff | `--review-target branch:NAME` | `/opencode-review branch:feature/auth` |
| Specific commit | `--review-target commit:SHA` | `/opencode-review commit:abc1234` |

## Example invocations

- `/opencode-review` — review all uncommitted changes
- `/opencode-review branch:main` — review diff from main to HEAD
- `/opencode-review commit:a1b2c3d` — review a specific commit
- `/opencode-review "focus on security and SQL injection"` — review with extra instructions

## Rules

- **Always verify we're in a git repo** before running. If not, tell the user.
- **If no changes exist**, tell the user there's nothing to review instead of sending an empty diff.
- **Present both perspectives** — show OpenCode's review, then add your own observations.
- **Don't auto-apply suggestions** — present findings and let the user decide what to fix.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.