Skip to content
Development
Command

/simplify

The over-engineering review: five tags (delete, stdlib, native, yagni, shrink), a mandatory replacement per finding, and a real null result when there is nothing to cut.

BOOST
From plugin
procoder
21130 skills30 commands2 hooks
Install
> /plugin marketplace add azrtydxb/procoder
> /plugin install procoder@procoder

How it fires

How this command gets triggered: by you, by Claude, or both.

  • Fires itselfClaude auto-loads it when your prompt matches the work.
  • You can call itInvoke it directly when you want it.
  • Slash command/simplify

Context preview

What this command does when you run it.

The over-engineering review: five tags (delete, stdlib, native, yagni, shrink), a mandatory replacement per finding, and a real null result when there is nothing to cut.

Command definition

simplify.md
description: "The over-engineering review: five tags (delete, stdlib, native, yagni, shrink), a mandatory replacement per finding, and a real null result when there is nothing to cut."

The user invoked /procoder:simplify with arguments:

The launcher is: "${CLAUDE_PLUGIN_ROOT}/hooks/launcher.sh"

This review hunts one thing only: code that should not exist. Correctness bugs, security, performance — out of scope here; those belong to `launcher.sh check`, `security`, and /procoder:debug.

Scope: with no arguments, review the working-tree diff (`git diff` plus staged). With `repo` (or a path) in the arguments, sweep that whole scope — use `launcher.sh index unused` and `launcher.sh maintain` as starting evidence, then read.

The diff pass runs before every pull request; the repo sweep before a tag.

Every finding is one line, with a mandatory replacement — a finding without a replacement is hedging, not reviewing:

<file>:L<line>: <tag> <what>. <replacement>.

The five tags:

  • `delete:` dead code, unused flexibility, speculative feature.

Replacement: nothing.

  • `stdlib:` hand-rolled code the standard library ships. Name the

function.

  • `native:` a dependency or code doing what the platform already does

(CSS over JS, a DB constraint over app code). Name the feature.

  • `yagni:` an abstraction with one implementation, config nobody sets, a

layer with one caller.

  • `shrink:` same logic, fewer lines. Show the shorter form.

End with the score line: `net: -<N> lines possible.` — and when there is genuinely nothing to cut, say exactly `Lean already. Ship.` and stop; never invent findings to look thorough.

Rules:

  • Never flag a lone smoke test or assert-based self-check as bloat — the

minimum check is part of the code, not decoration (see /procoder:tdd).

  • A deliberate simplification marked with the debt marker (see

`launcher.sh debt`) is a recorded decision, not a finding — unless its revisit trigger has arrived.

  • List the cuts; do not apply them. The user (or the task at hand)

decides — P-CONTROL applies to reviews too.

Read more
Ships withprocoder

Senior-developer discipline for AI coding agents. A commit gate that counts unchecked as failing, quality controllers that refuse to call unfinished work done, and a lessons loop that closes each escaped bug's class. One Go binary, no runtime deps, works with 20+ agents.

Get the whole plugin
Stats
210
Stars
17
Forks
Active
Maintenance
Go
Language
Apache-2.0
License
1d ago
Last commit
2mo ago
Created
5h ago
Added

Repo: azrtydxb/procoder

Other commands on procoder.

adr
Command

adr

Architecture decision records: durable decisions with their date, context, and consequences — supersede, never rewrite.

@azrtydxb@azrtydxbInstall Command