From Dev10x
Reviews own branch changes vs base branch using git diff, runs Python checks (ruff, black, mypy), produces structured findings with severity/file/line/fix for pre-PR self-review.
npx claudepluginhub dev10x-guru/dev10x-claude --plugin Dev10xThis skill is limited to using the following tools:
Review current branch changes against the base branch, applying project
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Review current branch changes against the base branch, applying project
review guidelines. Produces structured findings that Dev10x:review-fix
can consume to create fixup commits.
--unattended — skip finding approval, auto-advance to
Dev10x:review-fix for all actionable findingswork-on shipping pipelineNot for remote PR review — use Dev10x:gh-pr-review to post
findings to GitHub.
This skill follows references/task-orchestration.md patterns
(Tier: Standard).
Auto-advance: Complete each step and immediately start the next. Never pause between steps to ask "should I continue?".
REQUIRED: Create tasks before ANY work. Execute these
TaskCreate calls at startup:
TaskCreate(subject="Verify branch state", activeForm="Checking branch")TaskCreate(subject="Run automated checks", activeForm="Running checks")TaskCreate(subject="Review changed files", activeForm="Reviewing files")TaskCreate(subject="Present findings", activeForm="Presenting findings")Set sequential dependencies.
Nested-mode exemption: When invoked as a nested skill within
a parent orchestrator (e.g., via Skill() from Dev10x:work-on),
startup task creation is optional — at most 1 summary task. The
parent provides progress visibility. See
references/task-orchestration.md § Delegated Invocation Exception.
git develop-log alias to find commits
ahead of develop. If alias fails, fall back to origin/developgit develop-diff
Parse the diff to extract the list of changed files with their change types (added, modified, deleted, renamed).
Run in parallel where possible:
ruff check on changed Python filesblack --check on changed Python filesmypy on changed Python files (if configured)Collect any failures as findings with severity ERROR and
source automated.
For each changed file in the diff:
references/review-checks-common.md — false positive prevention.claude/agents/reviewer-*.md — domain-specific checks based
on file type (see .claude/rules/INDEX.md for routing)False Positive Prevention Gate (from review-checks-common.md):
Before recording any finding, verify:
Each finding is a structured object:
Finding:
severity: ERROR | WARNING | INFO
confidence: <0-100>
source: automated | manual
file: <path>
line: <number>
description: <what's wrong>
suggested_fix: <code or guidance>
category: <bug | security | architecture | style | test>
Confidence scoring (GH-872): Each finding includes a
confidence score (0-100) indicating how certain the reviewer
is that this is a genuine issue:
| Range | Meaning | Example |
|---|---|---|
| 90-100 | Certain defect | Missing null check on user input |
| 70-89 | Likely issue | Broad exception catch in prod path |
| 50-69 | Possible issue | Style preference, debatable pattern |
| 0-49 | Low confidence | Nitpick, subjective suggestion |
Threshold filtering: In unattended mode, only findings with
confidence >= 70 are passed to Dev10x:review-fix. Below-
threshold findings are reported as INFO in the summary but not
auto-fixed. In attended mode, all findings are presented
regardless of confidence.
The threshold is configurable via session config:
# .claude/Dev10x/session.yaml
review_confidence_threshold: 70 # default
Write findings to a temp file for handoff:
/tmp/Dev10x/bin/mktmp.sh review findings .json
Write the findings array as JSON to the temp file path.
Unattended mode (--unattended):
confidence >= threshold AND
severity ERROR or WARNING to Dev10x:review-fixSkill(skill="Dev10x:review-fix", args="<findings-file-path>")Attended mode (default):
When findings = 0:
REQUIRED: Call AskUserQuestion even when no findings exist.
This confirms the clean review to the user and prevents silent
skip-through (GH-447 F5).
Unattended mode exemption (GH-760 F6): When invoked with
--unattended flag (e.g., from Dev10x:work-on shipping
pipeline), skip this gate and auto-advance. The parent
orchestrator already approved the work plan — pausing for
zero-findings confirmation adds friction without safety value.
Attended mode options:
When findings > 0:
REQUIRED: Call AskUserQuestion (do NOT use plain text).
Options:
Dev10x:review-fixIf "Pick findings": present each finding with fix/skip choice,
collect approved findings, then invoke Dev10x:review-fix.
If "Fix all" or after picking: invoke Dev10x:review-fix with
the findings file path.
Report:
The JSON findings file is the contract between Dev10x:review
and Dev10x:review-fix:
[
{
"severity": "WARNING",
"confidence": 85,
"source": "manual",
"file": "src/auth/middleware.py",
"line": 42,
"description": "Missing type annotation on return value",
"suggested_fix": "def validate(self, token: str) -> bool:",
"category": "style"
}
]
Both skills must agree on this format. The fixer reads the file path passed as its argument.
work-on shipping pipeline
└─ Dev10x:review ← this skill (reviewer)
└─ Dev10x:review-fix ← fixer (consumes findings)
└─ git commit fixup! ← one fixup commit per finding
Complements:
Dev10x:gh-pr-review — posts findings to GitHub (remote PRs)Dev10x:gh-pr-respond — responds to PR review comments