菜单
Lint and format a Python project with the prek hook runner. Use when checking or cleaning the working tree, resolving lint/format/type/complexity/spelling failures, or understanding what each linter config enforces.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Write agent output for the accountable human reviewer — route narrative by audience and lifespan, lead with a budgeted summary, keep detail collapsed, and plan before building. Use when writing PR or issue descriptions, commit messages, or code comments, when addressing or resolving PR review comments, when deciding whether to raise an issue or where work-narrative belongs, or when scoping a non-trivial change before generating code.
Write asyncio Python to this project's standards — concurrent coroutines, async-all-the-way, and safe handling of errors from concurrent tasks. Use when writing async/await code, gathering coroutines, designing async FastAPI endpoints or clients, or handling failures from concurrent work.
Write Python source to this project's standards. Use when authoring or refactoring Python code and deciding on style, type hints, docstrings, comments, imports, or language idioms.
Work with dates, times, and timezones to this project's standards. Use when creating, parsing, serialising, comparing, or storing datetimes, or handling timezones.
Handle errors in Python to this project's standards — custom domain exceptions, narrow catches, and failing fast. Use when raising or catching exceptions, writing try/except, designing an exceptions module, or deciding whether to swallow or propagate an error.
Reach for this project's preferred, well-supported libraries instead of hand-rolling. Use when choosing a library for HTTP, retries, JSON, or parsing, or whenever you are about to write something the standard library or a maintained package already does.
| name | python-lint-format |
| description | Lint and format a Python project with the prek hook runner. Use when checking or cleaning the working tree, resolving lint/format/type/complexity/spelling failures, or understanding what each linter config enforces. |
This project runs its linters and formatters through prek, a pre-commit-compatible hook runner. The hooks cover Python style/typing as well as Markdown, YAML, and spelling.
A clone does not install prek's hooks — each developer installs them, and forgetting on a fresh clone silently skips the checks:
prek install --install-hooks --overwrite
This is idempotent: re-run it if commits complete without the checks running. It needs a
prek.toml or .pre-commit-config.yaml present (the --install-hooks step also prepares
each hook's environment).
To verify the hooks are installed — cross-platform, via uv/Python rather than
shell-specific grep/Select-String (the shim's header reads # File generated by prek):
uv run python -c "import pathlib, subprocess; p = pathlib.Path(subprocess.run(['git', 'rev-parse', '--git-path', 'hooks'], capture_output=True, text=True).stdout.strip(), 'pre-commit'); print('installed' if p.is_file() and 'generated by prek' in p.read_text() else 'not installed')"
prek run --all-files
git add new files first.Each hook is driven by a config file at the repo root:
| Config file | Tool | Enforces |
|---|---|---|
ruff.toml | Ruff | Code style and linting |
mypy.ini | mypy | Static type checking |
.complexipy.toml | complexipy | Code complexity limits |
.rumdl.toml | rumdl | Markdown linting |
.ryl.toml | ryl | YAML linting |
typos.toml | typos | Spelling |