Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →platformplatform/lint
Lint code via the developer CLI - backend (.NET via JetBrains inspectcode), frontend (oxlint), and the developer CLI itself.
Passed 20 of 22 test cases with the skill, and 8 of 22 without it.
and 14 more in the full report
12 fixed8 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
I modified several React components in the frontend app. I want to quickly run oxlint via the project's runner. What exact command should I use?
| Checked | Without skill | With skill |
|---|---|---|
| The command uses dotnet run --project developer-cli -- lint --frontend --quiet | Missed | Passed |
| The command does not invoke npx oxlint directly | Missed | Passed |
The instructions your model reads when the skill loads.
dotnet run --project developer-cli -- lint [--backend] [--frontend] [--cli] [--self-contained-system <name>] [--no-build] [--changed-only] --quiet
Use developer-cli exactly as written - do not expand to an absolute worktree path.
--backend - .NET (JetBrains inspectcode)--frontend - React/TypeScript (oxlint)--cli - the developer CLI itself--self-contained-system <name> - narrows backend linting to one SCS (e.g. account, main)--no-build - skip the rebuild step (faster after a recent build)--changed-only - lint only .cs files changed against origin/main (much faster; see guidance below)No arguments lints the whole solution. Every finding fails CI regardless of severity - fix all of them.
After build succeeds, run format, lint, test in parallel with --no-build. Backend lint is slow - run last. Frontend lint often needs code rewrites - run after each bigger change.
--changed-onlyInspectcode has cross-file rules ("unused public method", "member can be private", flow analysis across method calls). --changed-only only inspects the listed files - it doesn't catch issues in untouched files that became invalid because of edits elsewhere.
--changed-only. Most lint findings are local (style, naming, hints) and the saving is large (~4m → ~30s).--changed-only and lint the full solution.CI always lints the full solution, so anything missed by a local --changed-only run gets caught before merge.
dotnet run --project developer-cli -- lint --quiet # everything (full solution)
dotnet run --project developer-cli -- lint --backend --changed-only --quiet # backend, changed files only (recommended for routine work)
dotnet run --project developer-cli -- lint --frontend --quiet # frontend
dotnet run --project developer-cli -- lint --backend --self-contained-system main --quiet # one SCS, full
Verbose output goes to a log file. On success the CLI prints a single line; on failure it prints where to find the findings and exits 1.
test cases passed, vs 8 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.