ByteTerrace/Puck / .claude/skills/review-passes
review-passes
VerifiedRuns a Puck review pass, findings-only or review-and-fix. Use for review briefs and scope ranges, Codex task flags (--write, --cwd), job status, findings, blockers, follow-up fix branches.
evals/r01-brief-for-a-codex-pass/prompt.md
View on GitHub---
max_turns: 8
allowed_tools: [Read, Glob, Grep, Skill]
---
In the Puck repository, write the brief for a Codex review-and-fix pass over a lane's three commits that change capture readback in `RenderGraphRuntime` (`ReadbackBufferLease`, `CaptureReadbackEpoch`, `ReleaseAfterFence`) for plan `docs/plans/render-readback.md` step `R2`: `a1b2c3d render: lease the readback buffer until its copy completes`, `d4e5f6a render: key the readback epoch by frame`, `0718293 tests: pin the copied pixels`. The lane branch `lane/readback` branched from `c0ffee0` on `features/render` (verified ancestor; `features/render` has since advanced to `feedface`), and the lane's test run (`tests/Puck.Shaders.Tests`, 14 passed, 0 warnings) is green. The lane changes GPU resource lifetimes and a persisted replay tape format (`CaptureReadbackEpoch`), both review-only classes in the hazards page, so it gets an adversarial review. One decision is already taken: `ReadbackBufferLease` is released via `ReleaseAfterFence` only after its completion fence signals.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |