conferre

Name: conferre
Availability: InStock
Author: watministrator

Identify divergences between specifications and live code with file:line citations.

Updated May 20, 2026

Search Tags:#code-review #fidelity #spec-implementation #divergence #software-audit #contract-check #live-tree

Ready to run

npx skills add https://github.com/watmin/datamancy.dev --skill conferre

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: conferre
Source: https://github.com/watmin/datamancy.dev/tree/main/conferre
Command: npx skills add https://github.com/watmin/datamancy.dev --skill conferre

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conferre checks fidelity between the spec and the code, surfacing divergences so practitioners can align the contract.

Core Features & Use Cases

Spec-vs-code fidelity: validate that functions and contracts in the codebase match the design/spec.
Divergence reporting: identify where names, signatures, or invariants differ and explain which side is authoritative.
Live-tree validation: require the current branch and living code, with line-cited evidence to guide fixes.

Quick Start

Run a fidelity audit to compare the current spec with the live code in your active working tree and surface divergences.

Frequently Asked Questions about conferre

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

FAQPage Schema

How do I check spec implementation fidelity against my live code?▼

To check spec implementation fidelity, run a software audit that compares the specification against the live code in your active working tree to surface divergences between function names, signatures, and contracts.

What is spec-vs-code divergence reporting?▼

Spec-vs-code divergence reporting identifies where function names, signatures, or invariants differ between a design specification and its implementation, explaining which side is authoritative to help align the contract.

How do I enforce contract checks during a code review?▼

You enforce contract checks during a code review by applying a fidelity audit to the current branch, analyzing exact file:line locations to validate that the living code matches external specs.

Does spec implementation validation work without a live working tree?▼

No, spec implementation validation requires the current branch and living code in the live tree to perform a software audit and cite exact file:line evidence for each divergence finding.

What is the best way to surface divergences between design specs and code?▼

The best way to surface divergences is to run a fidelity audit that analyzes function names, signatures, contracts, and comments, citing exact file:line locations to guide fixes during design validations.

When should I not use a live-tree divergence audit?▼

Avoid using a live-tree divergence audit when external specs do not need strict alignment with the live code in your current branch, or when you cannot provide the living code required for line-cited evidence.