Skip to main content
skill CX Codex

python-expert-best-practices-code-review — Claude Code skill: Python

A rule set for writing, reviewing and refactoring Python. Useful when your agent touches error handling or dictionary access.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add wispbit-ai/skills --skill python-expert-best-practices-code-review -a claude-code
Open on GitHub

What python-expert-best-practices-code-review does

The skill hands the agent eight rules sorted by priority. Error handling comes first: reach for d[key] on required dictionary keys so a missing one fails fast with KeyError, and skip the broad except that swallows unexpected failures. Next are common bugs — mutable defaults in function parameters, and returning NotImplemented for operand types you do not support.

Clarity rules follow. A list comprehension has to produce a value you actually use, imports belong at the top of the file, and else blocks after return or break go away. Each rule lives in its own file under rules/, with the reasoning, a wrong example, a right one and references.

The rules target Python 3.14+. On an older branch, check the examples yourself before applying them — syntax and behaviour differ. Install runs through npx skills add; GitHub Copilot uses a different command.

What it helps with

  • catch a missing dictionary key at the point of access
  • drop a broad except that hides unrelated errors
  • spot a mutable default in a function signature
  • rewrite a list comprehension built only for side effects
  • move imports to the top and remove dead else branches

Example prompts for the agent

  • Review this module against the skill rules and point out every no-mutable-defaults violation
  • Refactor parser.py: remove the broad except and switch required dictionary lookups to d[key]
  • Check the list comprehensions in report.py for ones that never return a value

How to install python-expert-best-practices-code-review

1Skills CLI (Vercel)

npx skills add wispbit-ai/skills --skill python-expert-best-practices-code-review -a claude-code

2Manually: put the files in place

~/.claude/skills/python-expert-best-practices-code-review/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/python-expert-best-practices-code-review/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about python-expert-best-practices-code-review

How do I install python-expert-best-practices-code-review in Claude?

Run npx skills add wispbit-ai/skills --skill python-expert-best-practices-code-review -a claude-code. The skill lands at ~/.claude/skills/python-expert-best-practices-code-review/SKILL.md.

What does python-expert-best-practices-code-review do?

It gives the agent a set of Python rules covering error handling, common bugs, clarity and style. The agent applies them while writing, reviewing or refactoring code.

Which Python version do these rules cover?

The skill is written for Python 3.14+. On older versions, verify the examples before you apply them.

Source text

SKILL.md · MIT
---
name: python-expert-best-practices-code-review
description: Python best practices for writing production-grade code. This skill should be used when writing, reviewing, or refactoring Python code. Triggers on tasks involving Python development, error handling patterns, dictionary operations, and code quality improvements.
license: MIT
metadata:
  author: wispbit
  version: "1.0.0"
---

# Python 3.14+ Expert Best Practices

Simple, pragmatic, opinionated. Only what matters for writing production-grade python code.

## When to Apply

Reference these guidelines when:
- Writing Python functions, classes, or modules
- Reviewing Python code for error handling issues
- Refactoring existing Python codebases
- Implementing data validation and API boundaries
- Optimizing error detection and debugging patterns

## Rule Categories by Priority

| Priority | Category | Impact | Prefix |
|----------|----------|--------|--------|
| 1 | Error Handling | CRITICAL | `dict-`, `operators-` |
| 2 | Common Bugs | CRITICAL-HIGH | `no-mutable-`, `no-generic-` |
| 3 | Code Clarity | HIGH-MEDIUM | `listcomp-`, `no-inline-` |
| 4 | Code Style | LOW | `avoid-`, `unnecessary-` |

## Quick Reference

- `dict-required-keys` - Use `d[key]` for required dictionary keys to fail fast with KeyError
- `no-mutable-defaults` - No mutable defaults in function/method parameters
- `operators-return-notimplemented` - Return NotImplemented for unsupported operand types and design + vs += intentionally
- `no-generic-except` - Avoid generic except clauses to prevent hiding unexpected errors
- `listcomp-no-side-effects` - List comprehensions must produce a value you use (no side-effect listcomps)
- `no-inline-imports` - Place all import statements at the top of the file
- `avoid-explanatory-comments` - Avoid unnecessary comments for self-documenting code
- `unnecessary-else-blocks` - Avoid unnecessary else blocks after return/break/continue statements

## How to Use

Read individual rule files for detailed explanations and code examples:

```
rules/dict-required-keys.md
rules/no-mutable-defaults.md
rules/operators-return-notimplemented.md
rules/no-generic-except.md
rules/listcomp-no-side-effects.md
rules/no-inline-imports.md
rules/avoid-explanatory-comments.md
rules/unnecessary-else-blocks.md
```

Each rule file contains:
- Brief explanation of why it matters
- When to use and when not to use the pattern
- Implementation requirements
- Incorrect code example with explanation
- Correct code example with explanation
- Additional context and references

© wispbit · MIT · wispbit-ai/skills

Similar skills

All skills for Programming languages →

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor