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

harness-fix

Diagnose and repair broken behavior in a Harness Powers control plane.

Updated Aug 27, 2026
Search Tags:#debugging#verification#diagnose#root-cause#reproduction#fix-plan#harness-powers
One-click install
npx skills add https://github.com/Refinex-Space/Refinex-Skills --skill harness-fix
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: harness-fix
Source: https://github.com/Refinex-Space/Refinex-Skills/tree/main/plugins/harness-powers/skills/harness-fix
Command: npx skills add https://github.com/Refinex-Space/Refinex-Skills --skill harness-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Diagnose and repair broken behavior inside a Harness Powers control plane, serving as the lifecycle owner for bugs, regressions, incidents, build failures, and flaky paths.

Core Features & Use Cases

  • Preflight: read project context, gather evidence, and prepare an actionable bug brief.
  • Reproduction & Root-Cause Isolation: craft reproducible scenarios and apply hypothesis-driven debugging.
  • Minimal Fix & Verification: implement smallest change with regression protection and archival rationale.
  • Archive and Handoff: move completed plans to docs/PLANS, summon harness-verify, and communicate results to stakeholders.

Quick Start

Create a Bug Brief with symptom details and reproduction steps, then generate an active fix plan and start reproduction and root-cause isolation.

Frequently Asked Questions about harness-fix

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

FAQPage Schema
How do I diagnose and fix a build failure or regression in a Harness Powers control plane?▼

To diagnose and fix a build failure or regression in a Harness Powers control plane, you gather evidence during preflight, create a bug brief, reproduce the scenario, isolate the root cause, apply a minimal fix, and verify the changes.

What is the best way to reproduce flaky-path scenarios and isolate the root cause?▼

The best way to reproduce flaky-path scenarios and isolate the root cause is to craft reproducible scenarios from a bug brief and apply hypothesis-driven debugging to pinpoint the exact failure mechanism.

How do I create an actionable bug brief for incident reproduction?▼

You create an actionable bug brief for incident reproduction by reading project context, gathering initial evidence, and documenting symptom details with specific reproduction steps to guide root-cause isolation.

Does this debugging workflow support minimal fixes with regression protection?▼

Yes, this debugging workflow supports minimal fixes with regression protection by enforcing a stepwise process that implements the smallest possible change and verifies it before archival handoff.

What is the proper handoff process after verifying a bug fix plan?▼

The proper handoff process after verifying a bug fix plan involves moving completed plans to docs/PLANS, summoning harness-verify for archival rationale, and communicating results to stakeholders.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

debug-issue

Diagnose bugs by tracing evidence and generating a BR issue template.

Community
Advanced
ArvorCoArvorCo
96

plan

Convert feature specifications into implementation plans with TDD and governance requirements.

Community
Advanced
alexsandrocruzalexsandrocruz
6

verification-before-completion

Require fresh verification evidence before claiming completion in software workflows.

Community
Basic
JuanMS20JuanMS20
1

diagnose

Guide developers through structured diagnosis of hard bugs and performance regressions.

Community
Advanced