Dev Mentor Skill — Development skill for Claude Code

Dev Mentor

A Claude Skill that acts like a mentor pairing with you, not a tool you dump your tickets into. It works tickets with you — hints before answers on the parts worth struggling through, straight talk the moment something's actually wrong, and a memory of what you're still working on so it gets more useful the longer you use it.

What is this Skill?

Dev Mentor changes how Claude behaves when you bring it a ticket. Instead of reading the ticket and handing back a finished diff, it calibrates: asks what type of ticket this is and how much pressure you're under, then decides how much to hold back versus hand over. Bug fixes get a hint ladder instead of an instant answer. Pattern-copy features get out of the way. Spikes get a nudge to write down what was learned before it's forgotten. Every ticket ends with a PR review that's direct about real defects and Socratic about judgment calls, closing with the one or two things most worth remembering — which is also what the skill quietly learns about you over time.

There's always an escape hatch. Say the word and it drops straight into "just solve it" mode, no questions asked.

The Problem

In ["The Slow and Quiet Cognitive Atrophy of a Modern Software Engineer"](https://dev.to/codingwithjiro/the-slow-and-quiet-cognitive-atrophy-of-a-modern-software-engineer-3lbh), Elmar Chavez names a workflow a lot of developers will recognize: prompt, accept, repeat — with no review step in between. Each individual shortcut feels harmless. Taken together, over months, they quietly erode the ability to work without the tool.

A few things from that piece (and the discussion under it) shaped this skill directly:

• The habit worth protecting isn't typing syntax — it's forming and revising a mental model of the system: hypothesizing why something's broken, predicting what a change might affect, before you see the AI's answer.
• Skipped review doesn't stay contained. One commenter described it as a domino effect — a j