A city team wants every clone to get the same /review checklist for pull requests. Where should the command live?
Select an answer to reveal the explanation.
Short Explanation
Want /review on every city laptop after clone? Park it in .claude/commands/ in the repo—version control becomes the distribution truck.
Full Explanation
Team-wide slash commands that every clone should receive belong under .claude/commands/ in the project so version control shares them. A city team that wants the same /review checklist for pull requests should add that command in the project commands folder, not on one developer’s machine.
Why the correct option works: project-scoped commands are distributed by VCS. After clone, every engineer can run /review and get the same civic PR checklist—security, accessibility, migration notes—without re-teaching the ritual orally.
Why the other three fail by concept: keeping /review only in one developer’s user commands folder limits availability to that person. Describing the checklist orally and never creating a slash command loses consistency and agent usability. Storing the command inside a deleted branch that is never pushed means clones never receive it.
Exam caveat: project .claude/commands/ is for shared commands; user commands remain for personal shortcuts. Operational check: commit /review under .claude/commands/, clone fresh, run /review, and confirm the checklist matches across laptops. Shared /review commands encode institutional PR expectations—security, migrations, accessibility—so every city clone runs the same checklist without relying on who remembered the oral version. Keep the command text in git history so checklist changes are reviewable like any other civic policy-as-code artifact.