simplify-codebase

Featured

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.

Code & Development 97,678 stars 6669 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 96/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Simplify Codebase Reduce the number of concepts and obligations a codebase must keep coherent. Line-count reduction is supporting evidence, not the objective. A successful run may conclude that the inspected surface is already justified. ## Select mode and scope First choose the authority mode: - **Survey** for simplification audit, investigation, or candidate-finding requests. Remain read-only and return ranked evidence. - **Change** for explicit simplify, remove, consolidate, refactor, or repository-documentation edit requests. Prove each cut, implement it within the authorized scope, and validate the surviving contract. Then choose the coverage scope: - **Focused** when the user names a subsystem, symbol, state machine, dependency, or suspected duplication. Cover that boundary thoroughly before expanding outward. - **Broad** when the request spans the repository or asks for multiple candidates. Partition the system and account for every in-scope domain. Deleting a reachable capability, supported interface, stored representation, or compatibility path is a product decision. Describe the consequence and obtain direction unless the user has already chosen it. ## Establish the contract 1. Read the repository's instructions, architecture and decision records, manifests, test guidance, and generated-file conventions. 2. Inspect version-control state and preserve unrelated work. Identify vendored, generated, migration, fixture, and public-package surfaces before classi...

Details

Author
tt-a1i
Repository
tt-a1i/archify
Created
7 months ago
Last Updated
today
Language
JavaScript
License
Apache-2.0

Similar Skills

Semantically similar based on skill content — not just same category