lint-and-fix
Skill1 starsChanged 9 months agoApache-2.0View on GitHub
Run linters and fix violations, formatting errors, or style mismatches using Trunk. Use when code quality checks fail, before submitting PRs, or to repair "broken" linting states.
4 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- yu-iskw/coding-agent-skillstheir own version, first seen Mar 28, 2026
- yu-iskw/github-project-skillstheir own version, first seen Mar 23, 2026
- yu-iskw/openspec-skillstheir own version, first seen Feb 9, 2026
- yu-iskw/skill-inspectoredited, first seen Jan 23, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- yu-iskw/skill-inspector★ 251% same
Wrote their own version · 3
- yu-iskw/github-project-skills★ 10same name
- yu-iskw/coding-agent-skills★ 1same name
- yu-iskw/openspec-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .cursor/rules/tech-stack.mdcCursor rule
- build-and-fixSkill
- bumpup-versionsSkill
- clean-projectSkill
- fix-issueSkill
- improve-claude-configSkill
- initialize-projectSkill
- manage-adrSkill
- manage-changelogSkill
- node-upgradeSkill
- security-vulnerability-auditSkill
- setup-dev-envSkill
- sync-readmeSkill
- test-and-fixSkill
- test-integration-dockerSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Identify: Run pnpm lint (which executes trunk check -y and eslint .) to list current violations.
- Distinctive: line 21
If passed: Move to the next issue or finish if all are resolved.
- Distinctive: line 22
If failed: Analyze the new failure and repeat the loop.
- Very specific: line 26
No more errors reported by pnpm lint, pnpm lint:all, or pnpm lint:eslint.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Lint and Fix Loop: Trunk
Purpose
An autonomous loop for the agent to identify, fix, and verify linting and formatting violations using Trunk.
Loop Logic
- Identify: Run
pnpm lint(which executestrunk check -yandeslint .) to list current violations. For a comprehensive check across the entire project, usepnpm lint:all(executestrunk check --allandeslint .). You can also runpnpm lint:eslintfor focused ESLint checks. - Analyze: Examine the output from Trunk or ESLint, focusing on the file path, line number, and error message. Refer to ../common-references/troubleshooting.md for environment or runtime issues.
- Fix:
- For formatting issues, run
pnpm format(which executestrunk fmt). To format all files in the project, usepnpm format:all. - For linting violations, apply the minimum necessary change to the source code to resolve the error. You can use
pnpm format:eslintto automatically fix many ESLint violations. - For security-specific checks, you can run
pnpm run lint:security.
- For formatting issues, run
- Verify: Re-run
pnpm lint(orpnpm lint:allorpnpm lint:eslintdepending on what you used initially).- If passed: Move to the next issue or finish if all are resolved.
- If failed: Analyze the new failure and repeat the loop.
Termination Criteria
- No more errors reported by
pnpm lint,pnpm lint:all, orpnpm lint:eslint. - Reached max iteration limit (default: 5).
Examples
Scenario: Fixing a formatting violation
pnpm lintreports formatting issues insrc/index.ts.- Agent runs
pnpm format. pnpm lintnow passes.
Scenario: Performing a full project cleanup
- Agent runs
pnpm lint:allto check every file. - Several formatting issues are found.
- Agent runs
pnpm format:allto fix them all at once. pnpm lint:allnow passes.
Scenario: Fixing ESLint violations
pnpm lint:eslintreports several linting errors.- Agent runs
pnpm format:eslint. pnpm lint:eslintnow passes or shows fewer errors that require manual fixing.
Resources
- Project Scripts: Definitions for all lint and format scripts.
- Trunk CLI Reference: Common commands for linting and formatting.
- Trunk Documentation: Official documentation for the Trunk CLI.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.