Python code review
Claude Code Python skills that improve how you write Python: clean code, design, and testing, enforced by a pre-commit review.
npx -y skills add JoseVelazcoH/python-skills --skill python-code-reviewAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Trigger: code review, review my changes, review this PR, check my code, pre-merge review, review diff. Review Python changes by the Review Pyramid, priority-first.
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.2 KB, as published. Nobody here has run it
Python Code Review
Review Python changes using the Review Pyramid: prioritize what matters, automate what doesn't.
Activation Contract
Apply when the user asks to review changes, a diff, or a PR, or to check code before merge. Reviewing is distinct from writing: focus on judgment, not rewriting.
Hard Rules
- Review bottom-up: API semantics → implementation correctness → docs → tests → style. Spend effort where the pyramid is widest at the base.
- Flag style/nits last and lightest: they are automatable (ruff/formatter), not merge-blockers.
- Always anchor review in task/business context; correctness depends on intent.
- Block on: breaking API contracts, wrong business logic, unhandled edge cases, security issues, missing tests for new behavior.
- Verify claims against the diff: never approve logic you have not traced.
Decision Gates
| Layer | Check | Severity |
|---|---|---|
| API semantics | Breaking changes, naming, contracts | Critical |
| Implementation | Business logic, edge cases, error handling | Critical |
| Security | Injection, authz, data exposure | Critical |
| Tests | New behavior covered, branch coverage | High |
| Docs | Public surface documented | Medium |
| Style | Lint/format | Nit (automate) |
Execution Steps
- Quick pass: lint, type check, security pattern scan, confirm tests exist.
- Deep pass: trace API and implementation semantics against the stated task.
- Check edge cases and error paths; confirm tests cover new branches.
- Report findings ordered by severity (Critical → Nit), each with file:line and a concrete fix.
Output Contract
Return findings grouped by pyramid layer, severity-ordered, each citing file:line with a specific remediation. Separate merge-blockers from nits explicitly. Do not rewrite the change: review it.
References
- Pair with
python-clean-code,python-design-principles, andpython-testing-tddto justify findings.