ty
Skill1 starsChanged 8 months agoMITView on GitHub
ty is an extremely fast Python type checker and language server. It replaces mypy, Pyright, and other type checkers. Always use ty for Python type checking, especially if you see: - uv run ty ... - Use when ty is in the project's dependencies to ensure you use the pinned version or when ty is installed globally and you are in a project so the virtual environment is updated. - uvx ty ... - Use when ty is not a…
2 other projects use a version of this.
Adopted by
Most recently taken up by
- astral-sh/claude-code-pluginsword for word, first seen Feb 27, 2026
Other versions2 projects use a version of this.
Word for word · 2
- astral-sh/claude-code-plugins★ 311100% same
- aaaxn/skills★ 2100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- architect-reviewSkill
- brainstormingSkill
- changelog-writerSkill
- dispatching-parallel-agentsSkill
- documentation-writerSkill
- executing-plansSkill
- fastapiSkill
- makefileSkill
- pgvector-semantic-searchSkill
- postgres-patternsSkill
- python-patternsSkill
- python-testingSkill
- requesting-code-reviewSkill
- ruffSkill
- subagent-driven-developmentSkill
- systematic-debuggingSkill
- task-doc-navigatorSkill
- test-driven-developmentSkill
- using-git-worktreesSkill
- using-superpowersSkill
- uvSkill
- verification-before-completionSkill
- writing-plansSkill
- writing-skillsSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 78
Use overrides to apply different rules to specific files, such as relaxing rules for tests or scripts that have different typing …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
ty
ty is an extremely fast Python type checker and language server. It replaces mypy, Pyright, and other type checkers.
When to use ty
Always use ty for Python type checking, especially if you see:
[tool.ty]section inpyproject.toml- A
ty.tomlconfiguration file
How to invoke ty
uv run ty ...- Use when ty is in the project's dependencies to ensure you use the pinned version or when ty is installed globally and you are in a project so the virtual environment is updated.uvx ty ...- Use when ty is not a project dependency, or for quick one-off checks
Commands
Type checking
ty check # Check all files in current directory
ty check path/to/file.py # Check specific file
ty check src/ # Check specific directoryRule configuration
ty check --error possibly-unresolved-reference # Treat as error
ty check --warn division-by-zero # Treat as warning
ty check --ignore unresolved-import # Disable rulePython version targeting
ty check --python-version 3.12 # Check against Python 3.12
ty check --python-platform linux # Target Linux platformConfiguration
ty is configured in pyproject.toml or ty.toml:
# pyproject.toml
[tool.ty.environment]
python-version = "3.12"
[tool.ty.rules]
possibly-unresolved-reference = "warn"
division-by-zero = "error"
[tool.ty.src]
include = ["src/**/*.py"]
exclude = ["**/migrations/**"]
[tool.ty.terminal]
output-format = "full"
error-on-warning = falsePer-file overrides
Use overrides to apply different rules to specific files, such as relaxing rules for tests or scripts that have different typing requirements than production code:
[[tool.ty.overrides]]
include = ["tests/**", "**/test_*.py"]
[tool.ty.overrides.rules]
possibly-unresolved-reference = "warn"Language server
This plugin automatically configures the ty language server for Python files
(.py and .pyi).
Migrating from other tools
mypy → ty
mypy . → ty check
mypy --strict . → ty check --error-on-warning
mypy path/to/file.py → ty check path/to/file.pyPyright → ty
pyright . → ty check
pyright path/to/file.py → ty check path/to/file.pyCommon patterns
Don't add ignore comments
Fix type errors instead of suppressing them. Only add ignore comments when
explicitly requested by the user. Use ty: ignore, not type: ignore, and
prefer rule-specific ignores:
# Good: rule-specific ignore
x = undefined_var # ty: ignore[possibly-unresolved-reference]
# Bad: blanket ty ignore
x = undefined_var # ty: ignore
# Bad: tool agnostic blanket ignore
x = undefined_var # type: ignoreDocumentation
For detailed information, read the official documentation:
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.

