harness-code-review

Automate multi-phase code review with mechanical checks and graph-scoped context.

18|11|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/Intense-Visions/harness-engineering --skill harness-code-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-code-review
Source: https://github.com/Intense-Visions/harness-engineering/tree/main/agents/skills/claude-code/harness-code-review
Command: npx skills add https://github.com/Intense-Visions/harness-engineering --skill harness-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review is time-consuming and error-prone when done manually. Harness Code Review provides a mechanical, graph-aware pipeline that enforces architectural constraints while accelerating feedback.

Core Features & Use Cases

  • Mechanical checks: Linting, type checks, tests, and security scans run automatically as part of the review pipeline.
  • Graph-scoped context: Context bundles are scoped per domain to keep reviews focused and efficient.
  • Parallel subagents: Compliance, bug detection, security, and architecture findings are produced in parallel and deduplicated.
  • Evidence-rich output: Findings include evidence citations, justification, and remediation suggestions.
  • Handoff-ready: Outputs structured for inline comments, PR reviews, and CI handoffs.

Quick Start

Review a pull request with Harness Code Review to produce a structured assessment report.

Frequently Asked Questions about harness-code-review

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

FAQPage Schema
How do I automate pull request code reviews for security and architecture compliance?

Automated code review uses mechanical checks and graph-scoped context to evaluate pull requests. It coordinates parallel subagents for compliance, bug detection, security, and architecture to produce a unified, deduplicated findings report.

What is graph-scoped context in multi-phase code review?

Graph-scoped context in code review bundles context per domain to keep reviews focused. This mechanism ensures that automated findings are evaluated against the relevant architectural constraints and dependencies, reducing manual effort and errors.

How do I deduplicate findings from security scans and bug detection in PR reviews?

Deduplicate findings from security scans and bug detection by running parallel subagents that cross-reference mechanical checks. The pipeline filters overlapping results against evidence-based findings to produce a unified report.

Can I use automated code review for CI handoffs and inline PR comments?

Automated code review outputs structured findings designed for CI handoffs and inline PR comments. The evidence-rich output includes justification citations and remediation suggestions formatted for direct integration into review workflows.

Does automated code review work with linting, type checks, and threat modeling?

Automated code review integrates mechanical checks like linting, type checks, and tests alongside security scans. It also supports optional threat modeling for deeper analysis, coordinating these phases to enforce architectural constraints.

What are the limitations of automated multi-phase code review pipelines?

Automated multi-phase code review relies on graph-scoped context bundles, meaning review focus depends on domain scoping accuracy. While it deduplicates mechanical scans, optional threat modeling requires deeper analysis beyond standard automated validation.