lint-and-format
Skill1 starsChanged 3 months agoMITView on GitHub
When a repo has inconsistent style or no linter or formatter. Triggers: 'add linting', 'set up prettier/eslint/ruff', 'format the code', 'style config'. Adds the standard linter and formatter for the stack with config and a check.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- Mark-Life/peektracetheir own version, first seen Jul 29, 2026
- matteing/opaltheir own version, first seen Feb 16, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- matteing/opal★ 59same name
- Mark-Life/peektrace★ 4same 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.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- add-testsSkill
- cut-a-releaseSkill
- env-and-configSkill
- license-and-legalSkill
- one-command-runSkill
- package-for-npmSkill
- package-for-pypiSkill
- readme-that-convertsSkill
- repo-hygiene-passSkill
- security-basicsSkill
- set-up-ciSkill
- ship-checklistSkill
- ship-contextSkill
- write-a-changelogSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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 21
Keep rules pragmatic. A linter everyone disables is worse than a lean one that stays on.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Lint and Format
Consistent code reads as cared-for. You add the stack's standard formatter and linter, apply them once, and wire a check.
Before you start
Read .agents/ship.md.
Steps
- Add the standard tools: Prettier + ESLint for JS/TS, Ruff (or Black + Ruff) for Python, gofmt + golangci-lint for Go. Start from the recommended config, do not invent a bespoke one.
- Apply once across the repo in a single "style: format" commit, so real changes are not buried in reformatting later.
- Add a check: a
lintscript and a CI step (or a pre-commit hook) that fails on violations. - Keep rules pragmatic. A linter everyone disables is worse than a lean one that stays on.
Done when
npm run lint (or equivalent) passes, formatting is applied repo-wide in its own commit, and CI or a hook enforces it.
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.