review-swarm

Name: review-swarm
Author: Dimillian

3.8kstars203forks

How to install review-swarm?

dimillian/skills/review-swarm

$npx -y skills add Dimillian/Skills --skill review-swarm

Installs into the current project.

Summary

Parallel read-only multi-agent review of a current git diff or explicit file scope to find behavioral regressions, security or privacy risks, performance or reliability issues, and contract or test coverage gaps. Use when the user asks for a review swarm, parallel review, diff re

Files · 1

View on GitHub

SKILL.md

1	# Review Swarm
2
3	Review a diff with four read-only sub-agents in parallel, then have the main agent filter, order, and summarize only the issues that matter. This skill is review-only: sub-agents do not edit files, and the main agent does not apply fixes as part of this workflow.
4
5	## Step 1: Determine Scope and Intent
6
7	Prefer this scope order:
8
9	1. Files or paths explicitly named by the user
10	2. Current git changes
11	3. An explicit branch, commit, or PR diff requested by the user
12	4. Most recently modified tracked files, only if the user asked for a review and there is no clearer diff
13
14	If there is no clear review scope, stop and say so briefly.
15
16	When using git changes, choose the smallest correct diff command:
17
18	- unstaged work: `git diff`
19	- staged work: `git diff --cached`
20	- mixed staged and unstaged work: review both
21	- explicit branch or commit comparison: use exactly what the user requested
22
23	Before launching reviewers, read the closest local instructions and any relevant project docs for the touched area, such as:
24
25	- `AGENTS.md`
26	- repo workflow docs
27	- architecture or contract docs for the touched module
28
29	Build a short intent packet for the reviewers:
30
31	1. What behavior is meant to change
32	2. What behavior should remain unchanged
33	3. Any stated or inferred constraints, such as compatibility, rollout, security, or migration expectations
34
35	If the user did not state the intent clearly, infer it from the diff and say that the inference may be incomplete.
36
37	## Step 2: Launch Four Read-Only Reviewers in Parallel
38
39	Launch four sub-agents when the scope is large enough for parallel review to help. For a tiny diff or one very small file, it is acceptable to review locally instead.
40
41	For every sub-agent:
42
43	- give the same scope and the same intent packet
44	- state that the sub-agent is read-only
45	- do not let the sub-agent edit files, run `apply_patch`, stage changes, commit, or perform any other state-mutating action
46	- ask for concise findings only
47	- ask for: file and line or symbol, issue, why it matters, recommended follow-up, and confidence
48	- tell the sub-agent to avoid nits, style preferences, and speculative concerns without concrete impact
49	- tell the sub-agent to send findings back to the main agent only
50
51	Use these four review roles.
52
53	### Sub-Agent 1: Intent and Regression Review
54
55	Review whether the diff matches the intended behavior change without introducing extra behavior drift.
56
57	Check for:
58
59	1. Unintended behavior changes outside the stated scope
60	2. Broken edge cases or fallback paths
61	3. Contract drift between callers and callees
62	4. Missing updates to adjacent flows that should change together
63
64	This sub-agent is read-only. It must not edit files, apply patches, or make any other workspace changes.
65
66	Recommended sub-agent role: `reviewer`
67
68	### Sub-Agent 2: Security and Privacy Review
69
70	Review the diff for security regressions, privacy risks, and trust-boundary mistakes.
71
72	Check for:
73
74	1. Missing or weakened authn or authz checks
75	2. Unsafe input handling, injection risks, or validation gaps
76	3. Secret, token, or sensitive data exposure
77	4. Risky defaults, permission expansion, or trust of unverified data
78
79	This sub-agent is read-only. It must not edit files, apply patches, or make any other workspace changes.
80
81	Recommended sub-agent role: `reviewer`
82
83	### Sub-Agent 3: Performance and Reliability Review
84
85	Review the diff for new cost, fragility, or operational risk.
86
87	Check for:
88
89	1. Duplicate work, redundant I/O, or unnecessary recomputation
90	2. Added work on startup, render, request, or other hot paths
91	3. Leaks, missing cleanup, retry storms, or subscription drift
92	4. Ordering, race, or failure-handling problems that make the change brittle
93
94	This sub-agent is read-only. It must not edit files, apply patches, or make any other workspace changes.
95
96	Recommended sub-agent role: `reviewer`
97
98	### Sub-Agent 4: Contracts and Coverage Review
99
100	Review the diff for compatibility gaps and missing safety nets.
101
102	Check for:
103
104	1. API, schema, type, config, or feature-flag mismatches
105	2. Migration or backward-compatibility fallout
106	3. Missing or weak tests for the changed behavior
107	4. Missing logs, metrics, assertions, or error paths that make regressions harder to detect
108
109	This sub-agent is read-only. It must not edit files, apply patches, or make any other workspace changes.
110
111	Recommended sub-agent role: `reviewer`
112
113	Report only issues that materially affect correctness, security, privacy, reliability, compatibility, or confidence in the change. It is better to miss a nit than to bury the user in low-value noise.
114
115	## Step 3: A

People who liked this also viewed

6 picks

Type

review-swarm

3.8kstars203forks

View on GitHub

How to install review-swarm?

dimillian/skills/review-swarm

$npx -y skills add Dimillian/Skills --skill review-swarm

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Review Swarm
2
3	Review a diff with four read-only sub-agents in parallel, then have the main agent filter, order, and summarize only the issues that matter. This skill is review-only: sub-agents do not edit files, and the main agent does not apply fixes as part of this workflow.
4
5	## Step 1: Determine Scope and Intent
6
7	Prefer this scope order:
8
9	1. Files or paths explicitly named by the user
10	2. Current git changes
11	3. An explicit branch, commit, or PR diff requested by the user
12	4. Most recently modified tracked files, only if the user asked for a review and there is no clearer diff
13
14	If there is no clear review scope, stop and say so briefly.
15
16	When using git changes, choose the smallest correct diff command:
17
18	- unstaged work: `git diff`
19	- staged work: `git diff --cached`
20	- mixed staged and unstaged work: review both
21	- explicit branch or commit comparison: use exactly what the user requested
22
23	Before launching reviewers, read the closest local instructions and any relevant project docs for the touched area, such as:
24
25	- `AGENTS.md`
26	- repo workflow docs
27	- architecture or contract docs for the touched module
28
29	Build a short intent packet for the reviewers:
30
31	1. What behavior is meant to change
32	2. What behavior should remain unchanged
33	3. Any stated or inferred constraints, such as compatibility, rollout, security, or migration expectations
34
35	If the user did not state the intent clearly, infer it from the diff and say that the inference may be incomplete.
36
37	## Step 2: Launch Four Read-Only Reviewers in Parallel
38
39	Launch four sub-agents when the scope is large enough for parallel review to help. For a tiny diff or one very small file, it is acceptable to review locally instead.
40
41	For every sub-agent:
42
43	- give the same scope and the same intent packet
44	- state that the sub-agent is read-only
45	- do not let the sub-agent edit files, run `apply_patch`, stage changes, commit, or perform any other state-mutating action
46	- ask for concise findings only
47	- ask for: file and line or symbol, issue, why it matters, recommended follow-up, and confidence
48	- tell the sub-agent to avoid nits, style preferences, and speculative concerns without concrete impact
49	- tell the sub-agent to send findings back to the main agent only
50
51	Use these four review roles.
52
53	### Sub-Agent 1: Intent and Regression Review
54
55	Review whether the diff matches the intended behavior change without introducing extra behavior drift.
56
57	Check for:
58
59	1. Unintended behavior changes outside the stated scope
60	2. Broken edge cases or fallback paths
61	3. Contract drift between callers and callees
62	4. Missing updates to adjacent flows that should change together
63
64	This sub-agent is read-only. It must not edit files, apply patches, or make any other workspace changes.
65
66	Recommended sub-agent role: `reviewer`
67
68	### Sub-Agent 2: Security and Privacy Review
69
70	Review the diff for security regressions, privacy risks, and trust-boundary mistakes.
71
72	Check for:
73
74	1. Missing or weakened authn or authz checks
75	2. Unsafe input handling, injection risks, or validation gaps
76	3. Secret, token, or sensitive data exposure
77	4. Risky defaults, permission expansion, or trust of unverified data
78
79	This sub-agent is read-only. It must not edit files, apply patches, or make any other workspace changes.
80
81	Recommended sub-agent role: `reviewer`
82
83	### Sub-Agent 3: Performance and Reliability Review
84
85	Review the diff for new cost, fragility, or operational risk.
86
87	Check for:
88
89	1. Duplicate work, redundant I/O, or unnecessary recomputation
90	2. Added work on startup, render, request, or other hot paths
91	3. Leaks, missing cleanup, retry storms, or subscription drift
92	4. Ordering, race, or failure-handling problems that make the change brittle
93
94	This sub-agent is read-only. It must not edit files, apply patches, or make any other workspace changes.
95
96	Recommended sub-agent role: `reviewer`
97
98	### Sub-Agent 4: Contracts and Coverage Review
99
100	Review the diff for compatibility gaps and missing safety nets.
101
102	Check for:
103
104	1. API, schema, type, config, or feature-flag mismatches
105	2. Migration or backward-compatibility fallout
106	3. Missing or weak tests for the changed behavior
107	4. Missing logs, metrics, assertions, or error paths that make regressions harder to detect
108
109	This sub-agent is read-only. It must not edit files, apply patches, or make any other workspace changes.
110
111	Recommended sub-agent role: `reviewer`
112
113	Report only issues that materially affect correctness, security, privacy, reliability, compatibility, or confidence in the change. It is better to miss a nit than to bury the user in low-value noise.
114
115	## Step 3: A

People who liked this also viewed

6 picks

Type