coherence-fixer

Dispatch a fixer session to resolve coherence findings across feature layers.

3|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/willietran/autoboard --skill coherence-fixer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coherence-fixer
Source: https://github.com/willietran/autoboard/tree/main/skills/coherence-fixer
Command: npx skills add https://github.com/willietran/autoboard --skill coherence-fixer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dispatch a fixer session agent to address coherence findings that survived orchestrator pre-screening, ensuring consistency across feature layers and preventing drift.

Core Features & Use Cases

  • Spawn a dedicated fixer session and worktree for a feature
  • Ingest COHERENCE-REPORT findings and previous attempts to plan targeted fixes
  • Iterate to fix root causes, re-audit, and merge changes back into the feature branch
  • Support multi-layer retries and progress tracking to avoid stagnation

Quick Start

Run the coherence-fixer to start a dedicated session that loads the full workflow and begins the coherence repair cycle.

Frequently Asked Questions about coherence-fixer

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

FAQPage Schema
How do I fix cross-session coherence issues in my feature branch?

To fix cross-session coherence issues, you dispatch a dedicated fixer session that ingests a COHERENCE-REPORT and iterates through a multi-layer workflow to resolve root causes. It then merges the verified repairs directly back into your feature branch.

What is a session-workflow approach for mending code drift across feature layers?

A session-workflow approach for mending code drift spawns an isolated worktree to run a full cycle: Explore, Plan, Review, Implement, Verify, and Commit. This ensures durable fixes by enforcing root-cause resolution and running automated re-audits before merging.

How do I resolve coherence findings that survived orchestrator pre-screening?

You resolve surviving coherence findings by spawning a dedicated fixer agent that loads previous attempts and briefs to plan targeted fixes. It tracks progress across multiple retries to avoid stagnation and ensure the drift is fully corrected.

Do I need a COHERENCE-REPORT before starting an automated coherence audit repair?

Yes, an automated coherence audit repair requires a COHERENCE-REPORT as input to identify the specific findings. The fixer session ingests this report to plan targeted fixes and validate that the root causes are fully resolved.

What's the best way to prevent stagnation when fixing complex code drift?

The best way to prevent stagnation when fixing complex code drift is to use a multi-layer retry system with dedicated progress tracking. This approach iterates through implementation and verification phases, applying on-demand re-audits until the root cause is resolved.