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

How to catch tests that pass against old code in CI with Gap Trap

Run every new test against the old code in CI and fail any test that passes there.

Who it is forA developer whose agent writes tests that check that code ran rather than that it did the right thing.

The problemA test that cannot fail proves nothing, and agents often write tests like that.

The outcomeA CI job that flags each new test that also passes on the old code, so weak tests are caught before merge.

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. Run /gap-trap setup in the repository so the proven red CI job is added.
  2. Open a PR that adds a new test.
  3. Check the proven red CI job result for that PR.
  4. If the job fails, rewrite the test so it fails on the old code and passes on the new code.

Prompt for your agent

In the repo at <repo-path>, after gap-trap setup, open a PR that adds one new test. Report the result of the proven red CI job for that PR. Verify that the job ran in CI and not only locally.

Caveat. The README says proven red runs only in CI, so you will not see its result from a local run.

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