fix-lint
Skill15 starsChanged 5 months agoMITView on GitHub
Fix Biome linting/formatting errors in 1-3 files using auto-fix and minimal manual edits. Use proactively for lint issues.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- vladmandic/sdnexttheir own version, first seen Oct 8, 2026
- nudgebee/nudgebeetheir own version, first seen Aug 24, 2026
- leaf76/agent-skillstheir own version, first seen Aug 17, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- vladmandic/sdnext★ 7.4ksame name
- nudgebee/nudgebee★ 520same name
- leaf76/agent-skills★ 0same 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 repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- public/llms-full.txtllms.txt
- public/llms.txtllms.txt
- add-componentSkill
- add-diagram-componentSkill
- add-languageSkill
- add-pageSkill
- ai-diff-reviewerSkill
- dailybotSkill
- deepworkplanSkill
- doc-editSkill
- git-commit-pushSkill
- pr-review-liteSkill
- quick-fixSkill
- refactor-safeSkill
- responsive-lighthouse-auditSkill
- security-checkSkill
- translate-syncSkill
- type-fixSkill
- update-stylesSkill
- write-testsSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 8 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 24
Does NOT fix TypeScript type errors (use type-fix or Tier 2)
- Distinctive: line 25
Does NOT refactor logic or add features
- Distinctive: line 26
Does NOT modify more than 3 files
- Distinctive: line 27
Does NOT change behavior
- Distinctive: line 47
Before running this skill, ensure:
- Distinctive: line 64
Read remaining Biome messages
- Distinctive: line 66
Do not change logic
- Distinctive: line 116
Stop and escalate: if:
“Common” is measured: kept by at least 6 in 10 of the 3 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
Skill: Fix Lint
Objective
Fix Biome linting and formatting errors in specified files: run pnpm run biome:fix (or equivalent), then resolve any remaining issues with minimal manual edits. Adapted for this repo: Astro, TypeScript, Biome; no logic changes; follow AGENTS.md conventions.
Non-Goals
- Does NOT fix TypeScript type errors (use type-fix or Tier 2)
- Does NOT refactor logic or add features
- Does NOT modify more than 3 files
- Does NOT change behavior
Tier Classification
Tier: 1 - Light/Cheap
Reasoning: Mechanical fixes (formatting, rule compliance); small scope (1–3 files, <100 LOC); low risk.
Inputs
Required Parameters
$FILES: File(s) to fix (paths or "current file"); optional — default to files reported by Biome
Optional Parameters
$RULES: Specific rules to focus on (default: all reported)
Prerequisites
Before running this skill, ensure:
- No uncommitted changes or working on a dedicated branch
- Biome config is present (biome.json)
Steps
Step 1: Run Auto-Fix
pnpm run biome:fix
# or for specific files:
pnpm exec biome check --write "path/to/files"Step 2: Address Remaining Issues
- Read remaining Biome messages
- Apply minimal edits (e.g., add missing types, fix import order per AGENTS.md)
- Do not change logic
Step 3: Validate
pnpm run biome:check
pnpm run astro:checkOutput Format
Success Output
## ✅ Lint Fix Complete
### Files
- `{file1}`: {what was fixed}
- `{file2}`: {what was fixed}
### Validation
- pnpm run biome:check: ✅
- pnpm run astro:check: ✅
### Commit Message
style: fix Biome issues in {files}Escalation
## ❌ Fix Lint Not Enough
### Reason
{Remaining issues require type changes / refactor / many files}
### Recommendation
Escalate to Tier 2 or use quick-fix for logical issues.Guardrails
Scope Limits
- Maximum files: 3
- Maximum LOC changed: 100
- Allowed: Style, import order, simple rule compliance
Stop Conditions
Stop and escalate if:
- Fixes require logic changes or new types across many files
- More than 3 files need changes
- Auto-fix causes build failures (revert and escalate)
Definition of Done
pnpm run biome:checkpasses for modified filespnpm run astro:checkpasses- No behavior change
Related
- quick-fix - Small bug fixes
- doc-edit - Docs only
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.

