Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →mkurman/lint
Lint and format code. Auto-detects ESLint, Biome, Prettier, or language-native formatters and runs them with auto-fix. Reports remaining issues with actionable suggestions.
Passed 11 of 17 test cases with the skill, and 6 of 17 without it.
and 6 more in the full report
7 fixed7 passed either way7 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
Several files in the workspace only have indentation and whitespace formatting issues. What note should be provided for these files?
| Checked | Without skill | With skill |
|---|---|---|
| States that running `--fix` will safely resolve formatting-only issues. | Missed | Passed |
The instructions your model reads when the skill loads.
|------|------|---------| | ... | ... | ... | ... |
| File | Line | Rule | Message |
|---|---|---|---|
| ... | ... | ... | ... |
/lint --fix to apply)
**Step 4: Suggest fixes for common issues**
For the most frequent issues, provide brief actionable guidance:
- If the same rule appears 5+ times, suggest a bulk fix or config change.
- For unused imports/variables, list them for quick removal.
- For formatting-only issues, note that `--fix` will resolve them safely.
- For issues that cannot be auto-fixed, provide a one-line explanation of how to resolve each unique rule violation.
</execution>
<critical_rules>
1. **Never modify files without `--fix`**: Default mode is report-only. Respect the user's working tree.
2. **Use the project's own config**: Do not invent lint rules. Use whatever config files exist in the project.
3. **Use the project's installed version**: Always prefer `npx`, `cargo`, or the project-local binary. Do not use globally installed tools unless no local version exists.
4. **Handle missing tools gracefully**: If a config file exists but the tool is not installed, inform the user and provide the install command (e.g., `npm install --save-dev eslint`).
5. **Respect `.gitignore` and ignore patterns**: Do not lint `node_modules`, `dist`, `build`, `target`, `.git`, or other commonly ignored directories. Most tools handle this automatically; verify they do.
6. **Limit output**: If there are more than 50 issues, show the first 30 grouped by severity, then summarize the rest with counts per file. Do not flood the user with hundreds of lines.
7. **Exit cleanly**: After presenting results, do not take further action. Let the user decide next steps.
</critical_rules>
test cases passed, vs 6 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.