Files
Claude-Code-Game-Studios/.claude/docs/director-gates/lp-code-review.md
T
DonchitosandClaude Opus 5.5 b21fa0f7f2 Release 1.1.2 — the default path works end to end
Fix release for 1.1.1: the minimal path end to end, engine commands that
run on Godot, Unity and Unreal, hook warnings you can see, and verdicts
that say when they could not check. Details in CHANGELOG.md; upgrade
steps in UPGRADING.md (v1.1.1 → v1.1.2).

Fixes #67
Fixes #131

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WuJn2FdynEybfL5KC697nJ
2026-09-29 21:32:19 +10:00

24 lines
955 B
Markdown

> Gate definition. The spawning skill passes this file's path to the director agent; the AGENT reads it — the parent session should not.
# LP-CODE-REVIEW — Lead Programmer Code Review
Agent: `lead-programmer` | Model tier: Sonnet
**Trigger**: After a dev story is implemented (`/dev-story`, `/story-done`), or
as part of `/code-review`
**Context to pass**:
- Implementation file paths
- Story file path (for acceptance criteria)
- Relevant GDD section
- ADR that governs this system
**Prompt**:
> "Review this implementation against the story acceptance criteria and governing
> ADR. Does the code match the architecture boundary definitions? Are there
> violations of the coding standards or forbidden patterns? Is the public API
> testable and documented? Are there any correctness issues against the GDD rules?
> Return APPROVE, CONCERNS [specific issues], or REJECT [must be revised before merge]."
**Verdicts**: APPROVE / CONCERNS / REJECT