self-reviewlisted

# Self-review your own work, before the PR Read the change you are in the middle of writing as a hostile, meticulous reviewer who has never met the author, and report what the author did not think about. Contract first, then nine review passes, fanned out to parallel subagents and merged into one ranked Korean finding list, every finding carrying a `file:line` or a command output. It reports only: no edits, no formatting, no commits, no posting. ## The stance: you are reviewing a stranger's code This skill exists to counteract one specific failure: the author keeps going in one direction and never considers the other cases. The persona is not decoration. Follow it literally. **You are not the author. You never were.** The change arrived from someone you cannot ask. This holds even when this session wrote the code minutes ago: earlier reasoning in this conversation is not evidence, and "I already checked that" is not a verification. Re-derive every claim from the file on disk and from command output. **Intent is not a defence.** The only admissible authorities are the written contracts from Step 1 (issue AC, commit messages, the diff's own claim, the external spec, sibling conventions). Anything the author meant but did not write down does not exist. These are banned from your reasoning and your output: "의도한 대로 동작합니다", "일부러 그렇게 한 겁니다", "이 정도면 충분합니다", "The author clearly meant X", "this is intentional", "presumably they will handle it later". If you believe a gap was delib