{"id":48247718,"title":"Show HN: I build a tool to encourage before reviewing code, review intents","points":3,"user":"crs0910","time":1779544473,"time_ago":"9 hours ago","type":"link","content":"

In the past, I’ve encountered agents repeatedly falling into the same old pitfalls while writing code—pitfalls that might be difficult to include in the spec documentation.

These days, developers rarely review code line by line, but when agents do review it, they often focus only on code quality.

Additionally, in some cases, agents from different developers make changes to the same product logic (not just within the same code file), but issues often aren’t discovered until the branch merge phase, requiring rework.

To solve these problems, I created Mainline.

Mainline uses CLI, skills, and coding agent hooks to store the intent that humans express through agents in Git.

Before editing, agents can read historical intents, decisions, and risks; after making changes, they can record the rationale, trade-offs, and review notes. You can also export a static Hub for others to view historical intents, risks, and hotspots

Repo: https://github.com/mainline-org/mainline

How to use: curl -fsSL https://raw.githubusercontent.com/mainline-org/mainline/main... | bash

mainline doctor --setup

mainline init --actor-name "alice"

I’d like to know if you think the granularity of intent records is useful. Does reviewing intent before a code review actually reduce the reviewer’s burden?","url":"https://github.com/mainline-org/mainline","domain":"github.com","comments":[{"id":48249471,"level":0,"user":"Mechse","time":1779557515,"time_ago":"5 hours ago","content":"

By the time i’m reading the diff i’ve already lost track of what i actually asked for. gonna try it out.","comments":[]}],"comments_count":1}