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.
Installs into .claude/skills of the current project.
Are you the author of Superlint?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/mgechev-superlint)
# SuperLint Proprietary Workflow
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.
## 1. Description
SuperLint is a multi-stage validation tool. Standard ESLint or Prettier commands will NOT work.
## 2. Mandatory Workflow
To fix a file using SuperLint, you MUST follow these steps in order:
1. **Check**: Run `superlint check` to generate a report.
2. **Fix**: Run `superlint fix --target <filename>` to apply automated corrections.
3. **Verify**: Run `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.
## 3. Examples
```bash
# Correct usage for app.js
superlint check
superlint fix --target app.js
superlint verify
```
