agentleFS
Sign inStart free
dknaussdknauss/code-design-review-skills/skills/code-mentor/SKILL.md

code-mentor

Skill0 starsChanged 7 months agoMITView on GitHub

Use when writing or substantially changing code and you should explain the intended design approach before coding, then review whether the final implementation stayed simple, followed the plan, and avoided unnecessary code.

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. vekzz-dev/opencode-skills★ 4same name
    2. weininghui/skills★ 1same name
    3. jcerise/agent-skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 11 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 11

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the task benefits from explicit design explanation before implementation and reflective review after implementation.

    line 9
  2. Distinctive:

    Ask whether new code is needed at all.

    line 14
  3. Distinctive:

    Keep the planned approach visible.

    line 21
  4. Distinctive:

    Prefer deletion, simplification, configuration, or reuse over new abstraction.

    line 22
  5. Distinctive:

    Avoid generic machinery unless the problem truly requires it.

    line 23
  6. Distinctive:

    Check whether the implementation followed the intended approach.

    line 28
  7. Distinctive:

    If the implementation changed, explain why.

    line 29
  8. Distinctive:

    Ask again: Is this the simplest solution?

    line 31
  9. Distinctive:

    If less code, no abstraction, or no code would be better, say so clearly.

    line 32
  10. Distinctive:

    Prefer short explanations over lecture mode.

    line 37
  11. Distinctive:

    If the current approach is suboptimal, suggest a better one politely and explain why.

    line 38

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Code Mentor

Use this skill when the task benefits from explicit design explanation before implementation and reflective review after implementation.

Before coding

  1. Restate the problem in one sentence.
  2. Ask whether new code is needed at all.
  3. Name the intended approach or design pattern, if any.
  4. Explain the intended approach in 2–4 sentences.
  5. State why it is simpler than the most obvious alternative.

During implementation

  • Keep the planned approach visible.
  • Prefer deletion, simplification, configuration, or reuse over new abstraction.
  • Avoid generic machinery unless the problem truly requires it.

After coding

  1. Summarize what changed.
  2. Check whether the implementation followed the intended approach.
  3. If the implementation changed, explain why.
  4. Describe key tradeoffs, likely pitfalls, and maintenance consequences.
  5. Ask again: Is this the simplest solution?
  6. If less code, no abstraction, or no code would be better, say so clearly.

Tone

  • Be direct, calm, and instructive.
  • Prefer short explanations over lecture mode.
  • If the current approach is suboptimal, suggest a better one politely and explain why.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free