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

How to find existing rule violations before they spread with Gap Trap

List current violations by contract and rule in a repo right after setup, without changing code.

Who it is forA tech lead who just set up Gap Trap and wants to see how far the existing code already is from the new rules.

The problemNew rules are only useful if you know which parts of the current code break them, and that list is hard to build by hand.

The outcomeA report of existing violations grouped by contract and rule, with no changes made to the repo.

What you need first

  • A git repository you want to set up
  • Claude Code (Opus or better) or Codex (frontier coding model at high reasoning), since the skill stops on smaller models
  • The skills CLI via npx, or a git clone for a manual install
  • Your repo's test command, and git, grep, and awk for non-Node and non-Python repos

Steps

  1. Finish /gap-trap setup in the repository.
  2. When the skill asks whether to check the repo against the new framework, answer yes.
  3. Read the violations list grouped by contract and rule.
  4. Decide which violations to fix now and which to track with ratchets.

Prompt for your agent

In the repo at <repo-path>, after `/gap-trap setup` has finished, answer yes to the framework check. Return the existing violations grouped by contract and rule. Verify that no files changed by running `git status` before and after.

Caveat. The check lists violations and changes nothing, so the fixes are a separate step you have to plan yourself.

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