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

How to let a coding agent install the skill and run Jev Lint with Jev Lint

Install the Jev Lint skill so an agent can run checks and write project rules.

Who it is forA developer using Claude Code, Codex, Cursor or Gemini CLI who wants the agent to lint its own changes and draft rules for the project.

The problemAgents often lack a repeatable way to check their output against the repository's claims and instructions.

The outcomeAn agent that installs the Jev Lint skill, runs the right command for a target, and reports findings it can verify.

What you need first

  • Node 24 or newer with npx
  • A TYPESAFE_API_KEY from https://typesafe.ai, set in the environment (the code being judged is sent to the API)
  • A repository with code to lint, such as a TypeScript src folder

Steps

  1. npx skills add mizchi/jev-lint --skill jev-lint
  2. export TYPESAFE_API_KEY=...
  3. npx jev-lint check src --dry-run
  4. npx jev-lint review --base main (inferred, check the README)

Prompt for your agent

In the repository <repo-path>, install the skill with `npx skills add mizchi/jev-lint --skill jev-lint`, then run `npx jev-lint check src --dry-run` and report the planned request count and price. Only after a human approves, run `npx jev-lint review --base main` and list findings with file, line and score.

Caveat. The README warns the repository also ships jev-lint-repo, a maintainer skill, so the install must use --skill Jev Lint to avoid the wrong one.

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