From review
This skill should be used when need prioritize what changed code in repository human must review.
How this skill is triggered — by the user, by Claude, or both
Slash command
/review:traiage-reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The goal of this skill is to help human prioritize specific files in repository that require attention over the entire list of changes.
The goal of this skill is to help human prioritize specific files in repository that require attention over the entire list of changes.
CRITICAL: Human attention and time is limited. Reviewer cannot check all existing changes in repository. Your job is not to find all changes that require attention, you job is to build exhaustive list of files from whole pool of changes, that probably will cause this change to fail review!
git status, git diff --name-only, git branch, git symbolic-ref, git rev-parse.branch param was passed to the skill → use the branch-diff workflow directly.git status --porcelain (non-empty output means staged, unstaged, or untracked changes exist).
git rev-parse --abbrev-ref HEAD.git symbolic-ref --short refs/remotes/origin/HEAD → strip the origin/ prefix to get main or master.git rev-parse --verify origin/main — if it succeeds, default is main; otherwise try git rev-parse --verify origin/master — if it succeeds, default is master.origin/<default-branch> (e.g. origin/main) for use in the branch-mode prompt and the random sample script.origin/<default-branch> filled in) for the branch-diff workflow.
Choose the prompt that matches the review mode determined in the Process step, and pass it EXACTLY to launch change-story-agent, change-impact-agent, change-failure-agent and change-expectation-agent.
Default path for local-changes workflow — staged, unstaged, and untracked changes:
Review current project staged AND unstaged changes according to your process and provide list of files that require attention.
Replace origin/<default-branch> with the default ref you detected, e.g. origin/main:
Review the diff of the current branch against the default branch `origin/<default-branch>` (use `git diff origin/<default-branch>...HEAD`, three-dot) according to your process and provide list of files that require attention.
Use this script to pick 20 random files from the whole batch of changed files. Use the local mode block for the local-changes workflow (staged + unstaged + untracked) and the branch mode block for the branch-diff workflow (files changed between the default branch and the current branch). Replace origin/<default-branch> with the default ref you detected (e.g. origin/main).
Local mode (staged + unstaged + untracked):
import random
import subprocess
# Tracked changes (staged + unstaged) relative to HEAD
tracked = subprocess.check_output(['git', 'diff', '--name-only', 'HEAD']).decode('utf-8').splitlines()
# Untracked files (new, not yet added)
untracked = subprocess.check_output(['git', 'ls-files', '--others', '--exclude-standard']).decode('utf-8').splitlines()
changed_files = sorted(set(tracked + untracked))
# Pick up to 20 random files (won't crash on small changesets)
random_files = random.sample(changed_files, min(20, len(changed_files)))
print(random_files)
Branch mode (files changed on the current branch vs the default branch):
import random
import subprocess
# Files changed between the default branch and the current branch (three-dot: since the merge base)
default_ref = 'origin/<default-branch>' # e.g. 'origin/main' — set to the detected default ref
changed_files = sorted(set(
subprocess.check_output(
['git', 'diff', '--name-only', f'{default_ref}...HEAD']
).decode('utf-8').splitlines()
))
# Pick up to 20 random files (won't crash on small changesets)
random_files = random.sample(changed_files, min(20, len(changed_files)))
print(random_files)
In list of random files, pick only files that relate to logic changes, ignore documentation, tests, configuration, etc. Except case when there no files left, that wasn't highlighted by agents key files list.
### Key Facts
<note>Key facts should be provided by Change Story Agent</note>
- What change trying to achive: <if any>
- Architecture change: <if any>
- Design decisions: <if any>
- Risks: <if any>
- Solutions: <if any>
### Key Files
| File Path | Changed Lines | Importance | Severity | Detectability | Confidence |
|------------------|-----------------------|--------------|------------|-----------------|------------|
| <file path> | <changed lines count> | <importance> | <severity> | <detectability> | <confidence> |
<note>
- include in last column confidence rating that was provided by agent that provided this file (if there multiple, include highest confidence)
- in the rest columns include ratings that were provided by agent that provided this file (if there multiple, include highest rating. If there no rating, mark it as "-")
</note>
### Random Sample
| File Path | Changed Lines |
|-------------|-----------------------|
| <file path> | <changed lines count> |
### Declarative Files
| File Path | Changed Lines |
|-------------|-----------------------|
| <file path> | <changed lines count> |
npx claudepluginhub neolabhq/context-engineering-kit --plugin reviewGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Dispatches multiple subagents concurrently for independent tasks without shared state. Use when facing 2+ unrelated failures or subsystems that can be investigated in parallel.