parity-check

Audit hoard parity between pi and CC capabilities to identify drift.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/dotBeeps/hoard --skill parity-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: parity-check
Source: https://github.com/dotBeeps/hoard/tree/main/cc-plugin/skills/parity-check
Command: npx skills add https://github.com/dotBeeps/hoard --skill parity-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit and verify that the hoard's pi capabilities are in sync with the CC side, ensuring each artifact has a matching counterpart and preventing drift when morsels, cc-plugin skills/agents, or berrygems extensions change.

Core Features & Use Cases

  • Compares on-disk artifacts against the central parity map at .claude/parity-map.json.
  • Detects unregistered artifacts and stale map entries, aiding clean maintenance.
  • Supports full audits when adding or removing components or when drift is reported by hooks.

Quick Start

Run the parity audit to identify drift and generate a remediation plan.

Frequently Asked Questions about parity-check

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

FAQPage Schema
How do I audit parity drift between pi and CC capabilities?

Audit parity drift by loading the central parity map, enumerating on-disk artifacts, and checking for unregistered entries or stale map references. This validates cross-references without modifying the repository.

What is an artifact parity check for hoard maintenance?

An artifact parity check verifies that hoard pi capabilities match CC counterparts, ensuring each artifact has a registered entry and preventing drift when morsels, cc-plugin skills, or berrygems extensions change.

When should I run a parity audit on my artifacts?

Run a parity audit when adding or removing morsels, cc-plugin skills, agents, or berrygems extensions, or when the stop-parity-check hook reports drift between your pi and CC capabilities.

Does the parity audit modify repository files during validation?

No, the parity audit does not modify repository files. It loads the parity map, validates cross-references, and identifies unregistered artifacts and stale entries to generate a remediation plan.

How do I detect unregistered artifacts and stale map entries?

Detect unregistered artifacts and stale map entries by comparing on-disk artifacts against the central parity map at .claude/parity-map.json, which highlights items lacking matching counterparts.

Can I use this parity check with berrygems extensions and morsels?

Yes, apply this parity check during changes to morsels, cc-plugin skills, agents, or berrygems extensions to verify that pi capabilities remain synchronized with CC capabilities.