Complete Python toolkit for Claude Code — 20 skills, 11 agents, 11 commands for FastAPI, Django, SQLAlchemy, pytest, Allure, PostgreSQL, Redis, ClickHouse, Docker and more
This repository also configures its own agents. See what claude-code-python-stack tells them →
manikosto/claude-code-python-stack
Command Claude Code
Generate OOP-based API test suite with httpx, Pydantic models, Allure reporting, and proper test data factories. Invokes api-test-writer agent.
manikosto/claude-code-python-stack
Command Claude Code
Incrementally fix build and type errors with minimal, safe changes.
manikosto/claude-code-python-stack
Command Claude Code
Comprehensive security and quality review of uncommitted changes.
manikosto/claude-code-python-stack
Command Claude Code
Look up current documentation for a library or topic via Context7.
manikosto/claude-code-python-stack
Command Claude Code
Restate requirements, assess risks, and create step-by-step implementation plan. WAIT for user CONFIRM before touching any code.
manikosto/claude-code-python-stack
Command Claude Code
Comprehensive Python code review for PEP 8 compliance, type hints, security, and Pythonic idioms. Invokes the python-reviewer agent.
manikosto/claude-code-python-stack
Command Claude Code
Review test automation code for OOP compliance, Allure metadata, proper abstractions, and flaky patterns. Invokes qa-reviewer agent.
manikosto/claude-code-python-stack
Command Claude Code
Safely identify and remove dead code with test verification at every step.
manikosto/claude-code-python-stack
Command Claude Code
Enforce test-driven development workflow. Write tests FIRST, then implement minimal code to pass. Ensure 80%+ coverage.
manikosto/claude-code-python-stack
Command Claude Code
Analyze test coverage, identify gaps, and generate missing tests to reach 80%+ coverage.
manikosto/claude-code-python-stack
Command Claude Code
Run comprehensive verification on current Python codebase state.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: