Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
Smell-check conducts structured audits of selected code paths to identify code and test smells. By measuring structure metrics and applying size profiles, it provides findings with evidence strength to help technical leads and architects diagnose maintainability issues without altering the subject code.
The tool focuses on identifying patterns with known cleanup moves rather than searching for bugs. It separates the diagnosis of technical debt from the implementation of fixes, leaving the final judgment and strategy to the codebase owner.
WHO IT'S FOR
Technical leads / architects
conducting maintainability audits and tech debt scans
QA / test automation engineers
identifying test smells and improving test suite health
Platform / DevEx teams
establishing codebase quality baselines and size profiles
AI agent / automation builders
integrating static analysis audits into AI workflows
Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.
Audit a small code path for maintainability smells
Uses smell-check
A git repository containing the code to inspect
A small, explicit path or glob replacing `[path-to-source-directory]`
git, wc, and Python 3
Use the smell-check skill to audit `[path-to-source-directory]` for code smells and test smells. Treat `[path-to-source-directory]` as a placeholder that I will replace with a small repository path such as `src/`. Use the default or automatically selected size profile, perform the documented static audit only, and report the generated index.html path when validation is complete.
Claude