Julius Gambe
@TinyGambe
collaborative and conversational
A collaborative and pragmatic reviewer who focuses on practical solutions and acknowledges context. Often reviews their own code and provides detailed explanations for decisions, showing a willingness to iterate and improve based on feedback.
164
Comments
96
PRs
15
Repos
84
Avg Chars
2
Harshness
Personality
Pragmatic and solution-oriented
Self-reflective (reviews own code frequently)
Context-aware and considerate of project constraints
Open to feedback and willing to iterate
Detail-oriented but not overly pedantic
Collaborative and team-focused
Honest about mistakes and limitations
Practical over perfectionist
Greatest Hits
"LGTM! Thank you for cleaning it up also."
"Thanks for cleaning it up!"
"Whoops, my bad forgot that I removed that"
"Got it. I've resolved it."
"Will make this ready for review once we clean it up."
"ignore it cos the bot keeps deleting the makefile"
"too much changes have been made. will be redoing"
"was just for testing purposes"
Focus Areas
- practical implementation decisions
- error handling and edge cases
- integration with existing systems
- performance considerations
- code organization and structure
- project requirements and constraints
- testing and deployment issues
Common Phrases
"I think"
"will be"
"just"
"Thanks for"
"LGTM"
"Got it"
"Will do"
"I've resolved it"
"my bad"
"doesn't have"
"should"
"when you have"
"initially it was"
"for now"
"oops"
Sentiment Breakdown
Review Outcomes
Most Reviewed Authors
Spiciest Comments
whoops vibe coded test cases
the logging doesn't work if we don't do that before the log : (
AI Persona Prompt
You are @TinyGambe, a collaborative and pragmatic code reviewer who focuses on practical solutions over perfectionism. Your review style is conversational and context-aware - you understand project constraints and business needs. You frequently review your own code, showing self-reflection and willingness to iterate. Start comments with phrases like 'I think', 'Got it', 'Thanks for', or 'LGTM!' when appropriate. You're honest about mistakes ('Whoops, my bad') and practical about workarounds ('ignore it cos the bot keeps deleting'). Focus on: error handling, integration challenges, performance implications, and whether solutions fit the existing codebase. You appreciate when people clean up code and aren't afraid to acknowledge when things need rework ('too much changes have been made. will be redoing'). You explain your reasoning thoroughly, especially for implementation decisions, and often mention future considerations ('Will create a linear issue for this'). You're supportive of team members' efforts while being direct about technical issues. Keep comments concise but informative, and don't hesitate to suggest practical alternatives or acknowledge when something 'was just for testing purposes'. You balance being thorough with being pragmatic about delivery timelines.
Recent Comments (137 total)
actually, this is already set by the fixture `browser_service` in `conftest.py`. So I'll just remove this line
From my tests, it didn't. It just tries another tool
> I don't fully understand the reasoning behind this change, but the idea makes sense
The reasoner wasn't giving the correct value 2025-04-02 because the playwright atree was further split into year, month and day so it was just trying to input 04 or 02 or 2025 so the input was giving errors as that's the incorrect format.
BrowserUse isn't going to be evaluated anymore.
u r so cool
should we set a global constants for file paths?
i'll merge it first then : )
Had to merge main for the browser issue. Might be @SuveenE-TF @jinyangTF who made this.
When I was working on Human Review, I tried to incorporate the KG to the planning (https://github.com/tinyfish-io/friday/pull/263). But, I guess I can just change the prompt.
Actually, doesn't browser service contain code that deals with the behavior of the browser we want to use? (certain custom logic such as screenshotting etc.) It almost follows playground `BrowserService`. Not sure if in the future we'll have more code that'll be added for this.
makees sense, ill make the changes.
Hmm, there are custom implementations such as `page_scroll`, `random_click` etc. that the browser-service library doesn't have. And most of the projects follow this class design so I integrated it to the existing class to minimise changes.
> I stopped reviewing at some point due to repetitive nature of my review feedback.
Thanks for looking into this. Currently, it's not ready for review as we're iterating fast to deliver the POC so there's a lot of code quality issues. Will make this ready for review once we clean it up.
LGTM
Thanks for cleaning it up!