Tickets to pull requests
From a GitHub issue or Jira ticket to a pull request.
Assign the ticket to CoderHelm or add a label. It reads the repository, plans the change, writes it, runs your build and tests, reviews its own work and opens a pull request your team can review like any other.
Send start date at checkout
- TriageFeature · touches checkout
- Plan4 tasks · 3 files
- ImplementBuild, lint and tests passed in the sandbox
- Review1 fix round
- SecurityNo findings
- Pull request#318 ready for review
Start a run from the tools you already use
| Where | How to start a run |
|---|---|
| GitHub issue | Assign it to CoderHelm, add the coderhelm label, or comment /coderhelm or @coderhelm. |
| Jira ticket | Assign it to CoderHelm or add the coderhelm label. Your admin can change the label. |
| CoderHelm dashboard | Describe the work in a plan and approve it; each task becomes an issue and a run. |
| Monitoring alert | Route a CloudWatch alarm to CoderHelm and a matching rule starts a run. See alerts. |
What happens during a run
- 01
Triage and plan
It reads the ticket, the repository's conventions and your AGENTS.md, then writes a plan with the files it will touch.
- 02
Implement and test
It writes the change on a
coderhelm/branch and runs your real build, lint and tests in a sandbox that holds no credentials. - 03
Review and open
It reviews its own work (up to three fix rounds), runs a security check, resolves conflicts with the base branch and opens the pull request.
Pull requests open as drafts while the work is in progress, and are marked ready for review when CoderHelm is done.
Plans: describe the work, get ordered tickets
In the dashboard, describe what you want to build. CoderHelm streams a plan as it reasons, searching your code and the MCP servers you connected for the details. Approve it and each task becomes a GitHub issue and a run, in order.
FAQ
Can CoderHelm read screenshots attached to a ticket?
Yes, images attached to the ticket are read along with its text.
Will the pull request follow our conventions?
It reads AGENTS.md, CLAUDE.md, copilot instructions and .cursorrules from the repository, plus the guardrails, custom instructions and team voice your admins set.
What if CI fails on the pull request?
It reads the failing check's logs, fixes the cause and pushes again. It stops when the same failure happens twice, so it never loops on a problem it cannot fix. See maintenance.
Related
- Maintenance
CoderHelm stays on the code after the pull request: it answers review comments, fixes failing CI on its pull requests, resolves merge conflicts, checks deploys after merge and writes release notes.
- Code review
Add a label to any GitHub pull request and CoderHelm reviews it with the context of the whole repository, comments on exact lines with suggested fixes, rates risk and reviews again on every push.
- Skills
CoderHelm works your way: it reads your AGENTS.md, the skills and agent briefs your team keeps in a repository, the MCP servers you connect and what it learned on past runs.
Put CoderHelm on your next ticket.
CoderHelm is in open beta. Sign up and bring your own Anthropic API key.