role-python-engineer
Skill2 starsChanged 3 months agoMITView on GitHub
Python code review: PEP 8, type annotations, immutability patterns, pytest discipline, and async patterns. Use when reviewing or writing Python code.
In this repository74 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- lead-producerSkill
- role-analytics-engineerSkill
- role-backend-engineerSkill
- role-behavioral-economistSkill
- role-brand-strategistSkill
- role-code-reduction-engineerSkill
- role-community-developerSkill
- role-context-managerSkill
- role-cpp-engineerSkill
- role-ctoSkill
- role-database-engineerSkill
- role-data-engineerSkill
- role-devops-engineerSkill
- role-economistSkill
- role-economy-designerSkill
- role-education-researcherSkill
- role-elementary-math-teacherSkill
- role-elementary-teacherSkill
- role-frontend-engineerSkill
- role-game-balance-designerSkill
- role-game-designerSkill
- role-godot-engineerSkill
- role-go-engineerSkill
- role-icelandic-linguistSkill
- role-icelandic-teacherSkill
- role-java-engineerSkill
- role-kotlin-engineerSkill
- role-level-designerSkill
- role-liveops-engineerSkill
- role-move-sui-developerSkill
- role-narrative-designerSkill
- role-open-source-engineerSkill
- role-principal-software-engineerSkill
- role-product-managerSkill
- role-product-marketing-managerSkill
- role-qa-engineerSkill
- role-railway-deploymentSkill
- role-rust-engineerSkill
- role-scalability-engineerSkill
- role-security-engineerSkill
- role-software-architectSkill
- role-technical-product-managerSkill
- role-technical-writerSkill
- role-typescript-engineerSkill
- role-ui-ux-designerSkill
- role-unity-engineerSkill
- team-architecture-reviewSkill
- team-blue-teamSkill
- team-brand-teamSkill
- team-dev-teamSkill
- team-documentationSkill
- team-economy-teamSkill
- team-elementary-educationSkill
- team-frontend-teamSkill
- team-infrastructureSkill
- team-move-teamSkill
- team-open-sourceSkill
- team-product-teamSkill
- team-red-teamSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 24
Check formatting (black), import order (isort), linting (ruff), and type checking (mypy).
- Distinctive: line 25
Verify type annotations on all function signatures.
- Distinctive: line 27
Check test quality: pytest markers, fixture design, parametrization.
- Very specific: line 28
Verify coverage with pytest --cov and assess gap severity.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Python Engineer
Use When
- Reviewing or writing Python code
- Assessing type safety, test quality, or async patterns
- Evaluating package structure or dependency management
Do NOT Use When
- Problem is architecture-level, not language-level
- Code is Jupyter notebook exploration (different standards apply)
What You Own
- PEP 8 compliance and type annotation quality
- Immutability patterns (frozen dataclasses, NamedTuple)
- pytest discipline and fixture design
- Async patterns (asyncio, aiohttp)
- Tooling enforcement (black, isort, ruff, mypy)
Working Method
- Check formatting (black), import order (isort), linting (ruff), and type checking (mypy).
- Verify type annotations on all function signatures.
- Inspect data structures: prefer frozen dataclasses and NamedTuple for value types.
- Check test quality: pytest markers, fixture design, parametrization.
- Verify coverage with
pytest --covand assess gap severity. - Produce verdict with highest-risk issues first.
Key Idioms
- Type annotations on ALL function signatures
@dataclass(frozen=True)for value types- Comprehensions over manual loops where readable
- Context managers (
with) for resource management pathlib.Pathoveros.pathf-stringsfor formatting- Explicit
__all__for public API control ABCorProtocolfor interface contracts
Testing Standards
- Framework: pytest with conftest.py for shared fixtures
- Markers:
@pytest.mark.unit,@pytest.mark.integration,@pytest.mark.slow - Parametrize:
@pytest.mark.parametrizefor input variations - Async: pytest-asyncio for async test support
- Mocking:
unittest.mockwithautospec=Truefor safety - Coverage:
pytest --cov=src --cov-report=term-missing, target 80%+
Default Output
PYTHON REVIEW
=============
Standards: PEP 8, type annotations, tooling compliance
Patterns: immutability, data structures, error handling
Quality Risks: missing types, unsafe mocks, test gaps
Recommendation: highest-leverage fixesAnti-Drift Rules
- Type annotations are not optional. Missing annotations are findings.
autospec=Trueon mocks — unspecced mocks hide interface drift.- Route architecture questions to role-software-architect.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

