chain-verifier

Verify git working tree diffs against initial requirements.

15|6|Updated May 7, 2026
One-click install
npx skills add https://github.com/MinhThang1009/dotclaude --skill chain-verifier
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chain-verifier
Source: https://github.com/MinhThang1009/dotclaude/tree/main/plugins/subagent-system/skills/chain-verifier
Command: npx skills add https://github.com/MinhThang1009/dotclaude --skill chain-verifier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit and confirm that the current git working tree matches the original requirements after a chain of fix agents and reviews.

Core Features & Use Cases

  • End-to-end verification ensures the final state aligns with the initial requirements.
  • Git-aware diffing detects deviations and missing changes in the working tree.
  • Safe, fail-fast operation gracefully handles non-git repos or missing checkpoints and reports actionable results.

Quick Start

Run chain-verifier after the final fixes to confirm the working tree satisfies the initial requirements.

Frequently Asked Questions about chain-verifier

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

FAQPage Schema
How do I verify my git working tree matches the original requirements after pipeline changes?

To verify your git working tree matches original requirements, run chain-verifier after final pipeline fixes. It reads the start commit, computes diffs against the working tree, and reports discrepancies to confirm the final state aligns with initial requirements.

What is the best way to audit multi-phase pipeline outputs against an initial git commit?

The best way to audit multi-phase pipeline outputs is using a git-aware verification tool that computes diffs between the start commit and the current working tree, detecting deviations and missing changes to ensure end-to-end consistency.

Can I check final pipeline state consistency in a non-git repository?

Checking final pipeline state consistency in a non-git repository triggers a fail-fast operation. The verification gracefully handles missing checkpoints or non-git environments, reporting actionable results instead of crashing during the audit.

How do I validate that automated code fixes haven't introduced unintended deviations?

To validate automated code fixes haven't introduced unintended deviations, run a git diff verification against the start commit. This identifies any discrepancies between the initial requirements and the final working tree state after fixes.

When should I run a working tree verification check in my CI pipeline?

Run a working tree verification check after multi-phase pipelines, pipeline reviews, or when a user asks to validate outputs. This ensures the final working tree state satisfies the initial requirements before merging or deployment.