
linters
Runs linters on edited files: cslint (.cs), PSScriptAnalyzer (.ps1), shellcheck (.sh), rustfmt (.rs)
- version
- 1.2.0
Install
/plugin install linters@lucasp-claude-pluginsRun it inside Claude Code after adding the marketplace with /plugin marketplace add lucaspimentel/claude-plugins.
Contents
Discovered from sourceSkills 1
Bulk-fix cslint warnings in a C# codebase, committing fixes rule-by-rule from most common to least.
Prerequisites
cslint must be on PATH. If not found, tell the user to install it:
scoop install cslint
# or: dotnet tool install --global cslint
Workflow
1. Survey
Run cslint --summary [path] to get the rule breakdown sorted by count. Only pass the path if the user specified one; cslint defaults to the current directory.
If the user passed --semantic, add that flag to all cslint commands throughout.
If the summary shows zero violations, inform the user and stop.
Show the user the summary table and total count. Ask them to confirm before proceeding, or let them exclude specific rules.
2. Fix rules from most-common to least-common
Skip any rules the user excluded. For each remaining rule (starting with the highest count):
- Run
cslint --rules <RULE_ID> --format json [path]to get all violations with file paths and line numbers - Read the affected files and fix all violations for that rule
- Re-run
cslint --rules <RULE_ID> --format json [path]to verify zero remaining violations for that rule - If violations remain, fix them and re-verify (max 3 attempts per rule, then move on and warn the user)
- Stage and commit:
"Fix <RULE_ID>: <RuleName> (<count> violations)"— get the rule name from the"name"field in--format jsonoutput or--list-rules.
3. Grouping threshold
Once the remaining rules each have 5 or fewer violations, group all remaining fixes into a single commit:
- Fix all remaining rules together
- Re-run
cslint --summary [path]to verify - Commit:
"Fix remaining cslint warnings (<total_count> violations across <rule_count> rules)"
4. Final verification
Run cslint [path] (omit path if none was specified) (with --semantic if the user requested it) and confirm zero violations.
If any remain, report them to the user — they may be false positives or require manual intervention.
cslint CLI reference
cslint [<path>...] [options]
Key options:
--summary Show diagnostics grouped by rule ID (use for planning)
--rules <IDs> Comma-separated rule IDs, or 'all' (ignores .editorconfig)
--semantic Enable Tier 4 rules (unused usings, unused locals, etc.)
--exclude Glob patterns to exclude (e.g., **/Generated/*.cs)
--severity Minimum severity: info, warning, error
--format Output format: text, json, sarif
--list-rules List all available rules with metadata (JSON)
Output format (text): path/File.cs(line,col): severity RULEID: Message
Exit codes: 0 = clean, 1 = violations, 2 = error
Rules by tier
- Tier 1 (Formatting): indentation, whitespace, line endings, max line length, encoding
- Tier 2 (Naming): PascalCase, interface prefix, camelCase params, _camelCase fields
- Tier 3 (Style): var usage, expression-bodied, braces, namespaces, sealed, member ordering
- Tier 4 (Semantic, --semantic only): unused usings, unused locals, unreachable code, unnecessary casts
Important notes
- Do NOT use
--semanticunless the user explicitly requests it - Some rules (e.g., CSLINT252 SingleTypePerFile, CSLINT251 FieldsMustBePrivate) may require significant refactoring — warn the user and ask before fixing these
- If
.editorconfigis missing, cslint uses defaults — mention this to the user if relevant - Use
--excludeto skip generated files (e.g.,**/obj/**,**/*.g.cs,**/Generated/*.cs) — suggest this if the survey shows noise from generated code - The linters plugin's PostToolUse hook runs
cslinton every file edit. During this bulk-fix workflow, ignore the hook's lint output — you are already verifying fixes with--rulesafter each batch
Hooks 2
Sponsors
Details
- Marketplace
- lucaspimentel/claude-plugins
- Source
- plugins/linters
- Category
- Community