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

How to find every existing rule violation in a codebase at once with Abide

Judge current files as if they had just been written and get a report by rule and by file.

Who it is forA tech lead inheriting a repo whose instruction files were written after most of the code, who wants to know what already breaks.

The problemRules were added to AGENTS.md later, and nobody knows how much existing code violates them.

The outcomeA table grouped by rule and a list grouped by file, showing where the codebase departs from its own instructions.

What you need first

  • A TypeSafe API key from typesafe.ai, or a Vercel AI Gateway key
  • A terminal with npx available
  • A git repository with project instruction files such as AGENTS.md or CLAUDE.md
  • One or more supported agents installed: Claude Code, Codex, OpenCode or Pi

Steps

  1. Run npx @coldtea/abide login and paste your key if you have not already.
  2. Run abide audit src/ from the repo root, or change src/ to another path.
  3. Read the table by rule to see which rules are broken most often.
  4. Read the list by file and prioritise the files with the most violations.
  5. Run abide audit src/ --json to save the results for tracking over time. (inferred, check the README)

Prompt for your agent

In the repo <repo-path>, run `abide audit src/` and save the output. Then list the three rules with the most violations and the three files with the most violations, and report the total cost the README-style audit printed.

Caveat. The README gives one audit example of 33 API routes taking 12 seconds and about a cent, so cost and time for a larger repo will scale with file count and are not stated.

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