When we designed NeetoBugWatch, we wanted it to feel less like a noisy script and more like a helpful human teammate. A key part of that is respecting the natural rhythm of software development.
After you receive feedback on a pull request, you'll often push several small commits to address the suggestions. The last thing you need is an automated review on every single one of those commits. It’s distracting, inefficient, and not how you’d interact with a human reviewer.
That’s why NeetoBugWatch does not automatically re-run a review on every new commit.
So, how do you ask for a fresh review once your changes are ready?
The Solution: The neeto-bugwatch-run Command
We’ve made it simple. When you're ready for another look, just add a comment to your pull request containing the phrase: neeto-bugwatch-run
That's it. This command will instantly trigger a fresh, complete review of all the latest changes in your PR. No more closing and reopening pull requests just to get the bot's attention.
Our Design Philosophy: A Tap on the Shoulder
Think about how you interact with a senior developer. You wouldn't tap them on the shoulder after every single line of code you fix. You'd push all your changes, make sure they're ready, and then let your teammate know it's time for another look.
The neeto-bugwatch-run command is the digital version of that tap on the shoulder.
This approach has three clear benefits:
It Reduces Noise: You and your team won't be spammed with notifications for every intermediate commit.
It Puts You in Control: You decide the right moment for a re-review, just as you would in a human-centric workflow.
It Saves Costs: By avoiding unnecessary reviews, you prevent wasteful LLM API calls, keeping your operational costs incredibly low.
It’s a small feature that makes a big difference in the daily workflow, making NeetoBugWatch a more efficient and respectful teammate.