This is a submission for the [Hacktoberfest Weekend Challenge: Build for a Friend]. Lets see how Kiro IDE was used to streamline the entire thing. (https://dev.to/challenges/hacktoberfest-weekend-2026-10-01)
P.S: Written by one's own experience
What I Built
Honestly, let me give you a backstory. I love building stuff. I love practicing building in public. When I was there coding with my other friends who are also fellow developers, I saw that we had a hard time fixing all the issues that included only screenshots and nothing else. We didn't know what was root cause triggering that and how such could be prevented in long run. So I immediately thought of a plan: adding CodeRabbit and all. However it didn't solve the problem.
Neither for me neither for them. The developers had to know how to write a PR, then coderabbit reviews it. For most of cases, developers didn't care. They simply ran the software, found a bug and hitted on its issues. Its not that the bug is from their side, but it can come from the overall code too. They didn't know where exactly to pinpoint.
Naturally maintaining college and OSS is a hard stuff. My friends can't look at screenshots from every issue and debug whether its a local or a global issue. We needed an AI agent that could tell us where exactly it went wrong.
That why on Kiro Challenge and MLH x Kalyani Hackathon, I built PatchBridge. Its remarkably easy to use. Comment /patchbridge under an issue, Gemma 4 is multimodal anyways - understands the image, starts a session, streamlines its thoughts, calls GITHUB MCP tools for reading and grepping the repository thoroughly, comes with a solution and then raises a PR. After that other AI review agents like CodeRabbit and greptile can start working on it.
Demo
I didn't deploy it somewhere, honestly because I want people to learn how to self-deploy. I don't want them to just see repository and click "Yeah here's link, let me get it!". I want them to participate and understand no one is holding their hands by giving them a readymade solution.
Here's code however: https://github.com/Soumyabrataop/PatchBridge
Code
https://github.com/Soumyabrataop/PatchBridge
How I Built It
Don't get me wrong but I coded this using both my personal understanding and using Kiro.
I never thought I could complete this just alone. Hence, I decided to start this with Antigravity. However it isn't like "Code this for me. Here's the plan" but like "Look at this particular screenshot. It comes from this particular styling issue. Please create a patch that can fix the issue." - More engagement and understanding, not just driving on autopilot. Antigravity barely did anything.
I used a much better IDE named as Kiro, from Amazon after learning about it. It comes with specs, hooks and much more.
Why Does Open Innovation Matter?
A closed API is like a closed room. Dark and mysterious, we don't know what's going inside. Even reports published is a half story - we never know what's inside them. Open Innovation always stood out whether its Open Hermes, or Open Devin or a Open Copilot. Not just developers building products that are open-source versions of the existing solutions but something's that the existing solutions can take inspiration from! Hey don't think only the big inspires the small, the small does it too.
Adios,
Soumyabrata Mukherjee
Top comments (0)