CtrlK
BlogDocsLog inGet started
Tessl Logo

simon/skills

Auto-generated tile from GitHub (10 skills)

92

1.16x
Quality

94%

Does it follow best practices?

Impact

92%

1.16x

Average score across 44 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

ci-and-editor-integration.mdskills/linting-neostandard-eslint9/rules/

name:
ci-and-editor-integration
description:
Integrate neostandard and ESLint v9 with CI pipelines, pre-commit hooks, and editors
metadata:
{"tags":"ci, linting, neostandard, eslint, pre-commit, vscode"}

CI guidance

  • Run lint in CI as a required step:
npm run lint
  • Do not use auto-fix in CI.
  • Keep CI Node.js version aligned with local development and project engines.

Pre-commit hook pattern

Use lint-staged (or equivalent) to lint only changed files before commit.

{
  "lint-staged": {
    "*.{js,mjs,cjs,ts,mts,cts}": [
      "eslint --fix"
    ]
  }
}

When using neostandard, keep pre-commit execution on eslint --fix because ESLint is the actual runner.

VS Code integration

  • Install ESLint extension
  • Enable flat config support if required by extension version
  • Use editor.codeActionsOnSave for explicit, predictable auto-fixes

Example workspace settings:

{
  "editor.codeActionsOnSave": {
    "source.fixAll.eslint": "explicit"
  },
  "eslint.validate": ["javascript", "typescript"]
}

skills

linting-neostandard-eslint9

rules

ci-and-editor-integration.md

eslint-v9-flat-config.md

migration-from-legacy-eslint.md

migration-from-standard.md

neostandard.md

SKILL.md

README.md

tile.json