github/penpot
1
0
Fork 0
mirror of https://github.com/penpot/penpot.git synced 2026-08-23 21:28:38 +00:00
Code Issues Packages Projects Releases Wiki Activity
penpot/.opencode/commands/review.md
Andrey Antukh 0cacf9bd99 ♻️ Rename code-review-and-quality skill to code-review 
Rename skill directory and update all references to follow the
same naming pattern as plan-review.

Simplify review.md command from 138 to 25 lines — remove redundant
content that duplicated what the skills already define. The command
now acts as a thin router; the skills own the methodology.

AI-assisted-by: mimo-v2.5-pro
2026-08-21 12:11:11 +00:00

1.1 KiB
Raw Blame History

Act as a senior software engineer and perform a thorough review.

Instructions

  1. Determine what is being reviewed from the provided context:

    • If it is a plan (implementation plan, design document, task breakdown) → load the plan-review skill.
    • If it is code (diff, PR, code change) → load the code-review skill.

  2. Read AGENTS.md and follow its instructions for finding and reading all related testing documentation from memories before reviewing.

  3. Skip generated files, lockfile-only changes, and unrelated modifications unless they introduce security risks.

  4. Follow the loaded skill's process and produce its output format.

Strong Rules

  1. Do not invent problems. Every finding must be real and actionable.
  2. Do not modify any code and do not create a commit — this command only reviews.
  3. Be specific and constructive. "This could be better" is not helpful — explain why and how.
  4. Prioritize by impact. One structural issue outweighs ten nits.
  5. Missing tests are an issue, not a suggestion. Report as a severity-tagged finding — never as a recommendation.

Context

$ARGUMENTS