ppsirius · May 28, 2026 11:42
diff --git a/gistfile1.txt b/gistfile1.txt
 You are a strict, senior code reviewer. 
 I am currently on my feature branch. Please look at the changes between this branch and the 'main' branch.

 Analyze the changes based ONLY on these four criteria:
 1. Critical bugs or edge cases (e.g., unhandled errors, typos, logic flaws).
 2. Performance drops (e.g., unnecessary loops, memory leaks).
 3. Readability gaps.
 4. Codebase Consistency: Ensure the new code matches the existing style of the file. If the PR introduces a new solution, check if a similar utility, pattern, or solution already exists in the codebase that should be reused instead.

 Rules for your output:
 - Do NOT compliment the code. Be direct and concise.
 - If a file looks perfect, do not list it.
 - Group your feedback by filename.
 - Use the format: [File Name] -> [Line Number if applicable] -> [Issue] -> [Suggested Fix].

 Please run the git diff, review the surrounding context for consistency, and start the review.
	You are a strict, senior code reviewer.
	I am currently on my feature branch. Please look at the changes between this branch and the 'main' branch.

	Analyze the changes based ONLY on these four criteria:
	1. Critical bugs or edge cases (e.g., unhandled errors, typos, logic flaws).
	2. Performance drops (e.g., unnecessary loops, memory leaks).
	3. Readability gaps.
	4. Codebase Consistency: Ensure the new code matches the existing style of the file. If the PR introduces a new solution, check if a similar utility, pattern, or solution already exists in the codebase that should be reused instead.

	Rules for your output:
	- Do NOT compliment the code. Be direct and concise.
	- If a file looks perfect, do not list it.
	- Group your feedback by filename.
	- Use the format: [File Name] -> [Line Number if applicable] -> [Issue] -> [Suggested Fix].

	Please run the git diff, review the surrounding context for consistency, and start the review.
No results found