named-persona-adversarial-review
Code review through the lens of real engineers' documented philosophies (Torvalds, Thompson, Carmack, Kent Beck, Jobs, Cagan). Complements abstract-role adversarial review with named, sourced perspectives. Use when automated review findings feel generic, when a PR has architectural or UX impact, or when the author wants pre-submit hardening beyond standard checks.
Profile →npx skills add alirezarezvani/claude-skills --skill named-persona-adversarial-review --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Named-Persona Adversarial Review > **TL;DR:** Abstract roles find abstract problems. Named engineers with *documented, sourced* philosophies find problems you would actually fix — as long as you cite the real principle and never invent the quote. **Triggers:** "review this PR with real engineers" | "named persona review" | "philosophy-grounded review" ## Example Output ``` CRITICAL [Torvalds]: Special-case error handling at auth.ts:47 duplicates the happy path. Torvalds' documented "good taste" principle: restructure so the special case disappears rather than adding a branch. (confidence: high — TED 2016) WARNING [Thompson]: parseConfig() does three unrelated things; the Unix "do one thing well" principle argues to split it. (confidence: high) NOTE [Jobs]: Error "EACCES:13" leaks an errno at the user surface; "start from the customer experience" argues for a human message. (confidence: high — WWDC 1997) Verdict: CONCERNS — fix CRITICAL before merge. ``` ## Problem Abstract adversarial review ("act as a saboteur") produces generic findings — the model imagines what a reviewer *might* say. This skill grounds each lens in a **real, sourced engineering philosophy** documented in [`re
- Example Output
- Problem
- Attribution discipline (read this first — it is the load-bearing rule)
- Rules
- Persona Pools
- Severity Levels
- The Process
- Step 0: Read twice
- Step 1: Ground the principles first
- Step 2: Review (3 independent — 2 engineers + 1 product)
- Step 3: Synthesize & post
- Integrity Check (Feynman)
- Exit Condition
- When to Use
What does the named-persona-adversarial-review skill do?
Code review through the lens of real engineers' documented philosophies (Torvalds, Thompson, Carmack, Kent Beck, Jobs, Cagan). Complements abstract-role adversarial review with named, sourced perspectives. Use when automated review findings feel generic, when a PR has architectural or UX impact, or when the author wants pre-submit hardening beyond standard checks.
How do I install it?
Run `npx skills add alirezarezvani/claude-skills --skill named-persona-adversarial-review --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From alirezarezvani/claude-skills, a repository with 23,791 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.