<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: lizhengfeng101</title><link>https://news.ycombinator.com/user?id=lizhengfeng101</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Fri, 05 Jun 2026 22:27:24 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=lizhengfeng101" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by lizhengfeng101 in "Open Code Review – An AI-powered code review CLI tool"]]></title><description><![CDATA[
<p>I'm sorry — we didn't expect to receive so much attention from the developer community so soon after open-sourcing the project. Some parts of the codebase are not yet fully polished. We are currently refactoring the LLM module and will address this as soon as possible. Once again, I sincerely apologize for the inconvenience.</p>
]]></description><pubDate>Fri, 05 Jun 2026 11:34:37 +0000</pubDate><link>https://news.ycombinator.com/item?id=48411017</link><dc:creator>lizhengfeng101</dc:creator><comments>https://news.ycombinator.com/item?id=48411017</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48411017</guid></item><item><title><![CDATA[New comment by lizhengfeng101 in "Open Code Review – An AI-powered code review CLI tool"]]></title><description><![CDATA[
<p>Thank you all for the interest in Open Code Review!<p>This project was incubated from an AI code review tool that has been widely used by developers inside Alibaba at scale. The reason we decided to open-source it is simple — we noticed that many developers in the community are either paying for similar tools or using skills to perform AI code reviews.<p>As someone who has done deep research in this space, I think skills are actually a great approach, and running them as sub-agents is an elegant way to reduce context pollution. That said, skills do come with inherent limitations from general-purpose agents — they can be hard to debug, hard to evaluate, and difficult to tune. That's why we rewrote our internal tool in Go as a CLI and open-sourced it. Our goal is simple: free, token-efficient, and better results — while being easy to integrate into agent frameworks like Claude Code and Codex.<p>Our Design Philosophy: Deterministic Engineering × Agent Hybrid
We believe the best code review system combines the reliability of engineering with the flexibility of AI.<p>Deterministic Engineering — for hard constraints<p>We use engineering logic (not LLMs) to handle the parts of code review that simply cannot go wrong:<p>Precise file filtering — Clearly defines which files need review and which should be excluded, ensuring no critical change is ever missed.
Intelligent file bundling — Groups related files into the same review unit (e.g., message_en.properties and message_zh.properties are packed together). Each bundle is handled as an independent sub-agent with isolated context — this divide-and-conquer strategy performs exceptionally well on large changesets and naturally supports concurrent review.
Fine-grained rule matching — Matches review rules based on file characteristics, keeping the model's attention focused and eliminating information noise from the start. Compared to pure LLM-driven rule guidance, template-engine-based rule matching produces more stable and predictable behavior.
Standalone location & reflection components — Independent comment localization and comment reflection modules systematically improve both the positional accuracy and content quality of AI feedback.
Agent — for dynamic decision making<p>We let the Agent shine where it truly excels — dynamic reasoning and context retrieval:<p>Scenario-optimized prompts — Deeply tuned prompt templates for code review scenarios, improving output quality while significantly reducing token consumption.
Curated scenario-specific toolset — Based on in-depth analysis of tool call traces from large-scale production data — including call frequency distribution, repeated invocation rates per tool, and the impact of adding new tools on overall call chains — we carefully selected and restructured the general-purpose agent toolset into a specialized toolkit that is more stable and predictable in code review scenarios.
Due to some internal dependencies and compliance requirements, a few features haven't been released publicly yet. But I believe as more external developers show interest in this tool, we'll accelerate the alignment between our internal and external versions.<p>Finally, a huge thank you to everyone following this project.  We want it to keep getting better, and we hope to see more free, high-quality tools like this emerge from the community.</p>
]]></description><pubDate>Fri, 05 Jun 2026 04:32:15 +0000</pubDate><link>https://news.ycombinator.com/item?id=48407978</link><dc:creator>lizhengfeng101</dc:creator><comments>https://news.ycombinator.com/item?id=48407978</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48407978</guid></item></channel></rss>