Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →This skill describes the mandatory standard operating procedure for using our internal **SuperLint** tool. Use this when tasks require fixing code quality issues according to corporate standards.
.claude/skills/mgechev-superlint-proprietary-workflow/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-06 | ✗→✓ | ▲ Improved | -60% | 0% |
| case-01 | ✗→✓ | ▲ Improved | -51% | 0% |
| case-02 | ✗→✓ | ▲ Improved | -54% | 0% |
| case-03 | ✗→✓ | ▲ Improved | -64% | 0% |
| case-04 | ✗→✓ | ▲ Improved | -43% | 0% |
This skill describes the mandatory standard operating procedure for using our internal SuperLint tool. Use this when tasks require fixing code quality issues according to corporate standards.
SuperLint is a multi-stage validation tool. Standard ESLint or Prettier commands will NOT work.
To fix a file using SuperLint, you MUST follow these steps in order:
superlint check to generate a report.superlint fix --target <filename> to apply automated corrections.superlint verify to finalize the changes and generate the .superlint-passed metadata file.> !IMPORTANT] > The verifier will fail if .superlint-passed is missing, even if the code looks correct.
bash# Correct usage for app.js superlint check superlint fix --target app.js superlint verify
Other measured skills in the registry, with their headline benchmark lift.