One-click install
npx skills add https://github.com/softwaresalt/csv-managed --skill shipment-reconcile
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shipment-reconcile
Source: https://github.com/softwaresalt/csv-managed/tree/main/.github/skills/shipment-reconcile
Command: npx skills add https://github.com/softwaresalt/csv-managed --skill shipment-reconcile

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents shipment manifest drift by reconciling every declared manifest item against the queue (pre-mode) and the archive (post-mode) before and after the shipment run, so operators can stop early when the dataset state is inconsistent.

Core Features & Use Cases

  • GI/GR reconciliation gate: Verifies each manifest item exists where expected, including status correctness in pre-mode.
  • Deterministic report-and-halt behavior: Produces a reconciliation report and blocks progression when any missing, status mismatch, or orphan items are detected.
  • Single-writer lock integration: Acquires and holds the shipment queue lock across pre-mode through post-mode to avoid concurrent session conflicts.
  • Operator-focused failure modes: Recommends PROCEED or HALT with a clear report path and enforces “never mutate manifests/archives” in v1.

Quick Start

Use the shipment-reconcile skill with mode: pre, then run backlogit_ship_shipment, and finally rerun shipment-reconcile with mode: post to ensure archives and manifest items reconcile correctly.

Frequently Asked Questions about shipment-reconcile

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

FAQPage Schema
How do I verify shipment manifest integrity against queue and archive states?

To prevent shipment manifest drift, reconcile every declared manifest item against the queue (pre-mode) and the archive (post-mode) before and after the shipment run, stopping early when dataset state is inconsistent.

When do I need to apply pre-mode and post-mode reconciliation gating?

Pre-mode and post-mode reconciliation gating is required when workflows must validate that each manifest entry exists with an expected status before the shipment and exists in the archive after the archive and restore sequence completes.

What happens when a manifest reconciliation detects a missing or orphaned item?

When missing, status mismatch, or orphan items are detected, the workflow enforces deterministic report-and-halt behavior that blocks progression and outputs a RECONCILE_FAIL signal to stop the operation immediately.

How does single-writer lock integration work during shipment reconciliation?

Single-writer lock integration acquires and holds the shipment queue lock across pre-mode through post-mode scanning, preventing concurrent session conflicts and maintaining data consistency throughout the reconciliation process.

How do I classify matched, pre-archived, missing, and orphan items during manifest reconciliation?

Matched, pre-archived, missing, status-mismatch, and orphan items are classified using mode-dependent logic during pre-mode and post-mode scanning, with results written to a reconciliation report at .backlogit/reconcile.

Does shipment reconciliation allow mutating manifests or archives to fix mismatches?

No, shipment reconciliation enforces a strict never mutate manifests or archives policy in v1, meaning operators must manually resolve any detected drift or data integrity issues outside of the reconciliation workflow.