Swellshinider

@swellshinider source repo

3 skills
0 followers
6 hours ago last updated

▌
Cleaner · swellshinider bundle
Use when AI-generated code has bloated the repo: oversized files or classes, dead or unused code (functions, imports, variables, types, whole files), or duplicated blocks that need merging. Behavior-preserving cleanup only. Run when the user says "clean up this code", "remove dead code", "split this file", "this file is too big", "deduplicate", or "refactor without changing behavior". Not for new features, bug fixes, performance work, or over-engineering review.

0
installs
▌
Manager · swellshinider bundle
Use when the codebase is structurally hard to navigate: oversized files or classes that should be split into cohesive modules, or a flat or misplaced directory layout that should be regrouped by feature or responsibility. Behavior-preserving structural refactor only: split files and move them into a cleaner layout, with import rewrites and re-export shims keeping callers unchanged. Run when the user says "this module is a mess", "split this giant file", "reorganize these folders", "group these files by feature", or "restructure this directory". Not for in-place dead-code removal or deduplication (that is the cleaner skill), nor for new features, bug fixes, or behavior changes.

0
installs
▌
Docs Cleaner · swellshinider bundle
Audit and improve project documentation and open-source repository readiness: README files, guides, contribution policies, security and conduct files, support guidance, and GitHub issue or pull-request templates. Use when documentation is stale, redundant, incomplete, inconsistent, or needs a conservative open-source standards review. Documentation-only changes.

0
installs

3 published skills