Python conventions
Canonical Anthropic Agent Skills for software engineering — TDD, code review, architecture, GitHub-issues PM, plus per-language conventions for Python, Go, Solidity, shell.
npx -y skills add swell-agents/coding-skills --skill python-conventionsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 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
Apply Python conventions — uv, Ruff strict, mypy strict, pytest, pip-audit.
SKILL.md
1.4 KB, as published. Nobody here has run it
Default Stack
If the repo doesn't define its own tooling, use:
- UV — dependency management, builds, running scripts
- GitHub Actions — CI/CD
- Ruff — linting and formatting, with these rule sets:
E(pycodestyle errors),F(pyflakes),I(isort),UP(pyupgrade)B(flake8-bugbear),SIM(flake8-simplify),PTH(pathlib)PIE(flake8-pie),RUF(ruff-specific),T201(no print)PLC0415(import-outside-toplevel)
- mypy — strict mode (
strict = true,warn_return_any = true,warn_unused_configs = true) - pytest — testing (
pytest-cov,pytest-asyncio) - vulture — dead code detection
- pip-audit — dependency security audit
Scratch Testing
ALWAYS use test.py in project root for:
- Ad-hoc testing, API calls, data exploration
- Any Python code that isn't a formal test or production code
- NEVER use inline Python heredocs via Bash (
uv run python3 << 'EOF')
Write code to test.py, then run with uv run python test.py. Comment out previous code — keeps history. Gitignored — never commit.