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

How to turn a labeled GitHub issue into a reviewed draft PR with Eve Software Factory Template

Label an issue factory and get a reviewed draft pull request to review and merge.

Credentials. The GitHub App you install gives the factory access to push branches and open pull requests on the repository you select, so limit the install to the repositories you intend.

Who it is forA maintainer or developer with a backlog of small, well-described GitHub issues who wants a first draft of each change without writing it by hand.

The problemRoutine issues sit in the queue because writing the plan, the code, and the first pass of checks takes time that the team does not have.

The outcomeEach labeled issue produces a draft PR on the target repository, linked to the issue, with progress comments along the way. A person reviews it, marks it ready, and merges.

What you need first

  • A Vercel account to deploy the template with the deploy button
  • A GitHub repository you want the factory to work on, in owner/repo format
  • A GitHub App installed on that repository with access granted, as the connector requires
  • A Linear workspace, only if you want to delegate tasks from Linear
  • The Vercel CLI, for the local TUI workflow

Steps

  1. Click the Deploy button in the README and set FACTORY_REPO to your owner/repo.
  2. Install the GitHub App behind the GitHub connector on that repository so it has access.
  3. Open an issue on the repository with a clear description of the change.
  4. Add the factory label to the issue (default label: factory).
  5. Review the draft PR linked to the issue, then mark it ready and merge it.

Prompt for your agent

Work on the GitHub repository <owner/repo> using the factory label on issue <issue-number>. Confirm the factory opens a draft pull request linked to the issue, and check that the draft PR's CI runs and reports a result before anyone marks it ready.

Caveat. A station's sandbox clones FACTORY_REPO on its first session, so an unreachable repository shows up as a Cannot access error on the first task, not at deploy time.

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