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

How to keep CI and dependency PRs green while you work with Overtime

A repo-keeper agent watches CI and dependency PRs, fixes what breaks, and asks before anything ships.

  • Top pick
  • Software and DevOps
  • Intermediate
  • 30 minutes
  • From the README
  • Claude Code
  • Codex
  • Gemini CLI

Who it is forA developer or maintainer whose repo gets failing CI runs and dependency update PRs between their own work sessions.

The problemBroken CI and stale dependency PRs pile up while nobody is watching, and fixing them interrupts other work.

The outcomeAn agent that keeps its own schedule, fixes breakages it can handle, and leaves a question with options and a recommendation before merging anything that ships.

What you need first

  • Node.js 22.19 or newer
  • npm to install the package globally
  • One coding agent signed in, such as Claude (built in, uses your Claude Code login)
  • A repo or service the agent can access, with protected paths set if needed

Steps

  1. Run npm install -g @ukanwat/overtime to install the app.
  2. Run overtime and type a name for the agent, for example repo-keeper.
  3. Check the backend, model, daily budget and folder, then press Enter.
  4. Brief it in plain words: watch CI and dependency PRs in your repo, fix what breaks, and ask before merging anything that ships.
  5. Set any paths you want protected as read-only so the agent cannot change them.

Prompt for your agent

Using the Overtime repo at ukanwat/overtime, set up an agent named repo-keeper briefed to watch CI and dependency PRs for <target repo>. Expected output: a short list of failing checks and open dependency PRs, with a fix or a question for each. Verify that no merge happens without an approval question being answered.

Caveat. Overtime is in early development and Claude is the backend tested most, so Codex and Gemini CLI paths need wider testing.

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