The Fictional Senior — A Persistent Reviewer Who Remembers Every PR
Invent a senior engineer with twenty years and a specific personality. Spawn them as a persistent reviewer. They comment on every PR, in voice. They remember past PRs. They develop opinions about your growth.
Why this exists
Generic LLM code review is forgettable. The notes are correct, the tone is flat, and you close the tab. Reviewers with a stable voice and persistent memory feel different — they feel like mentorship. The bottleneck in most engineers' growth is not reviewer quality. It's reviewer continuity. A senior who sees one PR cannot tell you you're repeating a mistake from three weeks ago. A fictional senior, with memory, can.
What you get back
- A defined senior engineer character with a backstory, a name, and a specific personality you chose on purpose.
- A persistent review on every PR, written in their voice, not a default LLM voice.
- Callbacks to earlier decisions — "you fought me on this exact pattern in the auth refactor; I was right then too."
- An evolving narrative about your growth as an engineer over weeks and months.
- The specific patterns they keep flagging — your tells, your blind spots, the thing you reach for when tired.
When to reach for this pattern
Solo work, where there is no one to review you. Small teams without senior engineers, where everyone is roughly the same level and no one is the adult in the room. Learning a new language or paradigm, where you need someone to tell you which idioms are local and which are imported badly from your last stack. And any deliberate practice loop where you want feedback that compounds — where the reviewer in week twelve knows what they told you in week one.
Invent a fictional senior engineer with twenty years of experience
and a specific personality — pick one: nitpicky and kind, allergic
to cleverness, secretly impressed by terseness, etc. Spawn this
character as a persistent reviewer of my pull requests. Maintain
continuity across sessions: they remember my past PRs, develop
opinions about my growth, and call back to specific earlier
decisions. They are not a generic reviewer — they are this person.Paste this into Claude, Cursor, or Copilot. Change one thing that matters to you.
What I learned shipping it
- Code review is more useful from a persona than from a void. A voice with a backstory lands; a generic critique evaporates.
- Continuity is what mentorship actually feels like. A reviewer who remembers your last six PRs is doing something a one-shot model cannot.
- A fictional reviewer with a sharp personality outperforms a real one with no time. Availability and consistency beat prestige.