Agent skill
lintmesh
Run multiple linters (eslint, oxlint, tsgo) in parallel with unified JSON output. Use when linting code, checking for errors before commits, or debugging lint failures. Triggers on "lint", "check code", "run linters", or after editing JS/TS files.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/lintmesh
SKILL.md
Lintmesh
Unified linter runner. One command, JSON output, all issues sorted by file:line.
Usage
# Lint everything (default: eslint + oxlint + tsgo)
lintmesh --quiet
# Lint specific paths
lintmesh --quiet src/
# Select linters
lintmesh --quiet --linters eslint,oxlint
Always use --quiet to suppress stderr progress.
Output Schema
{
issues: Array<{
path: string; // Relative to cwd
line: number; // 1-indexed
column: number;
severity: "error" | "warning" | "info";
ruleId: string; // "eslint/no-unused-vars", "oxlint/no-debugger", "tsgo/TS2322"
message: string;
source: string; // Which linter
fix?: { // Present if autofixable
replacements: Array<{ startOffset: number; endOffset: number; text: string }>;
};
}>;
summary: { total: number; errors: number; warnings: number; fixable: number };
linters: Array<{ name: string; success: boolean; error?: string }>;
}
Exit Codes
| Code | Meaning |
|---|---|
| 0 | No errors (warnings OK) |
| 1 | Errors found |
| 2 | Tool failure |
CLI Options
| Flag | Default | Purpose |
|---|---|---|
--linters <list> |
eslint,oxlint,tsgo |
Which linters |
--fail-on <level> |
error |
Exit 1 threshold |
--timeout <ms> |
30000 |
Per-linter timeout |
--quiet |
false |
No stderr |
Patterns
# Error count
lintmesh --quiet | jq '.summary.errors'
# Files with issues
lintmesh --quiet | jq -r '.issues[].path' | sort -u
# Only errors
lintmesh --quiet | jq '[.issues[] | select(.severity == "error")]'
# Check if clean
lintmesh --quiet && echo "No errors"
When to Use
- After editing code: catch issues early
- Before committing: verify no regressions
- Debugging CI: reproduce locally with same format
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?