Python Anti-Patterns Checklist
Reviews Python code against a checklist of common bad practices before you ship it
- Repository
- wshobson/agents
- Stars
- 42,095
- Licence
- MIT
- Files
- 1 file
What it does
Once installed, the agent uses this file as a reference checklist when you ask it to review Python code. It checks for common mistakes such as duplicated retry or timeout logic, hard-coded secrets, leaking database models through APIs, blocking calls inside async code, unclosed files, swallowed exceptions, missing type hints and weak tests, and it shows bad versus better examples. It is a guide for the agent to follow, not a tool that runs anything.
Great for
- Developers reviewing Python code before a merge or release
- Teams that want a shared list of Python coding standards
- Students learning common Python pitfalls
Skip it if
- Projects not written in Python, since the checklist is Python-specific
- Replacing a full linter, type checker or security scanner, because it is a manual reference list and does not analyse your whole codebase automatically
Try asking
- “Review this Python module for anti-patterns before I open a pull request”
- “Check my async fetch code for blocking calls and unclosed resources”
- “Use the anti-pattern checklist to audit how my service handles errors and config”
- “Go through my tests and tell me where I only cover the happy path”
Install in 3 steps
- 1
Download the skill
The ZIP contains the 1 original files, the MIT licence and an attribution note.
python-anti-patterns.zip - 2
Add it to your agent
Claude Code (all projects)
mkdir -p ~/.claude/skills && unzip python-anti-patterns.zip -d ~/.claude/skills/Claude Code / Agent SDK (this project only)
mkdir -p .claude/skills && unzip python-anti-patterns.zip -d .claude/skills/Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.
- 3
Ask for the task
No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.
Get better results
- Point the agent at specific files or a diff so the review stays focused rather than general.
- Combine with your team's linter and type checker, since the agent's review is a judgement check, not an exhaustive scan.
- Ask the agent to explain each finding with the fix from the checklist so you can learn the reasoning behind it.
What's inside
- SKILL.md
Redistributed unmodified from wshobson/agents under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.