skills.rest
Refinex-Space
Refinex-SpaceCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

harness-review

Identify and document findings on code diffs and review feedback.

Updated Aug 23, 2026
Search Tags:#workflow#verification#review#diff#code#pull-request
One-click install
npx skills add https://github.com/Refinex-Space/Refinex-Skills --skill harness-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: harness-review
Source: https://github.com/Refinex-Space/Refinex-Skills/tree/main/plugins/harness-powers/skills/harness-review
Command: npx skills add https://github.com/Refinex-Space/Refinex-Skills --skill harness-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Reviewers need a disciplined, findings-first approach to assess code changes, plan outputs, and review feedback, ensuring issues are captured and addressed before verification.

Core Features & Use Cases

  • Findings-first review workflow: surface issues early, document evidence, and prioritize fixes by severity.
  • Structured feedback handling: manage review comments, track resolutions, and prepare for harness-verify handoff.
  • Evidence-backed verification: align reviews with acceptance criteria and plan tasks for reliable closure.
  • Use cases include PR reviews, diff evaluation, and delegated code reviews across software projects.

Quick Start

Supply the current diff or PR context to trigger a findings-first review workflow.

Frequently Asked Questions about harness-review

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

FAQPage Schema
How do I enforce a findings-first approach for pull request reviews?▼

A findings-first review workflow surfaces issues early by documenting evidence and prioritizing fixes by severity. You trigger this by supplying the current code diff or PR context, ensuring issues are captured before verification.

What is the best way to document code review findings with severity-based triage?▼

Documenting code review findings with severity-based triage involves identifying issues on code diffs, collecting supporting evidence, and preparing structured handoffs. This aligns reviews with acceptance criteria and plan tasks for reliable closure.

Can I use this workflow to evaluate active Harness plan outputs and delegated review comments?▼

Yes, you can apply the findings-first review workflow to active Harness plan outputs and delegated review comments. It manages feedback, tracks resolutions, and structures handoffs across software projects for verification.

How do I track and manage resolutions for structured review feedback?▼

To track and manage resolutions for structured review feedback, the workflow handles review comments and prepares them for handoff. This ensures all documented findings are addressed and aligned with plan tasks before verification.

Does code review coordination work without additional verification dependencies?▼

Code review coordination works independently to document findings but prepares structured handoffs for harness-verify. It enforces the findings-first workflow with evidence collection and severity-based triage to ensure reliable closure.

Related Skills

Explore More Software Engineering Skills→
dynatrace-ossdynatrace-oss
10

pr-reviewer

Review pull request diffs and comments to generate a structured review brief.

Official
Intermediate
truongnattruongnat
1

feedback-pro

Generate evidence-based feedback reports with severity ratings and closure plans.

Community
Advanced
srnicholssrnichols
5

bug-fix

Coordinate Plan Forge tools to fix bugs with tests and validation.

Community
Intermediate
JeremyDev87JeremyDev87
31

receiving-code-review

Classify code review feedback into Must-Fix, Evaluate, or Preference with evidence.

Community
Advanced