eslint
$ npm i -g eslintLinting, js rules, and code health from the terminal.
- eslint fits git & github well, especially for linting, js rules, and code health from the terminal.
- 86,074,114 npm weekly downloads.
- Easy to automate.
- Good fit for coding-agent workflows and repeatable scripts.
- Output is mostly text-first, so verify results before scripting around it.
Eslint guide
Linting, js rules, and code health from the terminal. Built by ESLint.
Open CLI packages the install path, verify step, and safe-start workflow so this tool can move from “interesting CLI” to something you can actually use. It also integrates with skills.sh so each CLI comes with the right companion skills, not just a binary and a docs link.
When to apply
- linting, js rules, and code health from the terminal.
- You need productivity workflows in both local dev and CI.
- You need linting.
- You need js rules.
- You need code health.
Quick reference
npm i -g eslinteslint --versioneslint .Open CLI × skills.sh
Open CLI integrates eslint with the right skills.sh companions so you get the tool and the workflow together.
Workflow Automation
Recommended pairingOpen CLI recommends this skills.sh skill because it fits productivity workflows. Turn repeated CLI sequences into cleaner, more reliable agent workflows.
$ npx skills add https://github.com/supercent-io/skills-template --skill workflow-automationUse eslint together with the Workflow Automation skills.sh skill. Start with safe inspection commands, summarize what you find, and ask before any step with side effects.
Why this tool
- eslint fits git & github well, especially for linting, js rules, and code health from the terminal.
- 86,074,114 npm weekly downloads.
- Easy to automate.
Watch-outs
- Output is mostly plain text.
Example workflow
1. eslint .Safe start
Install eslint.
Run `eslint --version` first.
Start with `eslint .`.
Install the CLI and make sure it is on your PATH.