@hyperlogue/r3 0.7.0 → 0.8.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +13 -0
- package/package.json +5 -5
package/README.md
CHANGED
|
@@ -136,6 +136,19 @@ Feedback anchors to a **quote**, not a line number: in a files review your notes
|
|
|
136
136
|
follow the code as it's edited; in a diff review the rounds are immutable, so
|
|
137
137
|
nothing drifts.
|
|
138
138
|
|
|
139
|
+
## How r3 compares to similar tools
|
|
140
|
+
|
|
141
|
+
| Tool | How r3 differs |
|
|
142
|
+
| -------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
143
|
+
| [difit](https://github.com/yoshiko-pg/difit) / [diffx](https://github.com/wong2/diffx) | r3 makes the review loop live. The agent `watch`es, you Submit, replies land back in the UI, tracking every item to resolution. r3 also supports raw text files like design docs, not just diffs. |
|
|
144
|
+
| GitHub / GitLab PRs | r3 drives the local pre-PR loop with your agent: nothing needs a remote, a push, or even a commit. |
|
|
145
|
+
| AI review bots (CodeRabbit, Copilot code review, …) | In r3 _you_ review the AI's work: the agent is the author, addressing your feedback. |
|
|
146
|
+
|
|
147
|
+
If you want a one-shot look at a diff with no state left behind, difit and diffx
|
|
148
|
+
are good enough. r3 shines when the review outgrows a single pass — feedback
|
|
149
|
+
spans several rounds, and each item keeps its thread and status until it's
|
|
150
|
+
resolved.
|
|
151
|
+
|
|
139
152
|
## Remote access
|
|
140
153
|
|
|
141
154
|
If you work on a remote dev server, r3 listens on loopback there, and you reach
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@hyperlogue/r3",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.8.0",
|
|
4
4
|
"description": "Review. Revise. Resolve. — a local-first review tool for AI-generated code and docs. Runs the matching prebuilt native r3 binary (shipped as a per-platform optional dependency); works with `bunx @hyperlogue/r3` and `npx @hyperlogue/r3`.",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"type": "module",
|
|
@@ -17,10 +17,10 @@
|
|
|
17
17
|
"launch.mjs"
|
|
18
18
|
],
|
|
19
19
|
"optionalDependencies": {
|
|
20
|
-
"@hyperlogue/r3-darwin-arm64": "0.
|
|
21
|
-
"@hyperlogue/r3-darwin-x64": "0.
|
|
22
|
-
"@hyperlogue/r3-linux-x64": "0.
|
|
23
|
-
"@hyperlogue/r3-linux-arm64": "0.
|
|
20
|
+
"@hyperlogue/r3-darwin-arm64": "0.8.0",
|
|
21
|
+
"@hyperlogue/r3-darwin-x64": "0.8.0",
|
|
22
|
+
"@hyperlogue/r3-linux-x64": "0.8.0",
|
|
23
|
+
"@hyperlogue/r3-linux-arm64": "0.8.0"
|
|
24
24
|
},
|
|
25
25
|
"engines": {
|
|
26
26
|
"node": ">=18"
|