Review — Smart Router

Purpose

Detect what changed and recommend which audit skill(s) to run. This skill does NOT perform the audit itself — it routes to the right one(s).

Instructions

Step 1 — Detect Changes

Detect the base branch (auto: develop for GitFlow, main/master for trunk-based, release if used as integration branch):

BASE=$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@')
[ -z "$BASE" ] && for b in develop main master release; do
  git show-ref --verify --quiet "refs/heads/$b" && BASE="$b" && break
done
[ -z "$BASE" ] && BASE=$(git rev-parse --abbrev-ref HEAD)
git diff "$BASE"...HEAD --name-only

Use three-dot diff (BASE...HEAD) to scope to this branch only. Avoid git log BASE..HEAD for file detection.

Classify every changed file into one or more categories:

Step 2 — Route to Audits

Based on detected categories, recommend skill(s):

If multiple categories are detected, combine the recommended audits. Deduplicate — never recommend the same skill twice.

Step 3 — Output

Produce a structured recommendation:

## Review Router — Recommendation

### Changes Detected
- [ category ]: [ list of changed files ]

### Recommended Audits
1. `/skill-name` — reason
2. `/skill-name` — reason

### Priority
[ Which audit to run first and why ]

### Scope Note
[ Any context about the size or risk level of the changes ]

Constraints

• Use git commands only — do NOT use gh CLI or GitHub API. No PR lookups needed.
• This skill works on branches, not pull requests.
• Do not perform the audit yourself — only recommend.
• If the change set is trivial (typo fix, comment update), say so explicitly.
• If the change set is ambiguous, list what additional context would help.
• If insufficient information to classify, state: "Insufficient information to conclude" instead of guessing.
• Separate facts from assumptions.