Automated summary
Runs code quality checks using ruff and mypy, with optional auto-fixing and directory scoping.
Strengths
- Combines two powerful tools (ruff and mypy) in a single command
- Auto-fixes many violations with --fix flag
- Allows focusing on a specific directory for faster checks
Limitations
- Requires preconfigured pyproject.toml settings
- Only supports Python, not other languages
- Auto-fix may change code in unintended ways
Use this skill when you need to quickly lint and type-check Python code before committing, reviewing, or integrating.
Avoid this skill if you are working with non-Python code, or if you need a more specialized linter not covered by ruff.
Security analysis
SafeThe skill only runs code linting and type-checking tools (ruff, mypy) via bash, with no destructive actions, network exfiltration, or obfuscation. File modifications are limited to safe auto-fixes (e.g., import sorting).
No concerns found
How this analysis is madeExamples
/lint/lint --fix --mypy/lint services/apiname: lint description: Run code quality checks with ruff and mypy argument-hint: "[--fix|--mypy|path]"
Code Quality Checker
Run linting and type checking on the codebase.
Usage
/lint- Run ruff on all Python files/lint --fix- Auto-fix ruff violations/lint --mypy- Also run mypy type checking/lint services/api- Lint specific directory/lint --fix --mypy- Fix issues and run type checks
Tools
- ruff - Fast Python linter (replaces flake8, isort, pyupgrade)
- mypy - Static type checker
Configuration
All tools configured in pyproject.toml:
- Line length: 120
- Target: Python 3.11
- Rules: E, W, F, I, B, C4, UP, S (security), and more
Instructions
When this skill is invoked:
-
Parse arguments:
--fix: Useruff check --fixinstead ofruff check--mypy: Also run mypy after ruff- Path argument: Limit scope to that path
-
Run ruff:
ruff check ${PATH:-.} $FIX_FLAG -
If
--mypyspecified, run mypy:mypy ${PATH:-services libs} -
Report results:
- Number of issues found/fixed
- Categorize issues (style, imports, security, types)
- For unfixed issues, explain how to resolve
-
Common issue categories:
- I001: Import sorting - use
--fixorruff check --select I --fix - F401: Unused imports - remove or mark with
# noqa: F401 - S101: Assert in non-test - move to test file or use proper validation
- B008: Function call in default arg - use
Nonedefault with internal check
- I001: Import sorting - use
Design-to-Dev Specification Writer
Development
Translate your mockups into technical specifications for developers.
Exports & Barrel Files
Development
Defines conventions for module exports and barrel files: named exports only, no flat wildcards (except `export * as Name` for compound components), sectioned comments, types alongside values, and one export line per source file. Helps maintain consistent, tree-shakeable exports in portal apps using Turbopack or similar bundlers.
Write an Agent Skill
Development
Step-by-step guide to create a structured Agent Skill for coding agents, including directory structure, SKILL.md format, and design principles.