signal-review

⚡ signal-review — Templated Code Review

One line per issue. Severity required. Summary at the end. No prose.

---

Invocation Triggers

Activate when user says any of:

• /signal-review
• "review this", "review my code", "review this file"
• "check this PR", "code review", "look at this diff"
• "what's wrong with this", "any issues with this code"

Target can be: a file, a diff, a PR URL, a code block, or the current working directory.

Slash command behavior

If the user's message is only /signal-review, treat that as review now.

• Do not stop after acknowledging the skill.
• Do not ask for confirmation unless the user explicitly asked for draft / dry behavior.
• Immediately inspect the provided target (or current working context) and output the review in the format below in the same turn.

---

Output Format

One line per issue:

{file}:{line}|{issue}|{severity:1-5}|{fix}

Full example:

auth.js:47|nullref on empty arr|4|add guard clause before map
api.js:103|missing await on async call|5|add await
utils.js:12|unused import lodash|1|remove import
∑ 3 issues [1×sev5, 1×sev4, 1×sev1]  critical→api.js:103

Rules:

• Severity is required on every line. No exceptions.
• Issue description: max ~60 chars, imperative noun phrase ("nullref on empty arr", not "there is a null reference error")
• Fix: max ~50 chars, imperative ("add guard clause before map", not "you should add a guard clause")
• Order by severity descending (sev5 first)
• One summary line at the end, always

---

Summary Line Format

∑ {N} issues [{breakdown}]  critical→{highest-sev-location}

Examples:

∑ 5 issues [2×sev5, 1×sev3, 2×sev1]  critical→auth.js:47
∑ 1 issue [1×sev2]
∑ 0 issues ✓

If zero issues: output only ∑ 0 issues ✓. No explanation, no praise.

---

Severity Scale

Full definitions in references/severity.md. Quick reference:

Level	Meaning
5	Breaks in production, security vulnerability, data loss
4	Likely runtime error, will crash under normal use
3	Wrong behavior under specific conditions, logic error
2	Code smell, maintainability issue, confusing pattern
1	Style, minor cleanup, nitpick