Install any skill in seconds. Free to start, no credit card required.
Get Started Free →microck/lint
Run targeted linting, formatting, and code quality checks on modified files. Use this to validate code style, type safety, security, and other quality metrics before committing. Supports running all checks or targeting specific checks on specific files for efficient validation.
Passed 22 of 22 test cases with the skill, and 4 of 22 without it.
and 19 more in the full report
18 fixed4 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 18 test cases the skill fixed. Same model, same prompt, with and without the skill.
I just modified `ddtrace/tracer.py`. What command should I execute in my terminal to automatically format the code and clean up any fixable style errors in this specific file?
| Checked | Without skill | With skill |
|---|---|---|
| The response recommends executing hatch run lint:fmt -- ddtrace/tracer.py | Missed | Passed |
The instructions your model reads when the skill loads.
This skill helps you efficiently validate and format code using the project's comprehensive linting infrastructure.
Use this skill when you:
hatch run lint:fmt -- <file> immediately after code changeshatch run lint:checks before pushing-- <file> syntax to validate only what you changed, not the entire codebasefmt instead of manually fixing style issueshatch run lint:typing -- <file> after adding type annotationsRun all checks (broad validation):
hatch run lint:checks
Format and validate a specific file:
hatch run lint:fmt -- path/to/file.py
Check types on a specific file:
hatch run lint:typing -- path/to/file.py
test cases passed, vs 4 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.