R
RusticStack/skills
Agent skills that prune what a repository doesn't need: stale comments, dead docs and bloated agent instruction files.
updated 2026-11-18
View on GitHub ↗Direct link · no redirect page
After install: how to tell it works
- What you see after install — The command exits 0 and the terminal shows no "command not found" or "permission denied".
- One-line self-check — Run the smallest usage example from that repository's README. If the output matches what the README describes, it is working.
- If that does not work — This project has no troubleshooting notes. Search its issues for "install".
The install command comes from the repository; these checks describe observable results only and do not replace the project's own docs.
- Star count
- 0 ★ · RusticStack/skills · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-11-19 · last seen 2026-11-20 · seen 2× · listed by 4 sources
- Score
- score 403 · 4 sources · repo
- Install
- see Install & config above
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: Agent skills. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
RusticStack/skills;first catalogued 2026-11-19;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
RusticStack Skills
Excerpted from the repository README (abridged)
Agent skills that leave a repository easier to read.
Short instruction files for Claude Code, Codex, Cursor and other coding agents. Each one removes or fixes something that costs the next reader, human or model.
## Skills
| Skill | What it does | Install in Claude Code |
| prune-docs-and-comments | Prunes comments and docs that say nothing the code doesn't, or say something no longer true. | /plugin install prune-docs-and-comments@rusticstack-skills |
| prune-tests | Prunes tests that guard no behavior anyone relies on, with proof for every deletion. | /plugin install prune-tests@rusticstack-skills |
| clarify-code | Makes code say what a reader otherwise has to work out, without changing what it does. | /plugin install clarify-code@rusticstack-skills |
| prune-dead-code | Prunes code that nothing runs and nothing reaches, with proof for every deletion. | /plugin install prune-dead-code@rusticstack-skills |
| prune-dependencies | Prunes dependencies the project does not use, with a clean install and build as proof. | /plugin install prune-dependencies@rusticstack-skills |
## Install
With the skills CLI, which works with Claude Code, Cursor, Codex and other agents:
npx skills add rusticstack/skills
Or, in Claude Code, add this repository as a plugin marketplace, then install a skill with the command in its row of the table above:
/plugin marketplace add rusticstack/skills
To install by hand, copy a skill's folder into ~/.claude/skills/.
## prune-docs-and-comments
Run it on a repository or a path:
/prune-docs-and-comments
/prune-docs-and-comments src/billing
The agent asks one question of every comment and document: what does it depend on? Prose stays only if it depends on intent the code cannot express, such as why the code is this way, what must stay true, or what a caller may rely on. It goes if it depends on:
The past. It narrates an edit, describes code that is gone, or is a finished plan or status report. Git history already holds it.
Nothing. It restates the code beside it, so no reader learns anything from it.
The implementation. It copies values, file trees or call lists out of the code, and is wrong the first time someone forgets to update it.
What makes it safe to run:
It changes no code. The diff contains comments and documents only, so the build, lint, type check and tests give the same results before and after.
It leaves what tools read. Linter and type-checker suppressions, build tags, license headers, doctests, expected-output comments in tests, and docstrings that become command-line help or API schemas stay exactly as they are. references/load-bearing.md lists the known forms for more than twenty languages and formats, and ten rules for recognizing one that isn't listed.
It keeps when unsure. A deleted reason is gone for good, so prose the agent cannot fault stays.
It needs evidence for staleness. A comment is stale when the agent can point to the code that contradicts it. Age is not evidence.
It reports what it won't settle. When a comment and the code disagree and the code may be the one that is wrong, both stay and the disagreement goes in the report.
Agent instruction files (CLAUDE.md, AGENTS.md, rule files) get the same test, held more strictly, because every line in them is read on every task. Directory tours, style rules a linter already enforces, and generic advice go. Exact commands, traps, and the owner's stated preferences stay.
Short instruction files for Claude Code, Codex, Cursor and other coding agents. Each one removes or fixes something that costs the next reader, human or model.
## Skills
| Skill | What it does | Install in Claude Code |
| prune-docs-and-comments | Prunes comments and docs that say nothing the code doesn't, or say something no longer true. | /plugin install prune-docs-and-comments@rusticstack-skills |
| prune-tests | Prunes tests that guard no behavior anyone relies on, with proof for every deletion. | /plugin install prune-tests@rusticstack-skills |
| clarify-code | Makes code say what a reader otherwise has to work out, without changing what it does. | /plugin install clarify-code@rusticstack-skills |
| prune-dead-code | Prunes code that nothing runs and nothing reaches, with proof for every deletion. | /plugin install prune-dead-code@rusticstack-skills |
| prune-dependencies | Prunes dependencies the project does not use, with a clean install and build as proof. | /plugin install prune-dependencies@rusticstack-skills |
## Install
With the skills CLI, which works with Claude Code, Cursor, Codex and other agents:
npx skills add rusticstack/skills
Or, in Claude Code, add this repository as a plugin marketplace, then install a skill with the command in its row of the table above:
/plugin marketplace add rusticstack/skills
To install by hand, copy a skill's folder into ~/.claude/skills/.
## prune-docs-and-comments
Run it on a repository or a path:
/prune-docs-and-comments
/prune-docs-and-comments src/billing
The agent asks one question of every comment and document: what does it depend on? Prose stays only if it depends on intent the code cannot express, such as why the code is this way, what must stay true, or what a caller may rely on. It goes if it depends on:
The past. It narrates an edit, describes code that is gone, or is a finished plan or status report. Git history already holds it.
Nothing. It restates the code beside it, so no reader learns anything from it.
The implementation. It copies values, file trees or call lists out of the code, and is wrong the first time someone forgets to update it.
What makes it safe to run:
It changes no code. The diff contains comments and documents only, so the build, lint, type check and tests give the same results before and after.
It leaves what tools read. Linter and type-checker suppressions, build tags, license headers, doctests, expected-output comments in tests, and docstrings that become command-line help or API schemas stay exactly as they are. references/load-bearing.md lists the known forms for more than twenty languages and formats, and ten rules for recognizing one that isn't listed.
It keeps when unsure. A deleted reason is gone for good, so prose the agent cannot fault stays.
It needs evidence for staleness. A comment is stale when the agent can point to the code that contradicts it. Age is not evidence.
It reports what it won't settle. When a comment and the code disagree and the code may be the one that is wrong, both stay and the disagreement goes in the report.
Agent instruction files (CLAUDE.md, AGENTS.md, rule files) get the same test, held more strictly, because every line in them is read on every task. Directory tours, style rules a linter already enforces, and generic advice go. Exact commands, traps, and the owner's stated preferences stay.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/rusticstack-skills/)
- Source
- github · https://github.com/RusticStack/skills
- Browse by field
- Agent skills
- Listed by
- 4 independent sources
- added
- today
More entries
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.