# AI use cases for Abide (coldteadotai/abide) Repo: [coldteadotai/abide](https://github.com/coldteadotai/abide) | Use cases: 4 | Page: https://dedupedai.com/use-cases/coldteadotai-abide/ Abide is a CLI that checks a coding agent's edits and turns against the project's own instruction rules and makes the agent repair any violation. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Stop a coding agent from breaking your written project rules: https://dedupedai.com/use-cases/coldteadotai-abide/enforce-project-rules-in-coding-agent/ - Find every existing rule violation in a codebase at once: https://dedupedai.com/use-cases/coldteadotai-abide/audit-existing-codebase-against-rules/ - Switch off or rewrite rules that never fire or fire wrongly: https://dedupedai.com/use-cases/coldteadotai-abide/tune-and-calibrate-noisy-rules/ - Give every teammate the same rule enforcement through the repo: https://dedupedai.com/use-cases/coldteadotai-abide/share-agent-rules-with-team-checkout/ ## How to stop a coding agent from breaking your written project rules with Abide Repo: [coldteadotai/abide](https://github.com/coldteadotai/abide) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Hook Abide into your agent so each edit is checked against your instruction files and violations are repaired in the same turn. **Who it is for:** A developer whose team keeps rules in AGENTS.md or CLAUDE.md that linters cannot check, and whose coding agent keeps ignoring them. **The problem:** Rules such as 'never let a raw error reach a user' are not enforced by any tool, so the agent breaks them on many turns. **The outcome:** The agent is told which rule an edit broke, with the rule text and file, and fixes it before moving on. ### Steps 1. Run `npx @coldtea/abide login`, choose the key type, and paste your key once. 2. Run `npx @coldtea/abide init` in your repo to install hooks into every agent found on the machine. 3. For Codex, start `codex`, type `/hooks`, and accept the four Abide entries. (inferred, check the README) 4. Start your agent as usual, for example `claude`, and let its first turn compile your rules into `.abide/rubric.json`. 5. Ask the agent for a change that one of your rules forbids and confirm it receives an Abide repair request. ### Prompt to paste into your agent ```text In the repo , install Abide with `npx @coldtea/abide init` and confirm that `.abide/rubric.json` was created after the first agent turn. Then ask the agent for an edit that breaks one rule in AGENTS.md and report the rule id and file that Abide names. ``` ### Caveat Each edit or turn is sent as changed lines to TypeSafe under your key, and the README says a key is required before any check runs. Risk, credentials: The setup stores your TypeSafe or Vercel AI Gateway key in ~/.abide/.env or .env.local, so keep those files out of version control and protect the machine. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/coldteadotai-abide/enforce-project-rules-in-coding-agent/ ## How to find every existing rule violation in a codebase at once with Abide Repo: [coldteadotai/abide](https://github.com/coldteadotai/abide) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Judge current files as if they had just been written and get a report by rule and by file. **Who it is for:** A tech lead inheriting a repo whose instruction files were written after most of the code, who wants to know what already breaks. **The problem:** Rules were added to AGENTS.md later, and nobody knows how much existing code violates them. **The outcome:** A table grouped by rule and a list grouped by file, showing where the codebase departs from its own instructions. ### 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 to paste into your agent ```text In the repo , 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. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/coldteadotai-abide/audit-existing-codebase-against-rules/ ## How to switch off or rewrite rules that never fire or fire wrongly with Abide Repo: [coldteadotai/abide](https://github.com/coldteadotai/abide) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Score each rule against your git history, disable the broken ones, and have the agent rewrite the rest. **Who it is for:** A developer who wrote a rubric from their instruction files and finds some rules either silent or noisy. **The problem:** A badly worded rule scores 0.4 on everything and never fires, so it adds no protection and nobody notices. **The outcome:** Rules that never fire are switched off, and remaining rules are reworded so their verdicts are useful. ### Steps 1. Run `abide report` to see your rules, which ones fired, and which never fire. 2. Run `abide calibrate` to score every rule against twenty real hunks from your git history. 3. Run `abide tune` to have the agent rewrite the rules that never fire. 4. Run `abide compile` to recompile the rubric now instead of waiting for the next session. 5. Run `abide report` again and confirm the rules changed as expected. ### Prompt to paste into your agent ```text In the repo , run `abide report`, then `abide calibrate`, then `abide tune`. Report which rules were switched off or rewritten, and confirm `.abide/rubric.json` still parses. ``` ### Caveat The README says compile and tune use Claude Code by default or Pi when Claude is unavailable, so one of those must be installed and logged in. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/coldteadotai-abide/tune-and-calibrate-noisy-rules/ ## How to give every teammate the same rule enforcement through the repo with Abide Repo: [coldteadotai/abide](https://github.com/coldteadotai/abide) | Difficulty: Advanced | Time: 45 minutes | Basis: From the README Install Abide into the project so the hooks travel with the checkout instead of each person's machine. **Who it is for:** A team lead whose members use different coding agents and need the same rules enforced for everyone. **The problem:** Each developer would otherwise install hooks by hand on their own machine, so enforcement varies between people. **The outcome:** Teammates get the same project-level hooks and rubric through the repository, and the rubric is reviewed like any other file. ### Steps 1. Run `npx @coldtea/abide init --project` in the repo to install into the repo instead of the user's home. (inferred, check the README) 2. Commit `.abide/rubric.json` and the new project hook files to git. 3. Ask each teammate to run `npx @coldtea/abide login` once with their own key. 4. Each teammate starts their agent in the repo and checks that the first turn reports the rubric as valid. 5. Edit a rule in the rubric through a pull request and review it like any other change. ### Prompt to paste into your agent ```text In the repo , install Abide into the project with `init --project` for the agent in use, then list the files that were created or changed and confirm which ones should be committed. Report any file that is outside .abide/ or the agent's project extension path. ``` ### Caveat The README says Pi must trust the project before it loads a project extension, and Codex asks once for each new hook, so teammates may need a manual step. Risk, credentials: Each teammate must use their own key, so do not commit a key to the repo or share one through a checked-in .env file. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/coldteadotai-abide/share-agent-rules-with-team-checkout/