feat(review): add commit mode to triage-review command

Author: LeoVS09

.claude-plugin/marketplace.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
   "name": "context-engineering-kit",
-  "version": "3.4.0",
+  "version": "3.5.0",
   "description": "Hand-crafted collection of advanced context engineering techniques and patterns with minimal token footprint focused on improving agent result quality.",
   "owner": {
     "name": "NeoLabHQ",
@@ -22,7 +22,7 @@
     {
       "name": "review",
       "description": "Introduce codebase and PR review commands and skills using multiple specialized agents.",
-      "version": "3.1.0",
+      "version": "3.2.0",
       "author": {
         "name": "Vlad Goncharov",
         "email": "vlad.goncharov@neolab.finance"

docs/plugins/review/traiage-review.md

@@ -13,14 +13,27 @@ An orchestrator agent launches four specialized triage agents in parallel, each
 
 ## Review Modes
 
-The orchestrator auto-detects the review mode before launching any agents:
+The orchestrator determines the review mode before launching any agents, checking in this order:
 
-- local changes - review staged, unstaged, and untracked changes
-- branch diff - review changes between current branch and default branch
+- **commit** - reviews the diff introduced by a single commit, not the whole changeset. Triggered by passing `commit <commit-hash>` (reviews that specific commit) or `commit` / `latest commit` with no hash (the orchestrator resolves HEAD to a concrete commit hash via `git rev-parse HEAD` and reviews that). This takes precedence over the other two modes.
+- **branch diff** - review changes between the current branch and the detected default branch (`origin/main` or `origin/master`). Triggered explicitly by passing `branch`, or automatically when there are no local changes and the current branch is not the default branch.
+- **local changes** - review staged, unstaged, and untracked changes. The default behavior when local changes exist and no other mode was requested.
+
+## Usage
+
+| Invocation | Mode | What it reviews |
+|------------|------|------------------|
+| `/traiage-review` | local changes (default) | Staged, unstaged, and untracked changes in the working tree |
+| `/traiage-review branch` | branch diff | Current branch vs. the detected default branch (`origin/main` or `origin/master`) |
+| `/traiage-review commit <commit-hash>` | commit | The diff introduced by that specific commit only |
+| `/traiage-review commit` | commit | The diff introduced by the latest commit (HEAD) |
+| `/traiage-review latest commit` | commit | The diff introduced by the latest commit (HEAD) - same as `commit` with no hash |
+
+For the commit mode's two no-hash forms (`commit` and `latest commit`), the orchestrator resolves the latest commit to a concrete hash with `git rev-parse HEAD` before doing anything else, then treats it exactly like an explicitly given hash - every agent and the random-sample step receive that resolved concrete hash. The reviewed diff is the diff introduced by that single commit (equivalent to `git show <commit-hash>` or `git diff <commit-hash>^!`), not the cumulative diff up to that commit.
 
 ## Triage Agents
 
-The four agents run in parallel, each receiving the mode-appropriate prompt (local-changes or branch-diff):
+The four agents run in parallel, each receiving the mode-appropriate prompt (local-changes, branch-diff, or commit):
 
 | Agent | Focus |
 |-------|-------|

plugins/review/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "review",
-  "version": "3.1.0",
+  "version": "3.2.0",
   "description": "Introduce codebase and PR review commands and skills using multiple specialized agents.",
   "author": {
     "name": "Vlad Goncharov",

plugins/review/agents/change-expectation-agent.md

@@ -24,8 +24,11 @@ Detect the review mode from the instruction you received:
   - `git diff HEAD` — unstaged changes
   - `git diff --cached` — staged changes
   - `git status` — overview of changed files
+- **Commit mode** — instruction says to review the diff introduced by a specific commit whose concrete hash is provided in the instruction (never the literal `HEAD` or `latest` — the orchestrator resolves that first). Use:
+  - `git show <commit-hash>` or `git diff <commit-hash>^!` (equivalently `git diff <commit-hash>^ <commit-hash>`) — full commit diff
+  - `git show --name-only --pretty=format: <commit-hash>` — file names only
 
-Use only read-only git commands. The `origin/<default-branch>` value is provided in the instruction (e.g. `origin/main`).
+Use only read-only git commands. The `origin/<default-branch>` value is provided in the instruction (e.g. `origin/main`). In commit mode the concrete `<commit-hash>` is provided in the instruction.
 
 ## Process
 

plugins/review/agents/change-failure-agent.md

@@ -24,8 +24,11 @@ Detect the review mode from the instruction you received:
   - `git diff HEAD` — unstaged changes
   - `git diff --cached` — staged changes
   - `git status` — overview of changed files
+- **Commit mode** — instruction says to review the diff introduced by a specific commit whose concrete hash is provided in the instruction (never the literal `HEAD` or `latest` — the orchestrator resolves that first). Use:
+  - `git show <commit-hash>` or `git diff <commit-hash>^!` (equivalently `git diff <commit-hash>^ <commit-hash>`) — full commit diff
+  - `git show --name-only --pretty=format: <commit-hash>` — file names only
 
-Use only read-only git commands. The `origin/<default-branch>` value is provided in the instruction (e.g. `origin/main`).
+Use only read-only git commands. The `origin/<default-branch>` value is provided in the instruction (e.g. `origin/main`). In commit mode the concrete `<commit-hash>` is provided in the instruction.
 
 ## Process
 

plugins/review/agents/change-impact-agent.md

@@ -24,8 +24,11 @@ Detect the review mode from the instruction you received:
   - `git diff HEAD` — unstaged changes
   - `git diff --cached` — staged changes
   - `git status` — overview of changed files
+- **Commit mode** — instruction says to review the diff introduced by a specific commit whose concrete hash is provided in the instruction (never the literal `HEAD` or `latest` — the orchestrator resolves that first). Use:
+  - `git show <commit-hash>` or `git diff <commit-hash>^!` (equivalently `git diff <commit-hash>^ <commit-hash>`) — full commit diff
+  - `git show --name-only --pretty=format: <commit-hash>` — file names only
 
-Use only read-only git commands. The `origin/<default-branch>` value is provided in the instruction (e.g. `origin/main`).
+Use only read-only git commands. The `origin/<default-branch>` value is provided in the instruction (e.g. `origin/main`). In commit mode the concrete `<commit-hash>` is provided in the instruction.
 
 ## Process
 

plugins/review/agents/change-story-agent.md

@@ -24,8 +24,11 @@ Detect the review mode from the instruction you received:
   - `git diff HEAD` — unstaged changes
   - `git diff --cached` — staged changes
   - `git status` — overview of changed files
+- **Commit mode** — instruction says to review the diff introduced by a specific commit whose concrete hash is provided in the instruction (never the literal `HEAD` or `latest` — the orchestrator resolves that first). Use:
+  - `git show <commit-hash>` or `git diff <commit-hash>^!` (equivalently `git diff <commit-hash>^ <commit-hash>`) — full commit diff
+  - `git show --name-only --pretty=format: <commit-hash>` — file names only
 
-Use only read-only git commands. The `origin/<default-branch>` value is provided in the instruction (e.g. `origin/main`).
+Use only read-only git commands. The `origin/<default-branch>` value is provided in the instruction (e.g. `origin/main`). In commit mode the concrete `<commit-hash>` is provided in the instruction.
 
 ## Process
 

plugins/review/skills/traiage-review/SKILL.md

@@ -17,12 +17,17 @@ CRITICAL: Human attention and time is limited. Reviewer cannot check all existin
 - You ARE allowed to run the following read-only commands yourself, and ONLY these:
     - The random sample script (see "## Random Sample Script").
     - Read-only git detection commands needed for review-mode and default-branch detection: `git status`, `git diff --name-only`, `git branch`, `git symbolic-ref`, `git rev-parse`.
+    - Read-only commit commands needed for commit-mode detection and latest-commit resolution: `git rev-parse HEAD` (resolve the latest commit), `git show --name-only`, `git diff` (commit-diff inspection).
 - You MUST NOT do any implementation work, read source files, or run any mutation git command (commit, stash, push, checkout, reset, revert, add, merge, rebase, etc.). If you try to read source files or run any command outside the allowed read-only list above, you will be killed! Your life is at stake!
 
 ## Process
 
 1. Determine the review mode BEFORE launching agents:
-    - If a `branch` param was passed to the skill → use the **branch-diff workflow** directly.
+    - If a `commit` param was passed to the skill → use the **commit workflow** directly (this takes precedence over the local-changes/branch auto-detection below):
+        - If a concrete commit hash was given (`commit <commit-hash>`) → use that hash.
+        - If no hash was given (`commit` or `latest commit`) → resolve the latest commit with `git rev-parse HEAD` and use the resolved concrete hash.
+        - Record the resolved concrete commit hash for use in the commit-mode prompt and the random sample script.
+    - Else, if a `branch` param was passed to the skill → use the **branch-diff workflow** directly.
     - Else, check for local changes with a read-only command:
       `git status --porcelain` (non-empty output means staged, unstaged, or untracked changes exist).
         - If local changes exist → use the **local-changes workflow** (default behavior).
@@ -34,7 +39,7 @@ CRITICAL: Human attention and time is limited. Reviewer cannot check all existin
         - Primary: `git symbolic-ref --short refs/remotes/origin/HEAD` → strip the `origin/` prefix to get `main` or `master`.
         - Fallback (if primary fails): `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`.
         - Record the detected default ref as `origin/<default-branch>` (e.g. `origin/main`) for use in the branch-mode prompt and the random sample script.
-2. Launch 4 parallel agents, to build his own list of files that require attention based on specific process for each agent. Pass the mode-appropriate agent prompt (see "## Agents"): the local-changes prompt for the local-changes workflow, or the branch-mode prompt (with the detected `origin/<default-branch>` filled in) for the branch-diff workflow.
+2. Launch 4 parallel agents, to build his own list of files that require attention based on specific process for each agent. Pass the mode-appropriate agent prompt (see "## Agents"): the local-changes prompt for the local-changes workflow, the branch-mode prompt (with the detected `origin/<default-branch>` filled in) for the branch-diff workflow, or the commit-mode prompt (with the resolved concrete `<commit-hash>` filled in) for the commit workflow.
     - change-story-agent
     - change-impact-agent
     - change-failure-agent
@@ -70,9 +75,19 @@ Review the diff of the current branch against the default branch `origin/<defaul
 
 ```
 
+### Commit-mode prompt for commit workflow
+
+Replace `<commit-hash>` with the concrete commit hash the orchestrator resolved:
+
+```md
+
+Review the diff introduced by commit `<commit-hash>` (use `git show <commit-hash>` or `git diff <commit-hash>^!`, equivalently `git diff <commit-hash>^ <commit-hash>`) according to your process and provide list of files that require attention.
+
+```
+
 ## Random Sample Script
 
-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`).
+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), the **branch mode** block for the branch-diff workflow (files changed between the default branch and the current branch), and the **commit mode** block for the commit workflow (files changed by the commit). Replace `origin/<default-branch>` with the default ref you detected (e.g. `origin/main`), and `<commit-hash>` with the resolved concrete commit hash.
 
 **Local mode** (staged + unstaged + untracked):
 
@@ -118,6 +133,29 @@ print(random_files)
 
 ```
 
+**Commit mode** (files changed by the commit):
+
+```python
+
+import random
+import subprocess
+
+# Files changed by the commit
+commit = '<commit-hash>'  # set to the resolved concrete commit hash
+changed_files = sorted(set(
+    line for line in subprocess.check_output(
+        ['git', 'show', '--name-only', '--pretty=format:', commit]
+    ).decode('utf-8').splitlines()
+    if line.strip()
+))
+
+# 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.
 
 ## Output Format