ChatToPR

During a production incident, engineers agree on the root cause and fix in Slack, but turning that conversation into a branch and a pull request still means leaving the chat, switching tools and writing everything up while production is down. ChatToPR removes that hand-off. With one click, it ingests an incident thread (every author, timestamp and message), extracts ticket and PR references (#4821, #312), code references and participants, and highlights the root-cause, fix and rollback messages. It then builds a structured incident record, triage/INC-<id>.md, commits it to a new branch, and opens a real GitHub pull request through the GitHub API. Nothing is ever merged automatically: a human always reviews. We built ChatToPR with IBM Bob IDE as our development partner, from an empty folder to a deployed app across 8 task sessions: the project scaffold and Slack-style UI, the Next.js API route, the Octokit branch-commit-PR pipeline, frontend-to-API integration, the landing page and documentation. Bob even diagnosed a "Bad credentials" error from a pasted screenshot. All task sessions are exported in the repo's bob_sessions folder. Next: AI-generated patches and regression tests with IBM watsonx.ai Granite, a real Slack app, and an IBM Bob custom mode that implements the fix from the triage PR.