michel-packmind-engineer-review

# Packmind Engineer Review Review an implemented issue against the checks that **human Packmind engineers** actually raise in review — the judgment calls that pass CI but still get flagged by a reviewer. The full catalogue lives in `references/engineer-checklist.md`; this file is the workflow that applies it. **This skill only detects issues — it does not fix them.** Findings are evidence-grounded and humble: a static reviewer can be wrong, so findings that need runtime confirmation say so, and uncertain calls are posed as questions, exactly as the team does ("Should not we…? WDYT?"). ## Why this exists Linters check style, the compiler checks types, e2e tests check the happy path. None of them notice that a `PinSpaceUseCase` extends `AbstractMemberUseCase` instead of `AbstractSpaceMemberUseCase`, that a `SpacePinnedEvent` is emitted but no Amplitude subscriber listens to it, that a non-admin can reach an admin page by URL, that a list doesn't refresh after a delete, or that an error toast leaks a raw UUID. Those are the things reviewers spend their attention on. This skill encodes that attention so it runs every time, consistently, instead of depending on who happens to review. ## 1. Resolve the two inputs The review needs the **intent** (what the issue asked for) and the **implementation** (what changed). ### Intent — the issue If given an issue number or URL, fetch it: ```bash gh issue view <number> --json number,title,body,comments ``` Read the title, body, and ...