Developer bot: from GitHub issue to tested pull request
Point one bot at a repository. It picks an issue, clones the code on its own computer, writes the fix and a test, runs the suite, and opens a pull request with a summary, asking you before anything is posted to GitHub.
GitHub
Bot computerBuilt in
Approvals. X posts always ask first, and so do trading orders unless you set a Binance or Polymarket bot to trade on its own within its limits. Other actions ask only when Approvals are on in Settings; on Never ask, the krypton.bot default, they run without asking.
Apps used
GitHub
Lists and reads the issues, opens the pull request, comments on the issue and checks the build status.
Bot computerBuilt in
The bot's own Linux computer, where it clones the repo, edits files, runs the tests and pushes the branch.
Included in Krypton, nothing to connect
How to set it up in Krypton
Connect GitHub
In Krypton, open Integrations, pick GitHub and sign in with the account that can see the repository. The bot reads issues and opens pull requests as that account.
Hire the bot
Open Bot Marketplace and hire the Developer, or ask Chief in chat to create a coding bot. Give it the GitHub app and a computer.
Let the computer push
For a private repository, the bot asks for a fine-grained GitHub token limited to that repo on a secure secret card. It is stored as a secret and never shown in chat.
Send the task
Paste the prompt below and change the repository, the label or the issue number. You can also name one issue, such as #128.
Approve what gets posted
Turn on Approvals in Settings (krypton.bot starts on Never ask) and opening the pull request and commenting on the issue each show an approval card. Tap Allow once, or deny it and ask for changes in chat first.
Review and merge yourself
Read the diff on GitHub, leave review comments for the bot to address, and merge when you are happy. Add a routine if you want it to pick up a new issue every morning.
Pick the oldest open bug in contoso/invoice-kit, fix it on your computer, run the tests and open a pull request with a short summary. Ask me before you post anything on GitHub, and don't merge.What the bot does
- Lists the open issues, picks one that matches your rule and reads it in full.
- Clones the repository on its own computer and creates a branch for the fix.
- Reads the code, writes the fix and a test that would have caught the bug.
- Runs the test suite and the linter, and fixes its own failures before going on.
- Pushes the branch and asks you before it opens the pull request with a summary.
- Asks again before it comments on the issue, checks the build status and leaves the merge to you.
Questions
Can the bot merge or push to main?
It works on its own branch and opens a pull request for you to review. With Approvals on, posting to GitHub waits for your approval card, and in this flow you tell it not to merge. Branch protection on GitHub keeps main safe as well.
Where does the code run?
On the bot's own computer in Krypton, not on your laptop. It clones the repo there, runs the tests there and pushes only the branch.
Is this a real repository?
No. It is an illustration with sample data: Contoso and invoice-kit are fictional, and the issue, diff and test counts are made up to show the flow.
Can it work with GitLab, Jira or Linear?
Yes, GitLab, Jira & Confluence and Linear are in the catalog too. Connect the one your team uses and give it to the bot the same way.
More use cases
All use cases
Browse every app in the MCP catalog or hire a ready-made bot from the Bot Marketplace.
Build this bot in Krypton
Start free, connect your apps and paste the prompt. X posts always wait for your OK, and so do trading orders unless you set the bot to trade on its own; turn on Approvals to review everything else first.