Prompt file imported from MaineK00n/vuls-data-update (
.github/prompts/review.prompt.md). Copyright stays with the author.
/review — Code Review
Review the changes in the current branch against the base branch.
Procedure
Phase 1: Gather Changes
- Determine the base branch from the PR target, or default to
origin/nightly - Get the diff:
git diff <base>...HEAD - List changed files:
git diff --name-only <base>...HEAD
Phase 2: Review
Load and apply these instructions before reviewing:
.github/instructions/review.instructions.md— review checklist and severity classification.github/instructions/go-code.instructions.md— Go code conventions.github/instructions/golden-test.instructions.md— golden test conventions.github/instructions/security.instructions.md— security and prompt-injection guidance
For each changed file, check against those guidelines.
Key areas:
- Deterministic output: Are
Sort()/Compare()updated? Isutil.Writeused? - Backward compatibility: Do type changes break external consumers?
- Golden tests: Are golden files updated? Are new tests added for new functionality?
- Security: No hardcoded secrets, input validation at boundaries, no command injection
- Error handling: Errors wrapped with context, consistent error patterns
Phase 3: Classify Findings
Classify each finding by severity according to .github/instructions/review.instructions.md.
Phase 4: Report
Output a structured report:
## Review Summary
**Verdict**: APPROVE | APPROVE WITH COMMENTS | REQUEST CHANGES
### Findings
#### CRITICAL
- [ ] ...
#### HIGH
- [ ] ...
#### MEDIUM
- [ ] ...
#### LOW
- [ ] ...
### Notes
- ...