plugins/python-engineering/skills/lint/SKILL.md
Runs deterministic Python quality checks against a path or scope — formatting, linting, type checking, and typing-boundary policy. Use when checking or fixing code quality via prek, ruff, ty, pytest, or the check-typing-boundaries policy script. Reports results grouped by category; fixes only when explicitly requested.
npx skillsauth add jamie-bitflight/claude_skills lintInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Deterministic quality check workflow.
Scope: $ARGUMENTS
.pre-commit-config.yaml and CI config# Linting, formatting, and type checking
uv run prek run --files $ARGUMENTS
# Fallback when no .pre-commit-config.yaml:
# uv run ruff format --check $ARGUMENTS
# uv run ruff check $ARGUMENTS
# Tests (if scope includes test files)
uv run pytest $ARGUMENTS -v --tb=short
# Typing boundary policy (Any outside boundary modules)
bash ${CLAUDE_PLUGIN_ROOT}/scripts/check-typing-boundaries.sh $ARGUMENTS
Group results by category:
## Lint Results
### Formatting
✅ Pass / ❌ Fail (N issues)
### Linting
✅ Pass / ❌ Fail (N issues: list rule IDs)
### Type Checking
✅ Pass / ❌ Fail (N issues)
### Policy
✅ Pass / ❌ Fail (Any usage outside boundary modules: list files)
development
When an application needs to store config, data, cache, or state files. When designing where user-specific files should live. When code writes to ~/.appname or hardcoded home paths. When implementing cross-platform file storage with platformdirs.
testing
Enforce mandatory pre-action verification checkpoints to prevent pattern-matching from overriding explicit reasoning. Use this skill when about to execute implementation actions (Bash, Write, Edit) to verify hypothesis-action alignment. Blocks execution when hypothesis unverified or action targets different system than hypothesis identified. Critical for preventing cognitive dissonance where correct diagnosis leads to wrong implementation.
tools
Reference guide for the Twelve-Factor App methodology — 15 principles (12 original + 3 modern extensions) for building portable, resilient, cloud-native applications. Use when evaluating application architecture, designing cloud-native services, reviewing codebases for methodology compliance, advising on configuration, scaling, observability, security, and deployment patterns. Incorporates the 2025 open-source community evolution and cloud-native reinterpretations of each factor.
tools
Converts user-facing documentation (how-to guides, tutorials, API references, examples) in any format — Markdown, PDF, DOCX, PPTX, XLSX, AsciiDoc, RST, HTML, Jupyter notebooks, man pages, TOML/YAML/JSON configs, and plain text — into Claude Code skill directories with SKILL.md plus thematically grouped references/*.md files. Use when given a docs directory or mixed-format documentation to transform into an AI skill. Uses MCP file-reader server for binary formats.