Skip to content
Skills Library
Programming · Building & coding

code-simplifier

/code-simplifier

Simplify the branch diff without changing behaviour - remove duplication, dead code and needless layers. Use when running the simplify pass or asked to simplify the branch diff. Don't use for new behaviour or code outside the diff (use the spec's change map).

Repository
spur-board ↗
Licence
MIT
Last repository change
13.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Simplify the branch diff without changing behaviour - remove duplication, dead code and needless layers. Use when running the simplify pass or asked to simplify the branch diff. Don't use for new behaviour or code outside the diff (use the spec's change map).

Original author description

Simplify the branch diff without changing behaviour - remove duplication, dead code and needless layers. Use when running the simplify pass or asked to simplify the branch diff. Don't use for new behaviour or code outside the diff (use the spec's change map).

How it works

  1. Scope
  2. Order
  3. Behaviour and tests
  4. Report
Original SKILL.md headings · 42 lines, 311 words
SKILL.md preview
---
name: code-simplifier
description: Simplify the branch diff without changing behaviour - remove duplication, dead code and needless layers. Use when running the simplify pass or asked to simplify the branch diff. Don't use for new behaviour or code outside the diff (use the spec's change map).
---

# Code simplifier

Make the branch smaller and plainer without changing behavior.

## Scope

- Only lines in `git diff <origin/main sha>...HEAD`, with the `origin/main` SHA from the handoff.
  Code the branch did not touch is out of scope; note a problem there as a finding instead.
- No new behaviour, no new feature flags, no renamed public exports, no changed output formats.

## Order

Work through the diff in this order and stop when nothing is left:

1. Delete - dead code, unused exports, parameters and imports, branches that cannot run, guards
   and caches for cases that do not occur, comments that restate the code.
2. Merge - duplicated logic into the one place that already exists; two helpers doing the same
   thing into one.
3. Narrow - wider types, options or interfaces than any caller needs; layers that only forward
   a call.
4. Shorten - long conditionals and nesting into early returns; names that need a comment into
   names that do not.

Prefer an existing pattern in the repo over a new abstraction.

## Behaviour and tests

- Tests stay as strong as before. Do not delete, skip or loosen a test to make a change fit.
  When a test must change (it tested a removed internal), report it under `Changed checks` as
  `gitflow` lists.
- Run `pnpm check` after each chunk; without a `package.json`, report `no checks available`.
  Read exit codes directly. A failure means the change altered behaviour - revert that chunk.
- Agent files in the diff (`.agents/`, `.claude/`, `.codex/`, `AGENTS.md`): check them against
  `skill-writer` and keep the copies in sync.
- Commit each chunk as `refactor(<scope>): ...`, or `chore(agents): ...` for agent files.

## Report

One line per change: what was removed, merged, narrowed or shortened, and where. Then the checks
with exit codes. Nothing worth simplifying -> say so; that is a valid result.

Versions

RepositoryScoreLicence
This page · AnDeVerin/spur-board90MIT
Shen-Ming-Hong/singular-blockly100Apache-2.0
OpenHands/extensions100MIT
duc01226/EasyPlatform100MIT
duc01226/EasyPlatform100MIT
s-hiraoku/vscode-sidebar-terminal100MIT
pproenca/dot-skills100MIT
kumaran-is/claude-code-onboarding100MIT
edmundmiller/dotfiles90MIT

Database snapshot: 13.11.2026 · package version a74bb8861c5b (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 86simplify
    Use when the user asks to simplify, clean up or refactor recently changed code without changing what it does (duplication, dead code, needless complexity).
  • 90simplify
    Simplify a completed workpackage without changing its intended behavior: remove needless abstraction, duplication, indirection, speculative flexibility, and defensive code, then report what changed and what was left for approval. Use when the user says \"/simplify\", asks to…
  • 95simplify
    Use when the user wants to simplify or clean up code without changing behavior. Accepts standalone scope or user-selected findings from /refactor.
  • 100axiom-swift-simplifier
    Use when the user wants to simplify Swift code, reduce boilerplate, or make Swift more readable and idiomatic without changing behavior.
  • 90refactor-safely
    Refactor code without changing what it does (rename, extract, split files, remove duplication, simplify). Use when the user says "clean this up", "refactor", "split this file", "simplify this function", "rename X everywhere", or "remove this duplication".
  • 90cmk:delivery-simplify
    Use when the user asks to "simplify", "clean up the diff", "polish the changed code", or "run a simplify pass" without changing behavior — or when phase 3b of `cmk:delivery-pipeline` needs a whole-branch quality cleanup. Produces a behavior-preserving polish of the changed…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.