Files
opencode-primer/.opencode/commands/review.md
Wesam Abousaid 5ce285d088 feat(.opencode): worked-example agents, commands, plugins, skills
This repo doubles as a fully-configured OpenCode project so readers can
see real files instead of abstract format docs.

Agents (.opencode/agents/, OpenCode YAML + markdown body):
- code-reviewer.md — read-only subagent, glob-gated bash perms,
  Severity/Where/Why/Fix output format. Rewrites the pre-refactor file
  which used incorrect frontmatter shape (no YAML, claude-sonnet-4.6
  as bare ID, made-up tool keys).
- security-auditor.md — OWASP-focused review subagent, deny edit,
  ask bash, CWE-aware output template.

Commands (.opencode/commands/):
- review.md, pr.md, test.md, optimize.md — uses real placeholders
  ($ARGUMENTS, @file, !shell), points the right agent at each task.

Plugins (.opencode/plugins/):
- protect-secrets.js — blocks tool calls touching .env*, secrets/,
  credentials*, SSH keys, .npmrc, .pypirc. Pure JS, no deps.
- audit-log.js — appends one JSON line per successful tool call to
  .opencode/audit.jsonl (also added to .gitignore).
- README.md — how to install/disable, sample audit-log line, link to
  docs/plugins.md.

Skills (.opencode/skills/git-release/SKILL.md):
- Proper folder-with-SKILL.md format. Trigger-shaped description so the
  model actually loads it when the conversation touches release prep.
2026-05-18 19:59:56 +02:00

936 B

description, agent
description agent
Run a code review on changed files (or a path you pass) plan

Run a code review with these inputs:

  • Scope: $ARGUMENTS if provided, otherwise the current branch's diff vs main.
  • Changed files (always check):

!git diff --name-only main...HEAD

For each changed file, evaluate (in this order):

  1. Correctness — bugs, race conditions, broken control flow.
  2. Security — input validation, auth, secrets, OWASP Top 10.
  3. Performance — N+1 queries, blocking I/O, unbounded loops.
  4. Maintainability — naming, duplication, missing tests.

Output one entry per finding using this format:

[Severity] <summary>
  Where: <file:line>
  Why:   <one sentence>
  Fix:   <concrete snippet or instruction>

End with a one-line verdict: LGTM, Approve with comments, or Changes requested.

Do not edit any files in this command — leave the implementation to the developer.