agentleFS
jerseycheesejerseycheese/agent-skills/skills/kiss/SKILL.md

kiss

Skill4 starsChanged 18 days agoMITView on GitHub

Trims a diff to the minimum change that meets its goal, dropping refactors, cleanup, style fixes, and "while I'm here" extras. Use when a diff has crept past its scope or before committing the smallest possible change. Trigger on: "KISS this", "trim this diff", "scope creep", "smallest possible change".

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Import reordering or cleanup

    line 21
  2. Distinctive:

    Prefer editing one line over editing a function.

    line 50
  3. Distinctive:

    If in doubt about whether something is necessary, remove it and note it.

    line 52
  4. Distinctive:

    Never introduce new patterns or dependencies in a KISS pass.

    line 53

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

KISS — Keep It Minimal

Purpose

Given a diff or staged changes, strip everything down to the smallest set of modifications that achieves the stated goal. Nothing more.

What to remove or simplify

  • Refactors or restructuring not required by the fix
  • Variable/function renames that aren't part of the stated goal
  • Comment additions or edits beyond the changed lines
  • Import reordering or cleanup
  • Whitespace normalization unrelated to the change
  • "While I'm here" fixes — flag these as separate tasks instead
  • New abstractions or helpers not required by the change
  • Extra test coverage beyond what directly tests the change
  • Style or formatting changes outside the modified logic

What to simplify (overengineering)

  • Constants or data structures that wrap what could be inline literals
  • Helper functions called only once — inline them
  • Intermediate variables that just rename what they hold
  • Multi-step logic that can be a single expression
  • Generic/parameterized code where one concrete case exists
  • Abstractions built for hypothetical future callers
  • Overly defensive null checks or fallbacks for impossible states
  • Tests with elaborate setup for simple assertions — simplify the fixture

Process

  1. Identify the stated goal — what is this change trying to do? One sentence.
  2. Read the full diff — git diff HEAD or git diff --staged
  3. For each hunk, ask: is this hunk strictly required to achieve the goal? If no, mark it for removal.
  4. Separate the extras — list anything removed with a one-line reason; offer to file each as a standalone task.
  5. Apply the trimmed diff — edit files to remove the extras, keeping only what's necessary.
  6. Verify — run tests on the trimmed change to confirm it still achieves the goal.

Rules

  • Prefer editing one line over editing a function; prefer editing a function over editing a file.
  • A change that touches N files should touch N-1 files if possible.
  • If in doubt about whether something is necessary, remove it and note it.
  • Never introduce new patterns or dependencies in a KISS pass.
  • Flagged extras go into a list at the end — never silently dropped.

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.