
Find Simplifications
Use for a periodic repo-wide sweep of qwen-code for accumulated excess surface, dead...
Install
npx skills add QwenLM/qwen-code --skill find-simplifications -g -a claude-code -y- Repository
- QwenLM/qwen-code28.9k
- Category
- Engineering
- Updated
- 3d ago
- License
- Apache-2.0
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Use for a periodic repo-wide sweep of qwen-code for accumulated excess surface, dead components and files, orphaned locale keys, exports nothing consumes, added-then-removed scaffolding, filing candidates on a tracking issue and landing only what a maintainer has said yes to. Repo-wide and evidence-first; every consumer is named before anything is deleted. Not for tidying a diff you just wrote (that is bundled `/simplify`) and not for defects (that is `/review`).
Finding qwen-code Simplifications
AGENTS.md § Simplicity First, "Minimum code that solves the problem.
Nothing speculative." This skill hunts what that principle already rejected
but that shipped anyway. It owns correct code nobody needs, repo-wide,
with no diff to anchor on.
Every candidate names the surface, names every consumer, and says what breaks when it goes. A candidate whose consumers cannot all be named is dropped, not downgraded, dropped.
Read this file, then the one document for your phase. Do not survey or land from this file alone; if the phase document cannot be read, stop and say so.
| Phase | Document |
|---|---|
| Survey (default): find and file | references/survey.md |
| Land: turn ONE approved candidate into a PR | references/land.md |
Issue First, PR Second
A run's deliverable is a comment on the tracking issue, not a PR.
Survey → file candidates on the tracking issue → maintainer says yes to one
→ land that one → one PR, one candidate.
This is not ceremony. AGENTS.md § Core Infrastructure ends "When in doubt,
escalate. Better to wrongly escalate than to wrongly approve," and an
unrequested batch of deletions is the shape that gets closed. It also makes
the ledger free: the issue that carries the proposals is the same object the
next run reads to avoid re-proposing them.
A maintainer asking for a PR in this session counts as assent, record it on the ledger before opening the PR.
