agentleFS
kapadiaskapadias/nonna/.claude/skills/audit/SKILL.md

audit

Skill0 starsChanged 46 days agoMITView on GitHub

Repo-wide over-engineering sweep: ranked delete/stdlib/native/yagni/shrink findings + the debt ledger. Read-only, one-shot.

193 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use delight, teach-impeccable and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • HK-hubSkill

    delight

    Add moments of joy, personality, and unexpected touches that make interfaces memorable and enjoyable to use. Elevates functional to delightful. Use when the user asks to add polish, personality, animations, micro-interactions, delight, or make an interface feel fun or memorable.

    Also in 31 projects that use this

  • HK-hubSkill

    teach-impeccable

    One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.

    Also in 18 projects that use this

  • zwy123zwySkill

    normalize

    将用户随意输入的提示词规范化为结构清晰、便于大模型执行的标准化提示词。适用于需要整理、统一提示词格式时调用。

    Also in 18 projects that use this

  • ww-w-aiSkill

    pm-discovery

    PM Agent Team - Automated product discovery, strategy, and PRD generation. Runs PM analysis workflow to produce comprehensive PRD before PDCA Plan phase.

    Also in 3 projects that use this

  • ww-w-aiSkill

    qa-phase

    Run QA tests at various levels (L1-L5) for features under PDCA management. Integrates with MCP tools to execute structured test plans.

    Also in 3 projects that use this

  • +7 more from HK-hub

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 174 edited versions we read keep these.

  • 0

    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. Very specific:

    Ledger: Run bash "${CLAUDE_SKILL_DIR}/../lean/scripts/check-debt.sh" --ledger and append its output to the report.

    line 25

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

Audit for over-engineering: $ARGUMENTS (if empty, the whole repository).

Applies the lean ladder to a tree instead of a diff — a full sweep for accumulated complexity rather than a check on one change. This produces findings only; nothing is applied. Correctness and security are /review's job, not this skill's.

Steps

  1. Fan out. Dispatch explorer per top-level source directory, concurrently, each carrying the same hunt list: dependencies the stdlib or platform already ships, single-implementation interfaces, factories with one product, wrappers that only delegate, files exporting one thing, dead flags and config, hand-rolled stdlib. Each subagent returns path:line plus a tag and a replacement — never file contents.
  2. Rank. Merge the returned findings, deduplicate, and order biggest cut first. One line per finding, tagged delete: / stdlib: / native: / yagni: / shrink: (the tag format is defined in the lean skill).
  3. Ledger. Run bash "${CLAUDE_SKILL_DIR}/../lean/scripts/check-debt.sh" --ledger and append its output to the report. A no-trigger marker from the script is itself a finding — report it, do not discard it.

Output

Ranked lines in the form <tag> <what to cut>. <replacement>. [path:line], followed by the debt ledger, then a closing net: -N lines, -M deps possible. — or, if the sweep turns up nothing, Lean already. Ship. Apply nothing here: route any accepted cut through /plan then /tdd, since a deletion still needs the suite green before it merges.

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.