DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to make coding agents fix Lint errors before finishing with Lint

Give the agent a Lint command and an instruction to run it and fix errors after every change.

Who it is forA developer who hands UI tasks to a coding agent and wants the agent to check its own work before reporting done.

The problemAgents report tasks complete without checking their Tailwind usage against the design system, so errors reach review.

The outcomeThe project has a Lint script, and the agent guidance file tells the agent to run it and fix all errors after each change.

What you need first

  • Node.js 20.19 or later
  • A Tailwind v4 project (shadcn/ui is not required)
  • ESLint 9.30 or later, or Oxlint 1.80 or later
  • A React, Vue, or Svelte project

Steps

  1. Run npm install -D @shadcn/lint eslint @typescript-eslint/parser in the project, or npm install -D @shadcn/lint oxlint if you use Oxlint.
  2. Add eslint . or oxlint as the Lint script in package.json.
  3. Add this line to AGENTS.md: After making changes, run npm run lint and fix all errors.
  4. Run npm run lint once to confirm the script works before giving the agent a task.

Prompt for your agent

Use the GitHub repo shadcn-ui/lint to set up the lint loop in <project-path>. Install the package, add the lint script, and add the README instruction to AGENTS.md. Expected output: npm run lint exits cleanly on the current code. Verify that a deliberate arbitrary value in one file makes the command report an error.

Caveat. The README reports eval results across many agent runs, but those results come from the authors' own tests and are not a guarantee for every project.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page