skills.rest
maxwell2732
maxwell2732COMMUNITY
Explore all skills by this author →
Website𝕏@ChenZhu_CAUGitHub

harness-review

Evaluate code, plan, and scope changes against governance with verified evidence.

39|46|Updated May 29, 2026
Search Tags:#governance#evidence#review#traceability#plans#scope#code
One-click install
npx skills add https://github.com/maxwell2732/claudecode-research-harness-workflow --skill harness-review-maxwell2732
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: harness-review
Source: https://github.com/maxwell2732/claudecode-research-harness-workflow/tree/main/skills/harness-review
Command: npx skills add https://github.com/maxwell2732/claudecode-research-harness-workflow --skill harness-review-maxwell2732

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Integrated Harness review provides a controlled, read-only workflow to evaluate code changes, plans, and scope with a focus on security, quality, and traceability before acceptance.

Core Features & Use Cases

  • Dispatcher: a lightweight front-end that routes review tasks to the appropriate references and assets.
  • Multi-mode review: supports code, plan, scope, and governance checks with evidence collection.
  • Evidence-driven verdicts: ensures spec alignment, Plan DoD, regression safety, and traceability before approvals.

Quick Start

Trigger a harness-review to assess code, plan, and scope against governance before acceptance.

Frequently Asked Questions about harness-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify code changes against spec and governance before approval?▼

Code review against spec and governance requires identifying diffs and collecting verified evidence to evaluate changes, enforcing no-script, no-log, and no-claim discipline before acceptance.

What is evidence-driven plan review and how does it enforce traceability?▼

Evidence-driven plan review collects verified artifacts to evaluate changes against Plans.md, ensuring spec alignment, Plan DoD, regression safety, and traceability before issuing approvals.

Can I run scope and governance reviews without writing custom scripts?▼

Scope and governance reviews operate under a strict no-script, no-log, no-claim discipline, routing tasks to appropriate references and assets while requiring verified evidence before approving changes.

How do I review code diffs to ensure compliance with project governance?▼

Reviewing code diffs for governance compliance involves identifying the changes, loading relevant references and assets, and collecting verified evidence to enforce spec alignment and regression safety.

What's the best way to approach end-to-end code and plan review?▼

The best way to approach end-to-end code and plan review is triggering a multi-mode assessment that evaluates code, plans, and scope against governance using a lightweight dispatcher for evidence collection.

Why does evidence collection matter for traceability in code review?▼

Evidence collection matters for traceability because it requires verified proof of spec alignment, Plan DoD, and regression safety before any changes are approved, preventing unverified claims.

Related Skills

Explore More Software Engineering Skills→
PriNovaPriNova
80

arch-code-review

Validate architectural diffs against canonical YAML artifacts for consistency and governance.

Community
Advanced
simotasimota
68

Attest

Extract acceptance criteria and generate BDD scenarios for compliance verification.

Community
Advanced
tachyon-beeptachyon-beep
14

using-technical-writer

Route documentation tasks to the appropriate technical-writing skill by document type and audience.

Community
Advanced
OrestesKOrestesK
2

review

Evaluate code and plans against approved requirements with categorized findings.

Community
Advanced