improve-harness

Run a structured incident-to-fix workflow for harness friction issues.

3|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/crypdick/obsidian-knowledge --skill improve-harness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: improve-harness
Source: https://github.com/crypdick/obsidian-knowledge/tree/main/plugins/obsidian-knowledge/skills/improve-harness
Command: npx skills add https://github.com/crypdick/obsidian-knowledge --skill improve-harness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

improve-harness helps recover when the Claude Code “harness” gets in the way of effective work, repeatedly blocking the user due to friction in repo behavior, hooks, or skill logic.

Core Features & Use Cases

  • Incident-to-fix workflow: Captures a blameless incident report, then turns it into a proposal and implementation with structured review phases.
  • Headless side-quest execution: Runs a controlled, budget-capped headless process to draft and implement the fix.
  • Safe branching and human approval: Never merges automatically; it leaves changes on an improve/<slug> branch and prompts for review and plugin reload.

Quick Start

Use improve-harness when the harness blocks you by saying: /improve-harness the harness just blocked me again, it was hard to complete the protect-vault workflow.

Frequently Asked Questions about improve-harness

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

FAQPage Schema
How do I fix Claude Code harness friction blocking my repo workflow?

To fix Claude Code harness friction, trigger an incident-to-fix workflow that captures a blameless incident report and converts it into a structured, phased implementation proposal on an isolated branch for your review.

What is a blameless incident report for code review automation?

A blameless incident report is a structured capture of repeated harness friction or blocking behavior, used as the starting point to draft and implement a fix proposal through a controlled, headless side-quest process.

Can I automate multi-file behavior changes for Obsidian plugin repo issues?

Yes, you can automate non-trivial multi-file behavior changes for global plugin-repo issues by running a budget-capped, headless process that drafts and implements fixes on an isolated worktree before requesting user approval.

How do I safely branch and review harness convention fixes?

To safely branch and review harness fixes, the workflow records state per slug on an improve/<slug> branch using isolated worktrees, enforces iteration caps, and never merges automatically without user approval and plugin reload.

Does the improve-harness workflow merge changes automatically?

No, the improve-harness workflow never merges automatically; it leaves all drafted changes on an improve/<slug> branch and prompts for explicit user approval before deploying via the deploy-harness skill.

What are the limitations of running headless side-quests for incident response?

Limitations include strict iteration caps and budget limits on the headless process, meaning complex or multi-file behavior changes may require multiple controlled runs and cannot exceed the defined execution budget.