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

How to triage new issues on a schedule with Clodfarm

Set a recurring job so the farm sorts new issues every weekday morning.

Who it is forA maintainer of a busy repo who wants new issues sorted before the day starts, without doing it by hand.

The problemTriage is repetitive and easy to skip on busy days, so issues pile up.

The outcomeA scheduled Claude runs the triage at the times you set, and the job runs without you starting it.

What you need first

  • Docker on a machine or server that stays on
  • A Claude subscription to sign in with
  • A Git repo you control, with a deploy key if you want the farm to clone and push to it
  • Your test command, for example pytest -q

Steps

  1. Install and start the farm, and connect it to your repo with FARM_REPO_URL.
  2. Open the Claude app, go to Code, and select [Clodfarm] Clodfarm.
  3. Ask for the schedule in plain words, for example "every weekday at 9, triage new issues".
  4. Check the farm UI after the first scheduled run to confirm it finished.
  5. Adjust or cancel the schedule by asking your Claude in the same chat.

Prompt for your agent

Using the clodfarm repo at github.com/matank001/clodfarm, set up a recurring task that triages new issues on <repo-url> every weekday at 9. Confirm the schedule exists, then report the result of the first run in the farm UI at http://localhost:8080.

Caveat. The README gives the schedule as an example phrase in the Claude app, so confirm the exact setup in the docs before relying on it.

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