
python-code-quality
Code quality checks, linting, formatting, and type checking commands for the Agent Framework Python codebase. Use this when running checks, fixing lint errors, or troubleshooting CI failures.
- Installs
- 97
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/microsoft/agent-framework --skill python-code-quality- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads python-code-quality automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Python Code Quality
Quick Commands
All commands run from the python/ directory:
# Syntax formatting + checks (parallel across packages by default)
uv run poe syntax
uv run poe syntax -P core
uv run poe syntax -F # Format only
uv run poe syntax -C # Check only
uv run poe syntax -S # Samples only
# Type checking
#
# Division of labor (see "Type checking architecture" below):
# - Pyright (strict) is the source-code type checker.
# - Pyright (relaxed `basic`), mypy, pyrefly, ty, zuban all check the TESTS;
# pyright/pyrefly/ty also check the SAMPLES (mypy/zuban skip script-style samples).
uv run poe pyright # Pyright (strict) over SOURCE, fan-out across packages
uv run poe pyright -P core
uv run poe pyright -A
uv run poe test-typing # mypy + pyrefly + ty + zuban + pyright over each package's TESTS
uv run poe test-typing -P core
uv run poe test-typing -S # samples (pyrefly + ty + pyright)
uv run poe test-typing -P core --checker mypy # narrow to one checker (repeatable)
uv run poe test-typing -P core --checker pyright # relaxed pyright over the tests
uv run poe mypy # alias: MyPy over the tests only
uv run poe mypy -P core
uv run poe typing # Pyright (source) + the tests checkers
uv run poe typing -P core
uv run poe typing -A
# All package-level checks in parallel (syntax + pyright)
uv run poe check-packages
# Full check (packages + samples + tests + markdown)
uv run poe check
uv run poe check -P core
# Samples only
uv run poe check -S
uv run poe pyright -S
# Markdown code blocks
uv run poe markdown-code-lint
Poe and the pytest toolchain stay in the cross-version development
environment. Ruff and the type checkers use pinned
tooling/requirements-*.txt files; prek is selected from the tool-hooks
dependency group only when needed.
Pre-commit Hooks (prek)
Prek hooks run automatically on commit. They stay lightweight and only check changed files.
# Install hooks
uv run poe prek-install
# Run all hooks manually
uv run --group tool-hooks prek run -a
# Run on last commit
uv run --group tool-hooks prek run --last-commit
They run changed-package syntax formatting/checking, markdown code lint only
when markdown files change, and sample syntax lint/pyright only when files
under samples/ change.
They intentionally do not run workspace pyright or mypy by default.
Type checking architecture
Following the "too many type checkers" approach, type checkers are split by target:
| Target | Checker(s) | Mode | Config |
|---|---|---|---|
Source (agent_framework*) | pyright | strict | [tool.pyright] in pyproject.toml |
| Tests | pyright, mypy, pyrefly, ty, zuban | relaxed/basic | pyrightconfig.tests.json, [tool.mypy], pyrefly.toml, ty rules |
| Samples | pyright, pyrefly, ty | basic | pyrightconfig.samples.json, pyrefly.samples.toml, ty.samples.toml |
- Pyright is the only strict source-code checker, and it ALSO runs in a relaxed
basicprofile over the tests and samples (so the surfaces customers copy from are validated by every checker, including pyright). MyPy was removed from source; its[tool.mypy]block is now a relaxed profile used only for tests/samples. - The extra checkers run over tests/samples because those exercise the public API the way users do. The profile is intentionally relaxed (private access allowed, untyped test bodies allowed) so authors aren't forced into ugly over-annotation.
- Gating checkers are
pyright,mypy,pyrefly,ty, andzuban— all five run by default and gate CI.zubanis the strictest of the mypy-compatible pair, so the same[tool.mypy]config yields more findings; suppress zuban-only friction with shared# type: ignore[code]. Suppress relaxed-pyright friction with# pyright: ignore[rule]. - Samples add
pyrighttopyrefly+ty— mypy/zuban can't resolve script-style sample layouts (numeric-prefixed dirs, duplicatemain.py), but pyright handles them. pyrefly.samples.tomlenables fallback lookup for standalone sibling imports. The ty sample profile uses first-partyroot = ["."]for PEP 723 sibling helpers, preserving automatic extra-path lookup for the existing samples.- The strict source-pyright (
[tool.pyright]) enforcesreportUnnecessaryTypeIgnoreCommentand excludes tests/samples; the relaxed test/sample pyright configs do not flag unnecessary ignores.
Ruff Configuration
- Line length: 120
- Target: Python 3.10+
- Auto-fix enabled
- Rules: ASYNC, B, CPY, D, E, ERA, F, FIX, I, INP, ISC, Q, RET, RSE, RUF, SIM, T20, TD, W, T100, S
- Scripts directory is excluded from checks
Pyright Configuration
- Source: strict mode (
[tool.pyright]),reportUnnecessaryTypeIgnoreComment = "error", excludes tests, samples, .venv, packages/devui/frontend. - Tests: relaxed
basicprofile (pyrightconfig.tests.json) — private import/usage and not-required TypedDict access allowed; runs as thepyrightchecker intest-typing. - Samples: relaxed
basicprofile (pyrightconfig.samples.json, with a py310 variant) — runs as thepyrightchecker intest-typing -S.
Parallel Execution
The task runner (scripts/task_runner.py) executes the cross-product of
(package × task) in parallel using ThreadPoolExecutor. Single items run
in-process with streaming output.
CI Workflow
CI splits into 4 parallel jobs:
- Pre-commit hooks — lightweight hooks (SKIP=poe-check)
- Package checks — syntax/pyright (source) via check-packages
- Samples & markdown —
check -Splusmarkdown-code-lint - Test Typing — change-detected mypy/pyrefly/ty over tests (
ci-test-typing)
FAQ
What does the python-code-quality skill do?
Code quality checks, linting, formatting, and type checking commands for the Agent Framework Python codebase. Use this when running checks, fixing lint errors, or troubleshooting CI failures.
How do I install python-code-quality?
Run npx skills add https://github.com/microsoft/agent-framework --skill python-code-quality in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/python-code-quality/ (personal) or .claude/skills/python-code-quality/ (project).
Which AI agents can use python-code-quality?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is python-code-quality safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains python-code-quality?
It is published by microsoft in microsoft/agent-framework, and it is an official skill from the maker of the technology it covers. It has 97 recorded installs.
More from microsoft/agent-framework
python-development
microsoft/agent-framework
Open the skill to read its SKILL.md instructions.
build-and-test
microsoft/agent-framework
Open the skill to read its SKILL.md instructions.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.