incoherence

Detects documentation-code-specification mismatches and guides interactive resolution workflows via Python script.

42|3|Updated Mar 5, 2021
One-click install
npx skills add https://github.com/fmoda3/nix-configs --skill incoherence-fmoda3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incoherence
Source: https://github.com/fmoda3/nix-configs/tree/main/home/claude-code/config/skills/incoherence
Command: npx skills add https://github.com/fmoda3/nix-configs --skill incoherence-fmoda3

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Detects and resolves incoherence between documentation, code, and specifications vs implementation, reducing confusion and rework.

Core Features & Use Cases

  • Automated detection of mismatches between docs, specs, and code across a codebase.
  • Interactive resolution workflow that guides decisions and changes.
  • Final reporting of discrepancies and applied resolutions in a structured format.

Quick Start

Invoke the workflow script to start detection: <invoke working-dir=".claude/skills/scripts" cmd="python3 -m skills.incoherence.incoherence --step-number 1 --thoughts '<context>'" />

Frequently Asked Questions about incoherence

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

FAQPage Schema
How do I detect mismatches between code and documentation in my codebase?

To detect documentation and code mismatches, this skill runs a Python-based workflow script that scans your codebase to identify incoherence between specifications, docs, and implementation, then generates a structured discrepancy report.

What is the best way to resolve incoherence between software specs and implementation?

Resolving incoherence between specs and implementation is handled through an interactive workflow that guides decision-making and changes step by step, applying structured detection to resolve divergence between documentation and actual code.

Can I use this documentation mismatch detection workflow without installing external dependencies?

You can run this mismatch detection workflow without external dependencies, as it relies solely on a self-contained Python script located in the scripts directory to perform detection, interactive prompts, and final reporting.

Does the interactive resolution workflow support automated code review for documentation drift?

The interactive resolution workflow supports code review for documentation drift by applying automated detection of mismatches across the codebase, then guiding interactive decisions to resolve discrepancies between docs, specs, and code.

What format does the final reporting use when documenting detected code and spec discrepancies?

The final reporting outputs detected discrepancies and applied resolutions in a structured format, summarizing the mismatches found between documentation, code, and specifications during the interactive detection workflow.