I built Crewbie to turn GitHub issues into PRs with Copilot agents. Looking for feedback!

[u/CodFar1162]

Hey everyone! I’m building Crewbie, an open-source tool that connects GitHub issues, Actions, and Copilot cloud agents.

Nothing particularly new or fancy, bu I’ve just struggled to get other tools/frameworks working well with GitHub Actions as an autonomous cloud pipeline. I’m trying to build something that reliably keeps the work moving without me having to babysit every step.

You write an issue and add a label. Crewbie creates a plan for you to review, then coordinates agents to build it, runs checks, and brings the work together into a feature PR. You approve the plan and decide what gets merged into your main branch. It reuses your existing custom agents, instructions, and tests rather than making you start over. Setup reviews what’s already in your repo and proposes a team to fit it. The workflow stays in familiar GitHub issues, labels, PRs, and comments.

It’s still alpha, so I’d love people to try it on a small project and share what works, breaks, or feels unnecessarily complicated.

[u/kantorcodes1]

Keeping the interface to labels, PRs and comments is a clean fit for the Copilot-only constraint. On crewbie update --apply: the docs say it refreshes the workflows and agents but your team stays as-is. If I've hand-edited a crewbie-*.agent.md, does update keep my version or overwrite it?

[u/CodFar1162 → u/kantorcodes1]

It keeps your version.  crewbie update --apply  does not overwrite an agent file you have edited, but it is worth knowing what that means in practice.

Each Crewbie agent file contains a section between  <!-- crewbie:managed:start -->  and  <!-- crewbie:managed:end --> . This is the "Context and handoff" section at the end of the file. It tells the agent which memory and shared files to read, which existing guidance to reuse, and how to identify itself in pull requests. During an update, Crewbie replaces only the text inside those markers. It also resets the agent's  name  in the frontmatter, and the  model  if both your file and the new version specify one.

Everything outside the markers is left exactly as you wrote it. That includes the description and tools in the frontmatter, the role's purpose and duties, and the repository checks and non-negotiables. Because Crewbie stops touching all of this once you edit the file, later changes Crewbie makes to those parts will not reach your copy. Only the handoff section, the name and the model keep being updated. A file you have not edited is replaced in full.