Where do I put the generated workflow file?

Save it as a .yml file inside the .github/workflows directory at the root of your repository — for example .github/workflows/lint.yml. GitHub Actions automatically picks up any workflow file in that folder once it's committed to your default branch or a branch with an open PR.

Why run lint as a separate workflow from tests?

Lint, format, and type-check finish in seconds and catch the most common review nits, so isolating them gives contributors near-instant red/green feedback without waiting for a slower test suite. Many teams run this fast workflow alongside a heavier test job.

What does the caching step do?

The actions/setup-node cache option stores your dependency download between runs keyed on the lockfile, so installs that would take a minute drop to a few seconds when the lockfile hasn't changed. It's the single biggest speed-up for a lint-only workflow.

Do I need all three checks?

No. ESLint catches code-quality issues, Prettier enforces formatting, and tsc --noEmit catches type errors — they overlap little, so most teams run all three. The builder lets you disable any you don't use so the workflow only runs what your project has scripts for.

Is the YAML generated in my browser?

Yes. The workflow is assembled locally from your selections and never sent anywhere, so you can generate CI config for private repositories safely.

GitHub Actions Lint-Only Workflow Builder

Email me this result

Get this tool's output sent to your inbox, plus one useful tool a week. No spam, unsubscribe any time.

The GitHub Actions Lint-Only Workflow Builder generates a ready-to-commit CI workflow that runs the three fast static checks every pull request should pass: ESLint, a Prettier format check, and a TypeScript type-check. Because these finish in seconds, a dedicated lint workflow gives contributors near-instant feedback without waiting on a full test suite.

How it works

You select your package manager (npm, pnpm, or yarn), the Node version to run on, and which of the three checks to include. The builder writes a workflow triggered on pull_request (and optionally push) that checks out the code, sets up Node with dependency caching keyed on your lockfile, installs with the right command, and runs each enabled check as its own step. Splitting the checks into separate steps means the Actions log shows exactly which one failed.

The generated workflow

The output is a complete YAML file you save as .github/workflows/lint.yml. It uses actions/checkout and actions/setup-node with the built-in cache option, runs npm ci (or the pnpm/yarn equivalent), then runs eslint ., prettier --check ., and tsc --noEmit depending on your toggles. Each step is named so failures are obvious in the PR’s checks panel.

Tips and notes

Match the scripts to your package.json. If you use npm run lint rather than calling ESLint directly, swap the command — the workflow is a starting point.
Cache is the big win. The setup-node cache turns a one-minute install into a few seconds on unchanged lockfiles.
Pair with tests. Run this fast workflow next to a slower test job so contributors get the quick red/green signal immediately.