simplify-codebase
An AI agent skill from tt-a1i/archify, scored 65 out of 100 by code.
Code score by group
It loses the most points in Done criteria (11), the group that checks whether there is a checklist and a step that verifies the work.
What the author says it does
Simplification audit or authorized codebase simplification whose stated objective is to remove accidental complexity. Use for evidence-backed deletion or consolidation of dead code, duplicate state, redundant APIs or layers, ownerless abstractions, obsolete compatibility or design records, and over-engineering in any language; also use for 代码简化 or 熵回收. Do not use for general code review, onboarding, style-only refactoring, or performance tuning.
This is the description in the skill's own SKILL.md, written by its author, not by SkillCheatSheet.
- Repository
- tt-a1i/archify
- Folder
- .agents/skills/simplify-codebase
- License
- Apache-2.0
- GitHub stars
- 95,776
- SKILL.md lines
- 84
- Other files
- 7
Add simplify-codebase to your agent
npx skills add tt-a1i/archify --skill simplify-codebase
The command uses the open skills CLI. A skill is instructions and scripts your agent will follow, so read it first: open the folder on GitHub at the commit that was scored.
More skills from tt-a1i/archify
-
archify
Create validated architecture, workflow, sequence, data-flow, lifecycle/state, ERD, class, tree, timeline, and waterfall diagrams as explorable standalone HTML with dark/light the…
77B -
archify-tuning
Improve Archify diagram accuracy, visual quality and complete authoring speed with fewer repairs. Use for generation experiments or evaluating changes to layout, routing, diagnost…
67C -
test-value
Improve test value and feedback cost when auditing slow, flaky, redundant or brittle tests; choosing tests during implementation; or reviewing test changes before a commit or PR.…
64C -
archify-review
Review Archify issues, PRs, or code through value, cost, and impact to support evidence-based maintenance decisions. Use for issue triage, change reviews, and code quality assessm…
58C
Scores come from a snapshot of 300 public GitHub repositories taken on 12 November 2026. Every score is the result of fixed checks run by code; no AI is involved. How scoring works.