coherence-audit

Automate cross-layer coherence checks after merges to detect DRY violations, architecture drift, and security gaps.

3|Updated Mar 25, 2026

Search Tags:#architecture #qa #audit #code-quality #coherence #coherence-report

Ready to run

npx skills add https://github.com/willietran/autoboard --skill coherence-audit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: coherence-audit
Source: https://github.com/willietran/autoboard/tree/main/skills/coherence-audit
Command: npx skills add https://github.com/willietran/autoboard --skill coherence-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run a coherence audit after every layer's merges. This catches cross-session AND cross-codebase quality issues (DRY violations, orphaned code, convention drift, security gaps) before they compound.

Core Features & Use Cases

Automatically run a multi-layer coherence check after merges to ensure shared quality standards.
Flag DRY violations, architecture drift, and security gaps; enforce QA gate and knowledge curation with COHERENCE-REPORT.
Use in multi-layer feature development to prevent cross-layer defects from propagating.

Quick Start

Run the coherence audit at a checkpoint by invoking /autoboard:audit with your current CHECKPOINT.

Frequently Asked Questions about coherence-audit

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

FAQPage Schema

How do I automate cross-layer coherence checks after code merges?▼

Automate cross-layer coherence checks by running an audit at your checkpoint to detect cross-session quality issues like DRY violations and architecture drift before they compound.

What is a coherence audit in multi-layer development workflows?▼

A coherence audit is a cross-session quality check that catches cross-codebase issues such as orphaned code, convention drift, and security gaps after merges to prevent cross-layer defect propagation.

When do I need to run a cross-codebase quality check for architecture drift?▼

Run a cross-codebase quality check after every layer's merges to catch architecture drift, DRY violations, and security gaps early before parallel development sessions fall out of alignment.

How do I enforce QA gates and trigger COHERENCE-REPORT processing?▼

Enforce QA gates and trigger COHERENCE-REPORT processing by invoking an audit at your current checkpoint, which flags quality issues and coordinates with the coherence-fixer workflow.

Does the coherence audit work with parallel development sessions?▼

Yes, the coherence audit is designed for multi-layer workflows where parallel sessions must stay aligned, detecting cross-session issues like convention drift and orphaned code after merges.

What are the limitations of automated coherence checks for code quality?▼

Automated coherence checks target multi-layer development workflows and require a checkpoint to trigger; they focus on cross-session alignment and may not catch single-session logic errors.