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

How to turn small labeled issues into reviewed draft pull requests with Factory

Let scheduled agents implement charter-allowed issues on claimed branches and open draft PRs for review.

Who it is forA maintainer with a backlog of small, well-described bugs who wants them worked overnight while a person keeps the merge decision.

The problemSmall fixes sit in the backlog because steering an agent session by hand for each one costs more time than the fix itself.

The outcomeEach permitted issue gets a failing test, a scoped change, passing gates, an independent verifier verdict, and a draft PR that a human reviews in the control room before merging.

What you need first

  • A GitHub project you control, with permission to create labels and manage its pull requests
  • Claude Code installed, or Codex if you use the Codex adapter
  • A clone of the addyosmani/factory repository
  • Your project's real test, lint, and build commands, since the gates run them
  • A human-owned docs/factory/CHARTER.md that defines scope, risk, and the review-queue limit

Steps

  1. Write the scope, risk tier, protected paths, and review-queue limit in docs/factory/CHARTER.md.
  2. Label a small, clear issue factory:ready-to-implement.
  3. Let the scheduled implementation routine claim the issue on its deterministic branch and open a draft PR.
  4. Wait for the PR verification routine to leave its verdict on the pull request.
  5. Open /factory, read the evidence in the review queue, then request changes, close, or merge the PR yourself.

Prompt for your agent

In the addyosmani/factory setup of <target-repo>, pick one issue labeled factory:ready-to-implement and run the implementation stage on it. Expected output: a draft pull request with its gate results and verifier verdict. Verify that no merge was performed and that the PR is still open as a draft.

Caveat. The README says Claude routines do not trigger on newly created issues, so the default hourly triage poll means an issue may wait until the next run, and the optional GitHub Action is needed for immediate triage.

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