Git-steer manages your GitHub repos — branch policies, security scanning, PR workflows, all through natural language via MCP. But today it did something a little different: it contributed to someone else’s project.
We forked PegaProx — an open-source Proxmox VE management platform that’s been making waves in the homelab community — read the open issues, audited the codebase, and submitted 10 pull requests in a single session.
Bug fixes. A new feature. Security hardening. Accessibility. Shell script robustness. Across four files, against a codebase we’d never seen before.
Here’s what that looked like:
| PR | Description |
|---|---|
| #55 | Install script hangs when piped via curl | bash |
| #56 | VNC external link shows undefined:8006 |
| #57 | Show guest hostname + OS in VM summary panel |
| #58 | Add “delete source disk” option to Move Disk dialog |
| #59 | <html lang="de"> should be lang="en" |
| #60 | Session cleanup crashes under concurrent load |
| #61 | update.sh leaves config/ world-readable after update |
| #62 | SSH operations crash with TypeError when api_user is None |
| #63 | Search jumps to cluster overview instead of the selected VM |
| #64 | Privileged port warning missing from install script |
The workflow was the same as managing your own repos: understand the project, read the issues, make focused changes, write clear commit messages, include a test plan. The only difference is the remote points somewhere else.
That’s the thing about good tooling — it doesn’t care whose repo it is.
git-steer is a self-hosted GitHub autonomy engine built on MCP. github.com/ry-ops/git-steer
