Our goal is to run a nightly process where production errors from the last 24 hours are analyzed by Claude, and proposed fixes are created in our GitHub repository as Draft Pull Requests.
The expected flow is: Collect and group production errors daily Generate a structured bug report for each unique issue Claude analyzes the repository, identifies root cause, and implements a minimal fix Add or update relevant tests Open a Draft PR including root cause analysis, fix explanation, and test results The PR must remain in Draft state with no automatic merge.
Developers will review the proposed changes each morning. We also require strict permission controls, no exposure of sensitive secrets, and proper CI validation before review.
Please guide us on the recommended architecture, security best practices, and any workflow configuration to help us implement this.
We can share our tech stack and sample sanitized error logs if needed. currently we have made implmenation , that cloud watch we have the erros is wachted by cloud watch , then the erros comes to RDS and then all the erros is send to the developer so whether the code is written by that developer or not , so we need implmnet that also that error that is come that error should go to tht email only those who have weiten the code or some primary key so that we can get to know that its written by them
Question
Automating bug reports and fixes with Claude and GitHub
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.