harness

Run make targets and spawn fix sub-agents for quality checks.

Updated Mar 4, 2026
One-click install
npx skills add https://github.com/multicam/ikigai-rev --skill harness-multicam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness
Source: https://github.com/multicam/ikigai-rev/tree/main/.claude-i/library/harness
Command: npx skills add https://github.com/multicam/ikigai-rev --skill harness-multicam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automated fix loops. Each harness runs a make target, spawns sub-agents to fix failures, commits on success, reverts on exhaustion.

Pattern: .claude/harness/<name>/run + fix.prompt.md

Escalation: sonnet:think → opus:think → opus:ultrathink

History: Each harness maintains history.md for cross-attempt learning. Truncated per-file, accumulates across escalation. Agents append summaries after each attempt so higher-level models can avoid repeating failed approaches.

Core Features & Use Cases

The Harness supports running structured quality checks, linking to fix scripts, and maintaining a centralized history to guide future attempts.

Quick Start

Run a harness to execute quality checks and spawn fix sub-agents automatically.

Frequently Asked Questions about harness

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

FAQPage Schema
How do I automate software quality checks with fix sub-agents?

You automate quality checks by running a harness that executes a make target and spawns fix sub-agents to address failures, committing on success and reverting on exhaustion.

How does escalation work when automated fix loops fail?

Escalation progresses from sonnet:think to opus:think to opus:ultrathink, allowing higher-level models to leverage historical learning from history.md to avoid repeating failed approaches.

What is the pattern for structuring quality check pipelines and fix scripts?

The pattern uses .claude/harness/<name>/run paired with fix.prompt.md to enable reproducible quality gates by linking structured command patterns with versioned run scripts.

Can I use this automated fix loop for projects requiring structured check pipelines?

Yes, it applies directly to software projects requiring structured check pipelines, escalation pathways, and historical learning, satisfying metadata frontmatter and versioned run scripts for reproducible quality gates.

How do sub-agents learn from previous failed quality check attempts?

Each harness maintains a truncated per-file history.md for cross-attempt learning, where agents append summaries after each attempt so higher-level escalation models avoid repeating failed approaches.