Enforce human-readable naming and shallow repo structures during planning, implementation, or refactoring.
npx skills add https://github.com/athif23/skills --skill repo-shape
Please help me install this Agent Skill. Skill: repo-shape Source: https://github.com/athif23/skills/tree/main/skills/repo-shape Command: npx skills add https://github.com/athif23/skills --skill repo-shape
Keep code and repo changes calm, skimmable, and human by preventing AI slop, fake enterprise structure, bad naming, and duplicated helpers.
Describe the kind of changes you are about to make in plain language to align with repo-shape guidelines.
High-intent search queries and answers about installing and using this skill.
Fix bloated repo structures and unclear code naming by enforcing shallow layouts and naming by responsibility. This approach maintains human-readable code, prevents AI slop, and guides structure and abstraction decisions during refactoring.
Naming by responsibility in code architecture assigns identifiers based on what a module or function actually does. It keeps layouts shallow, state derivable, and avoids speculative abstractions to maintain readability and calm code.
Prevent speculative abstractions during a large refactor by enforcing minimal layers and reusing existing helpers. Apply guidelines that require derivable state and name-by-responsibility to keep code calm, skimmable, and easy to extend.
Yes, you can apply these architecture and refactoring guidelines for small to mid-sized projects. They guide naming, structure, and abstraction decisions during planning, implementation, or refactoring to keep code readable and easy to extend.
Avoid minimal layers in code architecture when your project genuinely requires complex, deeply nested enterprise structures. These guidelines target small to mid-sized projects by enforcing shallow layouts and avoiding speculative abstractions entirely.
jpfieldingGenerate conventional commit messages from staged git diffs.
markky21Guide code reviews and refactoring with naming, structure, and error handling principles.
VSF-QC-TTSEnforce TypeScript best practices for naming, functions, modules, and error handling.
codybromEvaluate software abstractions for genuine complexity hiding versus redundant layers.
