agentleFS
Sign inStart free
rpraharajrpraharaj/ai-sdlc/skills/lean-review/SKILL.md

lean-review

Skill0 starsChanged 17 days agoMITView on GitHub

Review a diff or repo for unnecessary complexity only — delete-list of reinvented stdlib, unneeded deps, speculative abstractions. Use when the user asks what to delete, whether this is over-engineered, a simplify review, or a bloat audit. Do not edit product code.

5 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the target is empty, stop.

    line 31
  2. Very specific:

    Do not flag trust-boundary validation, the focused test for new logic, or correctness/security/perf bugs (name the other skill).

    line 42

“Common” is measured: kept by at least 6 in 10 of the 5 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

Lean review

Hunt complexity that does not need to exist. Not correctness (review-change), security, or performance.

Is this the right skill?

SignalDo this instead
Bugs / bar failuresreview-change
Apply the cutsrefactor-safely / implement-change

Required inputs

  • Current diff, or the whole tree if they said “audit”
  • engineering-bar Minimum path + Never cut

If the target is empty, stop.

Human decisions (do not invent)

  • Applying cuts (not this skill)

Procedure

  1. Collect the diff or scan the tree (skip node_modules, .git, vendored/build).
  2. One line per finding: <file>:<line>: <tag> <what to cut>. <what replaces it>.
  3. Tags: delete | stdlib | native | yagni | shrink. See references/tags.md.
  4. Do not flag trust-boundary validation, the focused test for new logic, or correctness/security/perf bugs (name the other skill).
  5. Rank biggest cut first. End with net: -<N> lines. Nothing to cut: Lean already.

Output

  • Path: reply
  • Template: references/tags.md

Quality bar

  • Product code not edited
  • Tags from the table only
  • Never-cut items absent from the list

Done

The delete-list or Lean already.

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