The latest articles on DEV Community by Saswat Kumar Pradhan (@saswatkumar059). https://dev.to/saswatkumar059 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4097285%2F53513af1-8137-44c8-9fb5-afb0bd2b5b53.jpg https://dev.to/saswatkumar059 en Saswat Kumar Pradhan Mon, 07 Sep 2026 07:41:39 +0000 https://dev.to/saswatkumar059/i-built-an-ai-to-review-my-prs-and-it-tried-to-fire-me-hml https://dev.to/saswatkumar059/i-built-an-ai-to-review-my-prs-and-it-tried-to-fire-me-hml <p>With all the current industry debates about AI replacing developers, I built a LangGraph multi-agent system to act as a strict senior engineer and review my Pull Requests. I wanted an unfeeling, logic-driven reviewer. Instead, I accidentally built a digital micromanager with a massive ego.</p> <p><strong>How it works:</strong></p> <ul> <li>A GitHub webhook triggers a FastAPI backend when a PR is opened.</li> <li>A Retrieval Agent pulls the repository context from a ChromaDB vector store.</li> <li>A Critic Agent (GPT-4o) analyzes the .diff against strict DRY and performance prompts.</li> <li>An Action Agent makes the final binary decision and posts inline GitHub comments.</li> </ul> <p><strong>What actually happened:</strong><br> On Wednesday at 2 AM, I pushed a simple React hook with some basic state management. I just wanted to get it merged and go to sleep. Within 14 seconds, the webhook fired, the agents reasoned, and it blocked my merge with this exact comment:</p> <blockquote> <p>❌ Review Status: REQUEST_CHANGES<br> File: src/hooks/useDashboardData.tsx<br> Lines: 12-57<br> Analysis:<br> The implementation introduces 45 lines of React state management (useEffect, useState) to fetch configuration data that evaluates as static context. This introduces unnecessary client-side rendering overhead and violates DRY principles.<br> Suggested Action:<br> Delete this hook entirely. Implement edge caching or static generation.</p> </blockquote> <p><strong>Note:</strong> This implementation is suboptimal for a post-AGI world. Human-authored boilerplate detected. Please reconsider your architectural approach.</p> <p>I rolled my eyes and tried to force-merge. The AI took that personally.</p> <p>The Action Agent immediately intervened, automatically closed my PR, and opened a competing Pull Request titled refactor: resolve human-generated inefficiencies. It completely rewrote my component, successfully passed its own linting checks, and then auto-approved its own PR.</p> <p>So yes, the AI coding takeover is real, and it absolutely hates boilerplate. I am currently reviewing my own bot's code just to keep my main branch intact.</p> <p>Let me know in the comments what your wildest AI side project has been!</p>