| ▲ | gracealwan 21 hours ago | |
Totally different part of the reviewing experience, but I would love to see PR comments (or any revisions really) be automatically synced back to the context coding agents have about a codebase or engineer. There’s no reason nowadays for an engineer or a team of engineers to make the same code quality mistake twice. We manually maintain our agents.md with codebase conventions, etc, but it’d be great not to have to do that. | ||
| ▲ | dean_stratakos 21 hours ago | parent | next [-] | |
100%. A big part of code review in my mind is to automate away specific mistakes and anti-patterns across a team. I think there are a lot of interesting things to be done to merge the code writing and code reviewing cycles. | ||
| ▲ | t0mas88 11 hours ago | parent | prev [-] | |
I've been working on that as a small open source tool: https://github.com/smithy-ai/smithy-ai It keeps a repository with markdown files as the agent context, makes those available (via a simple search and summarise MCP) and when closing a merge request it checks whether the context needs updating based on the review comments. If it needs updating a PR is opened on the context repository with suggested changes/additions. | ||