Ultracite
agustinusnathaniel/nextarter-tailwind
Ultracite is a zero-config linting and formatting preset for JavaScript/TypeScript projects.
A skill your agent uses when reviewing scripts, client components, bundles, or runtime behavior related to Lint JavaScript code.
Install Javascript Linter
$ npx skills add thedaviddias/Front-End-Checklist --skill javascript-linter -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install thedaviddias/Front-End-Checklist javascript-linter --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/javascript-linter .claude/skills/javascript-linter && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "javascript-linter" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/javascript-linter into .claude/skills/javascript-linter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "javascript-linter", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/javascript-linterType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add thedaviddias/Front-End-Checklist --skill javascript-linter -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install thedaviddias/Front-End-Checklist javascript-linter --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/javascript-linter .agents/skills/javascript-linter && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "javascript-linter" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/javascript-linter into .agents/skills/javascript-linter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "javascript-linter", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedaviddias/Front-End-Checklist --skill javascript-linter -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install thedaviddias/Front-End-Checklist javascript-linter --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/javascript-linter .cursor/skills/javascript-linter && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "javascript-linter" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/javascript-linter into .cursor/skills/javascript-linter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "javascript-linter", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/thedaviddias/Front-End-Checklist.git --path skills/javascript-linter--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add thedaviddias/Front-End-Checklist --skill javascript-linter -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install thedaviddias/Front-End-Checklist javascript-linter --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/javascript-linter .gemini/skills/javascript-linter && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "javascript-linter" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/javascript-linter into .gemini/skills/javascript-linter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "javascript-linter", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install thedaviddias/Front-End-Checklist javascript-linterInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add thedaviddias/Front-End-Checklist --skill javascript-linter -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/javascript-linter .github/skills/javascript-linter && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "javascript-linter" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/javascript-linter into .github/skills/javascript-linter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "javascript-linter", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedaviddias/Front-End-Checklist --skill javascript-linter -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install thedaviddias/Front-End-Checklist javascript-linter --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/javascript-linter .opencode/skills/javascript-linter && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "javascript-linter" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/javascript-linter into .opencode/skills/javascript-linter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "javascript-linter", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
javascript-linter- GitHub stars
- 74k
- Token cost
- ~446 tokens
- SKILL.md length
- 169 words
- Files
- 2 (incl. references)
- Skills in repo
- 390
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when reviewing scripts, client components, bundles, or runtime behavior related to Lint JavaScript code.
- Reviewing scripts
- SKILL.md covers Quick Reference, Check, Fix and Explain, plus 1 more section
- Calls pnpm
- Client components
What it does
Javascript Linter is an agent skill from thedaviddias/Front-End-Checklist. Use when reviewing scripts, client components, bundles, or runtime behavior related to Lint JavaScript code. Inspect both source code and the browser execution path so fixes target the real bottleneck or bug.
Its SKILL.md is about 450 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/rule.md`).
It sits in Development, covering Linting and formatting. It works with JavaScript and ESLint. The repository describes itself as: 🗂 The essential checklist for modern web development, for humans and AI agents. The licence is MIT.
When your agent uses it
- Reviewing scripts
- Client components
- Runtime behavior related to Lint JavaScript code
Example prompts
- “/javascript-linter”
What it can do on your machine
Read from SKILL.md and the folder at commit e8d14d0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
pnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
frontendchecklist.io
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Javascript Linter loads about 446 tokens when it runs, and up to ~8k if it reads all its reference files. Until then it costs about 57 tokens; SKILL.md has 169 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from thedaviddias/Front-End-Checklist at commit e8d14d0, republished under its MIT licence (© thedaviddias). 169 words, ~446 tokens.
Download SKILL.mdSave it as
.claude/skills/javascript-linter/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- javascript-linter
- description
- Use when reviewing scripts, client components, bundles, or runtime behavior related to Lint JavaScript code. Inspect both source code and the browser execution path so fixes target the real bottleneck or bug.
- metadata.category
- javascript
- metadata.priority
- medium
- metadata.difficulty
- beginner
- metadata.estimatedTime
- 20
- metadata.source
- frontendchecklist.io
- metadata.url
- https://frontendchecklist.io/rules/javascript/javascript-linter
Lint JavaScript code
Linting catches bugs before runtime, enforces team coding standards, and prevents common mistakes that slip through code review.
Quick Reference
- Set up ESLint with
pnpm dlx eslint --init - Use shared configs (eslint:recommended, @typescript-eslint)
- Integrate with your editor for real-time feedback
- Add lint checks to CI/CD pipeline
Check
Set up JavaScript linting tools like ESLint to automatically detect syntax errors, enforce coding standards, and maintain consistent code quality across the team.
Fix
Configure ESLint with appropriate rules and plugins, integrate it into your development workflow, and fix all linting errors and warnings.
Explain
Explain how JavaScript linting prevents bugs, enforces consistent coding standards, improves code readability, and catches potential issues before runtime.
Code Review
Review scripts, client components, and browser execution paths related to Lint JavaScript code. Flag exact imports, event handlers, runtime side effects, or blocking operations that violate the rule, and state how the change should be verified in the browser.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/javascript/javascript-linter
© thedaviddias, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in skills/javascript-linter of thedaviddias/Front-End-Checklist.
- SKILL.md
- references/rule.md
Open the folder on GitHubat commit e8d14d0
Compare with similar skills
Javascript Linter next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Javascript Linter this skillthedaviddias/Front-End-Checklist | 74k | — | ~446 | Automated safety check: Pass | MIT | |
| Ultraciteagustinusnathaniel/nextarter-tailwind | 125 | 2 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Code Qualityredis/RedisInsight | 8.9k | — | ~1.2k | Automated safety check: Pass | Custom licence | |
| Port Ruleweb-infra-dev/rslint | 460 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Migrate OxlintAsvarox/allkaraoke | 261 | 4 repos | ~2.5k | Automated safety check: Pass | None | |
| Cb Code QualityBlkLeg/CircuitBreaker | 201 | — | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
- Official
Code Quality
redis/RedisInsight
Code-quality standards for RedisInsight: TypeScript strictness, naming conventions (camelCase, PascalCase, UPPERSNAKECASE), linting rules, no any without reason, no !important in styles, and…
Port Rule
web-infra-dev/rslint
Port a new ESLint core or plugin rule to rslint, including explicitly requested batches.
Migrate Oxlint
Asvarox/allkaraoke
Guide for migrating a project from ESLint to Oxlint. An agent skill from Asvarox/allkaraoke.
Cb Code Quality
BlkLeg/CircuitBreaker
Circuit Breaker code conventions and the quality gates that actually block a push — ruff, mypy, eslint, the pytest coverage ratchet, and the make verify tiers.
Es X Changeset
eslint-community/eslint-plugin-es-x
Add or update Changesets entries for eslint-plugin-es-x. An agent skill from eslint-community/eslint-plugin-es-x.
More from thedaviddias/Front-End-Checklist
All 390 skills in this repoContent Dates Audit
thedaviddias/Front-End-Checklist
Audits article and blog pages for visible publish dates, Article JSON-LD with datePublished and dateModified, and Open Graph time tags, then fixes what is missing.
FAQPage Schema Markup
thedaviddias/Front-End-Checklist
Adds, checks and fixes FAQPage JSON-LD on pages with visible question-and-answer sections so it matches what readers see and can qualify for rich results.
Favicon Audit and Setup
thedaviddias/Front-End-Checklist
Checks that a site's favicon is linked, reachable and large enough for Google search results, and sets up ICO, SVG and Apple touch icon files when they are missing.
Content Freshness Signals
thedaviddias/Front-End-Checklist
Audits article pages for freshness signals, covering the Last-Modified header, Article JSON-LD dateModified and a visible last-updated date, and fixes mismatches.
Geo Meta Tags Audit
thedaviddias/Front-End-Checklist
Audits and fixes geo.region, geo.placename and geo.position meta tags on regional pages, noting where they help (Bing) and where they do not (Google).
Improve a Front-End Checklist Rule
thedaviddias/Front-End-Checklist
Scores and rewrites a Front-End Checklist rule MDX file against a scored quality rubric, replacing generic stub prompts with specific, actionable ones.
Related
Works with
Categories
Questions about Javascript Linter
What does Javascript Linter do?
A skill your agent uses when reviewing scripts, client components, bundles, or runtime behavior related to Lint JavaScript code. Javascript Linter is an agent skill from thedaviddias/Front-End-Checklist. Use when reviewing scripts, client components, bundles, or runtime behavior related to Lint JavaScript code.
When should I use Javascript Linter?
Javascript Linter fits situations like: reviewing scripts; client components; runtime behavior related to Lint JavaScript code.
How do I install Javascript Linter in Claude Code?
Run `npx skills add thedaviddias/Front-End-Checklist --skill javascript-linter -a claude-code`. Or copy the skill folder (skills/javascript-linter in thedaviddias/Front-End-Checklist) into .claude/skills/javascript-linter in your project. Claude Code loads it when a task matches its description.
How do I install Javascript Linter in Codex?
Run `npx skills add thedaviddias/Front-End-Checklist --skill javascript-linter -a codex`. Or copy the skill folder (skills/javascript-linter in thedaviddias/Front-End-Checklist) into .agents/skills/javascript-linter in your project. Codex loads it when a task matches its description.
Can I use Javascript Linter in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add thedaviddias/Front-End-Checklist --skill javascript-linter -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/javascript-linter, .gemini/skills/javascript-linter, .github/skills/javascript-linter and .opencode/skills/javascript-linter in your project.
What does Javascript Linter need to run?
Going by SKILL.md and its folder, Javascript Linter needs the command-line tools its instructions call (pnpm).
Does Javascript Linter access the network?
SKILL.md names 1 domain. As links in the text: frontendchecklist.io. This is read from the text; nothing was executed.
Is Javascript Linter safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Javascript Linter use?
Javascript Linter is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Javascript Linter use?
About 446 tokens (SKILL.md is roughly 1.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 7.6k tokens, read only when the agent opens those files.
What are the alternatives to Javascript Linter?
Skills that share tags, products or a category with Javascript Linter: Ultracite (agustinusnathaniel/nextarter-tailwind, 125 stars), Code Quality (redis/RedisInsight, 8.9k stars), Port Rule (web-infra-dev/rslint, 460 stars) and Migrate Oxlint (Asvarox/allkaraoke, 261 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Javascript Linter?
thedaviddias (a GitHub user) maintains it in thedaviddias/Front-End-Checklist, which has 74,388 GitHub stars. The repository holds 390 skills in this directory. The repository was last updated on October 6, 2026.
Source: thedaviddias/Front-End-Checklist on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.