agentsclimarketplace

Simplify

Skill magarcia/skills/skills/simplify

Agent skills for taking work from idea to merged PR

Install
npx -y skills add magarcia/skills --skill simplify

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 14 days oldThe repository was created 14 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Make a behavior-preserving quality pass over changed files for reuse, clarity, types, dead code, structure, and accidental inefficiency. Use after significant implementation, before a PR, when the user asks to simplify or clean up a diff, or as the closing pass of $implement.

SKILL.md

2.4 KB, as published. Nobody here has run it

Simplify

Never change observable behavior. Report a real bug instead of hiding its fix inside cleanup, because a semantic change invalidates prior verification. Limit edits to the target diff and files that must change with it; do not perform drive-by refactors.

Read every changed file in full and every applicable AGENTS.md, then inspect:

  • Reuse — Search for existing utilities, components, and types before adding another. Consolidate repeated code only when it represents the same concept and extraction reduces total complexity; two call sites alone do not justify an abstraction.
  • Dead code — Remove unused imports, variables, branches, commented-out code, and debug logging introduced or exposed by the diff. Use configured project tooling such as Knip and linters when available. Do not add a dependency for this pass, and corroborate analyzer output against dynamic imports, generated code, exports, tests, and external consumers.
  • Comments — Remove narration, stale history, and comments that merely restate code. Preserve intent, invariants, constraints, and non-obvious tradeoffs.
  • Naming and structure — Ensure names describe current behavior and flatten avoidable nesting with early returns when clearer.
  • Types — Remove unjustified any, broad object types, and unchecked assertions or casts. Preserve unknown at untrusted boundaries and narrow or validate it immediately. Use configured cycle analysis when available; do not assume Madge is installed.
  • Efficiency — Remove accidental quadratic work and repeated parsing or fetching. Avoid speculative micro-optimization.

Run the smallest relevant tests, lint, typecheck, and diagnostics required by the repository and changed code. Summarize what changed, what was intentionally left alone, and any bugs reported.

  • Prefer readable code over compact cleverness.
  • Follow an established repository pattern even when another style is personally preferable.
  • Leave unproven fallback, compatibility, and legacy-path removal out of scope. Suggest a separately scoped $improve-vibecode audit when broader evidence-backed cleanup is warranted.

Gives 1 of the 12 instructions most refactoring skills give

Counted across 521 of the 525 authors here whose files we hold, read 2026-08-06

  • run tests after each changein 59 of 521, across 56 files
  • write tests before refactoringin 27 of 521, across 24 files
  • preserve external behaviorhere, and in 26 of 521, across 22 files
  • remove dead codein 25 of 521, across 24 files
  • make small incremental changesin 20 of 521, across 17 files
  • break the implementation into tiny commitsin 18 of 521, across 5 files
  • ask the user about alternative optionsin 17 of 521, across 4 files
  • create a GitHub issue with the planin 17 of 521, across 4 files
  • explore the repository to verify assertionsin 17 of 521, across 4 files
  • interview the user about the refactorin 16 of 521, across 3 files
  • check the codebase for test coveragein 16 of 521, across 3 files
  • refactor one thing at a timein 16 of 521, across 12 files

Said here and by no other author read

  • limit edits to the target diff
  • remove dead code exposed by the diff
  • remove narration and stale comments
  • remove unjustified any types
  • remove accidental quadratic work
  • run the smallest relevant tests

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.