conductor-validate-review
Validate a code review document against the repository, finding by finding, before it becomes a Conductor remediation programme. Use when the user asks to validate a review in conductor/reviews/.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-05
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- conductor-validate-review
- description
- Validate a code review document against the repository, finding by finding, before it becomes a Conductor remediation programme. Use when the user asks to validate a review in conductor/reviews/.
03 SKILL.md 正文
Follow ${CLAUDE_PLUGIN_ROOT}/templates/conductor-protocol.md for file resolution, git policy, and output style.
Conductor Validate Review
Claude Tool Mapping
- User Prompt Protocol for structured user prompts (AskUserQuestion tool when available, else numbered options in chat; wait for reply)
- Read / Write / Edit for file operations
- Bash for shell commands
- Grep / Glob for search
- Use relative paths under
conductor/for all Conductor artifacts
Output Style
Follow Agent Output Style in templates/conductor-protocol.md. Line 1 = validation status and count of findings checked.
Plugin Template Path
Locate installed plugin templates:
${CLAUDE_PLUGIN_ROOT}/templates/- Fallback (local dev):
./plugins/conductor/templates/from claudekit repo root - Fallback:
./plugins/conductor/templates/from repo root
1.0 SYSTEM DIRECTIVE
Validate a review document in Reviews Directory against the codebase. Produce a validation addendum before /conductor:conductor-new-track programme creation.
Read-only until writing validation output. Git write operations follow Git Write Policy.
2.0 VALIDATION PROTOCOL
2.1 Resolve review
- If
{{args}}is non-empty, use as review path (relative to repo root or underconductor/reviews/). - Otherwise User Prompt Protocol — header "Review path", type text, placeholder
conductor/reviews/foo_YYYYMMDD-review.md. - Verify file exists via Universal File Resolution.
2.2 Extract findings
Parse review for:
- Location: lines with file paths and line numbers
- Severity claims (Critical, High, ARCH-N, §X.Y)
- Inline backtick paths in finding bodies
Load templates/review-document-header.md for expected structure.
2.3 Verify paths
- Run
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/conductor_state.py" verify-paths <review path>(Deterministic Plumbing Protocol). It checks every cited path andfile:linereference and suggests corrections for missing files. - For paths marked
verifiedwith a line ref,Readthe cited lines to confirm the symbol/context still matches the claim. - Record: Verified | Wrong path (use the script's
suggestions) | Not found - Fallback without
python3:test -f/test -d, glob variants, andReadfor line refs.
2.4 Verify severity claims
For each finding with code citation:
- Read cited code
- Mark: Confirmed | Partially confirmed | Disputed | Obsolete
- Drop claims you cannot validate — do not flag uncertain items
2.5 Write validation addendum
Default: sibling file <review-stem>_validation.md (preserves original review).
User Prompt Protocol if user prefers append to review instead.
Addendum structure:
# Validation — <review title>
**Source:** `conductor/reviews/<file>`
**Validated:** YYYY-MM-DD
## Path verification
| Finding | Cited path | Status | Correction |
| ------- | ---------- | ------ | ---------- |
## Severity confirmation
| ID | Verdict | Notes |
| -- | ------- | ----- |
## Blocking issues
List wrong paths or disputed Critical findings that must resolve before programme creation.
## Programme readiness
**Ready** | **Not ready** — <reason>
2.6 Halt rules
- Blocking wrong paths on Critical findings → announce halt; programme creation blocked until fixed
- User may opt out via the User Prompt Protocol when running
/conductor:conductor-new-track(document opt-out in programme metadata)
2.7 Completion
Announce: "Validation written to <path>. Next: /conductor:conductor-new-track from this review."
04 同仓库更多 Skills
research
Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.
prototype
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
improve-codebase-architecture
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
grilling
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
grill-with-docs
A relentless interview to sharpen a plan or design, which also creates OKF repo knowledge as we go.
domain-modeling
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing the glossary (conductor/context/product.md or a GLOSSARY.md), or recording or editing a decision concept.