redline-review 2.0.0 → 2.0.1
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.
|
@@ -25,6 +25,37 @@ redline-review --prompt strict # CRITICAL/HIGH severity only
|
|
|
25
25
|
redline-review --prompt lightweight # top 3 issues, quick scan
|
|
26
26
|
```
|
|
27
27
|
|
|
28
|
+
## Range review
|
|
29
|
+
|
|
30
|
+
Review changes between two commits or tags:
|
|
31
|
+
|
|
32
|
+
```bash
|
|
33
|
+
redline-review range --from <ref> --to <ref>
|
|
34
|
+
redline-review range --from v1.0.0 --to v1.1.0 --prompt strict
|
|
35
|
+
```
|
|
36
|
+
|
|
37
|
+
## Commit walk
|
|
38
|
+
|
|
39
|
+
Step through commits one at a time. Run `--start`, review the output, then `--next` to advance:
|
|
40
|
+
|
|
41
|
+
```bash
|
|
42
|
+
redline-review walk --start # begin
|
|
43
|
+
redline-review walk --next # advance
|
|
44
|
+
redline-review walk --status # check progress
|
|
45
|
+
redline-review walk --reset # clear state
|
|
46
|
+
redline-review walk --start --interval 2 # batch commits
|
|
47
|
+
redline-review walk --start --direction forwards # walk oldest → newest
|
|
48
|
+
```
|
|
49
|
+
|
|
50
|
+
## Repo review
|
|
51
|
+
|
|
52
|
+
Full repository audit. Output is a manifest — use file-reading tools to explore as instructed:
|
|
53
|
+
|
|
54
|
+
```bash
|
|
55
|
+
redline-review repo
|
|
56
|
+
redline-review repo --max-tree-depth 3
|
|
57
|
+
```
|
|
58
|
+
|
|
28
59
|
## One-shot (no global install)
|
|
29
60
|
|
|
30
61
|
```bash
|
|
@@ -12,15 +12,14 @@ The CLI assembles a focused code review prompt from the git diff and the install
|
|
|
12
12
|
npm install -g redline-review
|
|
13
13
|
```
|
|
14
14
|
|
|
15
|
-
##
|
|
15
|
+
## Branch diff (default)
|
|
16
16
|
|
|
17
17
|
```bash
|
|
18
|
-
#
|
|
18
|
+
# Auto-detect base branch
|
|
19
19
|
redline-review
|
|
20
20
|
|
|
21
|
-
# Pin the base branch explicitly
|
|
21
|
+
# Pin the base branch explicitly
|
|
22
22
|
redline-review --base origin/develop
|
|
23
|
-
redline-review --base develop
|
|
24
23
|
|
|
25
24
|
# Focused by review type
|
|
26
25
|
redline-review --type auth,performance
|
|
@@ -35,7 +34,60 @@ redline-review --prompt strict
|
|
|
35
34
|
redline-review --prompt lightweight
|
|
36
35
|
```
|
|
37
36
|
|
|
37
|
+
## Range review
|
|
38
|
+
|
|
39
|
+
Review changes between two specific commits or tags.
|
|
40
|
+
|
|
41
|
+
```bash
|
|
42
|
+
redline-review range --from <ref> --to <ref>
|
|
43
|
+
redline-review range --from v1.0.0 --to v1.1.0
|
|
44
|
+
redline-review range --from HEAD~5 --to HEAD --prompt strict
|
|
45
|
+
```
|
|
46
|
+
|
|
47
|
+
`--to` defaults to HEAD if omitted.
|
|
48
|
+
|
|
49
|
+
## Commit walk
|
|
50
|
+
|
|
51
|
+
Step through commits one at a time.
|
|
52
|
+
|
|
53
|
+
```bash
|
|
54
|
+
redline-review walk --start
|
|
55
|
+
redline-review walk --next
|
|
56
|
+
redline-review walk --status
|
|
57
|
+
redline-review walk --reset
|
|
58
|
+
```
|
|
59
|
+
|
|
60
|
+
**Interactive flow:**
|
|
61
|
+
|
|
62
|
+
1. Run `redline-review walk --start` and capture stdout.
|
|
63
|
+
2. Perform the review described by that prompt.
|
|
64
|
+
3. Present findings to the user, then ask: "Continue to the next commit?"
|
|
65
|
+
4. If the user confirms, run `redline-review walk --next` and repeat from step 2.
|
|
66
|
+
5. If the user declines, stop. State persists — they can resume later with `--next`.
|
|
67
|
+
6. When walk is complete (`--next` exits with no stdout), tell the user.
|
|
68
|
+
|
|
69
|
+
Optional flags for `--start`:
|
|
70
|
+
|
|
71
|
+
```bash
|
|
72
|
+
redline-review walk --start --interval 2 # batch 2 commits per step
|
|
73
|
+
redline-review walk --start --direction forwards # walk oldest → newest
|
|
74
|
+
redline-review walk --start --from v1.0.0 --to v2.0.0 # explicit range
|
|
75
|
+
redline-review walk --start --force # overwrite in-progress walk
|
|
76
|
+
```
|
|
77
|
+
|
|
78
|
+
Flags `--stack`, `--type`, and `--prompt` passed at `--start` time are captured and reused for every `--next`.
|
|
79
|
+
|
|
80
|
+
## Repo review
|
|
81
|
+
|
|
82
|
+
Full repository architecture audit. The output is a manifest with an annotated file tree and orientation files — use your file-reading tools to explore the codebase as instructed by the prompt.
|
|
83
|
+
|
|
84
|
+
```bash
|
|
85
|
+
redline-review repo
|
|
86
|
+
redline-review repo --max-tree-depth 3
|
|
87
|
+
redline-review repo --stack go --type architecture
|
|
88
|
+
```
|
|
89
|
+
|
|
38
90
|
## How to use as a Claude Code skill
|
|
39
91
|
|
|
40
|
-
Place this file at `.claude/commands/redline-review.md` in your project.
|
|
92
|
+
Place this file at `.claude/commands/redline-review.md` in your project (or `~/.claude/commands/redline-review.md` for global access).
|
|
41
93
|
Then invoke it with `/redline-review` in Claude Code.
|
|
@@ -31,6 +31,37 @@ redline-review --prompt strict # CRITICAL/HIGH only
|
|
|
31
31
|
redline-review --prompt lightweight # top 3 issues
|
|
32
32
|
```
|
|
33
33
|
|
|
34
|
+
## Range review
|
|
35
|
+
|
|
36
|
+
Review changes between two commits or tags:
|
|
37
|
+
|
|
38
|
+
```bash
|
|
39
|
+
redline-review range --from <ref> --to <ref>
|
|
40
|
+
redline-review range --from v1.0.0 --to v1.1.0 --prompt strict
|
|
41
|
+
```
|
|
42
|
+
|
|
43
|
+
## Commit walk
|
|
44
|
+
|
|
45
|
+
Step through commits one at a time. Run `--start`, review the output, then `--next` to advance:
|
|
46
|
+
|
|
47
|
+
```bash
|
|
48
|
+
redline-review walk --start # begin
|
|
49
|
+
redline-review walk --next # advance
|
|
50
|
+
redline-review walk --status # check progress
|
|
51
|
+
redline-review walk --reset # clear state
|
|
52
|
+
redline-review walk --start --interval 2 # batch commits
|
|
53
|
+
redline-review walk --start --direction forwards # walk oldest → newest
|
|
54
|
+
```
|
|
55
|
+
|
|
56
|
+
## Repo review
|
|
57
|
+
|
|
58
|
+
Full repository audit. Output is a manifest — use file-reading tools to explore as instructed:
|
|
59
|
+
|
|
60
|
+
```bash
|
|
61
|
+
redline-review repo
|
|
62
|
+
redline-review repo --max-tree-depth 3
|
|
63
|
+
```
|
|
64
|
+
|
|
34
65
|
## One-shot (no global install)
|
|
35
66
|
|
|
36
67
|
```bash
|
|
@@ -24,8 +24,6 @@ Take the full output and treat it as your review instructions. Perform the revie
|
|
|
24
24
|
|
|
25
25
|
## Focused reviews
|
|
26
26
|
|
|
27
|
-
In the Copilot Chat panel, ask it to run:
|
|
28
|
-
|
|
29
27
|
```bash
|
|
30
28
|
redline-review --type auth,performance
|
|
31
29
|
redline-review --stack laravel,inertia --type backend
|
|
@@ -33,6 +31,37 @@ redline-review --prompt strict
|
|
|
33
31
|
redline-review --prompt lightweight
|
|
34
32
|
```
|
|
35
33
|
|
|
34
|
+
## Range review
|
|
35
|
+
|
|
36
|
+
Review changes between two commits or tags:
|
|
37
|
+
|
|
38
|
+
```bash
|
|
39
|
+
redline-review range --from <ref> --to <ref>
|
|
40
|
+
redline-review range --from v1.0.0 --to v1.1.0 --prompt strict
|
|
41
|
+
```
|
|
42
|
+
|
|
43
|
+
## Commit walk
|
|
44
|
+
|
|
45
|
+
Step through commits one at a time. After each step, perform the review from the output, then run `--next` to continue:
|
|
46
|
+
|
|
47
|
+
```bash
|
|
48
|
+
redline-review walk --start # begin
|
|
49
|
+
redline-review walk --next # advance
|
|
50
|
+
redline-review walk --status # check progress
|
|
51
|
+
redline-review walk --reset # clear state
|
|
52
|
+
redline-review walk --start --interval 2 # batch commits
|
|
53
|
+
redline-review walk --start --direction forwards # walk oldest → newest
|
|
54
|
+
```
|
|
55
|
+
|
|
56
|
+
## Repo review
|
|
57
|
+
|
|
58
|
+
Full repository audit. Output is a manifest — use file-reading tools to explore the codebase as instructed:
|
|
59
|
+
|
|
60
|
+
```bash
|
|
61
|
+
redline-review repo
|
|
62
|
+
redline-review repo --max-tree-depth 3
|
|
63
|
+
```
|
|
64
|
+
|
|
36
65
|
## Workspace instructions path
|
|
37
66
|
|
|
38
67
|
`.github/copilot-instructions.md` is loaded automatically by Copilot in VS Code for workspace-level context.
|
|
@@ -25,6 +25,37 @@ redline-review --prompt strict
|
|
|
25
25
|
redline-review --prompt lightweight
|
|
26
26
|
```
|
|
27
27
|
|
|
28
|
+
## Range review
|
|
29
|
+
|
|
30
|
+
Review changes between two commits or tags:
|
|
31
|
+
|
|
32
|
+
```bash
|
|
33
|
+
redline-review range --from <ref> --to <ref>
|
|
34
|
+
redline-review range --from v1.0.0 --to v1.1.0 --prompt strict
|
|
35
|
+
```
|
|
36
|
+
|
|
37
|
+
## Commit walk
|
|
38
|
+
|
|
39
|
+
Step through commits one at a time. Run `--start`, review the output, then `--next` to advance:
|
|
40
|
+
|
|
41
|
+
```bash
|
|
42
|
+
redline-review walk --start # begin
|
|
43
|
+
redline-review walk --next # advance
|
|
44
|
+
redline-review walk --status # check progress
|
|
45
|
+
redline-review walk --reset # clear state
|
|
46
|
+
redline-review walk --start --interval 2 # batch commits
|
|
47
|
+
redline-review walk --start --direction forwards # walk oldest → newest
|
|
48
|
+
```
|
|
49
|
+
|
|
50
|
+
## Repo review
|
|
51
|
+
|
|
52
|
+
Full repository audit. Output is a manifest — use file-reading tools to explore as instructed:
|
|
53
|
+
|
|
54
|
+
```bash
|
|
55
|
+
redline-review repo
|
|
56
|
+
redline-review repo --max-tree-depth 3
|
|
57
|
+
```
|
|
58
|
+
|
|
28
59
|
## Integration tip
|
|
29
60
|
|
|
30
61
|
Add to your project's `AGENTS.md` or OpenCode instructions:
|