Cheickmec Smellcheck
cheickmec-smellcheck is a Claude Code plugin for the Ship phase that detects Python code smells using 82 patterns and 55 AST checks with refactoring guidance.
by cheickmec · github.com/cheickmec/smellcheck
Detect Python code smells with AST-backed checks and numbered refactoring guidance inside Claude Code, CI, or pre-commit before you merge.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install cheickmec-smellcheck@cheickmec/smellcheckBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:cheickmec/smellcheck") and the paste-ready config with skillselion.get_install_config("plugin:cheickmec/smellcheck").
What it does
cheickmec-smellcheck is a Python-focused code smell detector and refactoring guide packaged so solo builders can wire it into Claude Code, local CLI, CI, or pre-commit without pulling a heavy analysis stack. It catalogs dozens of smell patterns and runs AST checks that surface design, control-flow, and idiomatic Python issues with enough structure for an agent to propose targeted refactors instead of vague cleanup. Builders shipping backends, CLIs, or small SaaS APIs use it when review time is scarce but they still want consistent quality signals before merge. Because it is zero-dependency and multi-surface, it fits indie workflows that mix agent assistance with traditional gates. It is not a full security audit or test runner; it complements review and testing skills by making maintainability problems visible early.
Highlights
- 82 documented code-smell patterns with refactoring-oriented guidance
- 55 AST-based static checks with zero runtime dependency footprint
- Runs as Claude Code Agent Skills plugin, PyPI package, GitHub Action, or pre-commit hook
- Covers architecture, class design, control flow, immutability, and Python idioms
- Numbered catalog and metrics-oriented smell reporting for agent-led fixes
Why builders use it
Your Python codebase accrues subtle design and idiomatic smells that agents gloss over until reviews become slow and risky refactors pile up.
You get consistent AST-backed smell reports and a numbered refactor catalog so Claude Code or CI can apply focused fixes before ship.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 0 stars, 0 votes.
FAQ
Who is cheickmec-smellcheck for?
Python-building solo developers and small teams who want structured smell detection in Claude Code plus optional PyPI, Action, or pre-commit wiring.
When should I use cheickmec-smellcheck?
Use it during backend work and especially at Ship review whenever you merge Python changes and want AST-verified smell signals.
How do I add cheickmec-smellcheck to my agent?
Install the smellcheck Agent Skills plugin for Claude Code from cheickmec/smellcheck, or install the PyPI package and point your skill or hooks at the same analyzer.
Comments
Share how you use cheickmec-smellcheck, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.