Diagnose and prioritize codebase rot with confidence-tagged findings.
npx skills add https://github.com/subinium/vibesubin --skill fight-repo-rot
Please help me install this Agent Skill. Skill: fight-repo-rot Source: https://github.com/subinium/vibesubin/tree/main/plugins/vibesubin/skills/fight-repo-rot Command: npx skills add https://github.com/subinium/vibesubin --skill fight-repo-rot
Finds and prioritizes rot in a codebase: dead code, god files, hotspots, hardcoded paths, and stale TODOs. It returns a prioritized diagnosis where dead-code candidates are tagged HIGH/MEDIUM/LOW and the operator hands off fixes to the appropriate skills. It is a diagnosis-only tool designed to avoid unauthorized edits to the repo.
Analyze a repository to generate a prioritized rot report and actionable next steps.
High-intent search queries and answers about installing and using this skill.
Find and prioritize dead code in your repository by running a static analysis diagnosis that surfaces orphaned files and deletion candidates, tagging each with HIGH, MEDIUM, or LOW confidence levels to guide cleanup.
Repo rot is the gradual degradation of code quality characterized by dead code, god files, hotspots, hardcoded paths, and stale TODOs. Diagnose it by surfacing these issues and generating a prioritized report for remediation.
Yes, static analysis can identify god files and coupling hotspots before refactoring by applying diagnostic checks across the codebase to prioritize structural issues and prevent major changes from introducing regressions.
Yes, this dead code diagnosis tool works with codebases of any programming language, applying language-agnostic static analysis to surface rot and generate prioritized remediation guidance without requiring language-specific setup.
No, running a repo rot diagnosis will not modify or delete your source files. It is a diagnosis-only tool designed to avoid unauthorized edits, outputting a prioritized report and hand-off guidance for safe remediation.
After identifying stale TODOs and hardcoded paths, you should hand off the prioritized diagnosis to remediation skills like refactor-verify to execute fixes and verify that the cleanup does not break existing functionality.
remiverdiesenClone Ark's repository and inspect its architecture, CRDs, and controllers.
bitsocialnetAutomate a targeted refactor pass on frontend code using git diff inputs.
zerx-labEnforce Rust GPUI coding standards for error handling and naming conventions.
ArabelaTsoDetect design smells in Python codebases via static AST analysis.
