rye-import-inspector

Validate Rye import and update runs for traceability compliance before and after target writes.

2|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/BLTGV/project-rye --skill rye-import-inspector
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rye-import-inspector
Source: https://github.com/BLTGV/project-rye/tree/main/skills/rye-import-inspector
Command: npx skills add https://github.com/BLTGV/project-rye --skill rye-import-inspector

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill eliminates the risk of incomplete or non-compliant Rye import and update runs by providing deterministic validation of all required traceability evidence before and after target writes, preventing unapproved or untraceable data changes from being committed.

Core Features & Use Cases

  • Pre-write validation: Checks source rows, mapped records, change plans, approval metadata, and Rye audit evidence to catch blockers before any target writes occur.
  • Post-write verification: Confirms touched IDs, readback results, and count consistency after writes to ensure the run completed as expected.
  • Flexible workflow support: Works with both standard tabular mapped record imports and source-context intake workflows, with specialized post-write gates for source-context use cases.
  • Use Case: A team running a monthly customer data update can use this skill to verify all old values are preserved, required approvals are present, and post-write record counts match source expectations before marking the run as complete.

Quick Start

Use the rye-import-inspector skill to run a pre-write validation check on your latest import run's source, mapped, and change-plan files, then address any blocker findings before proceeding with target writes.

Frequently Asked Questions about rye-import-inspector

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

FAQPage Schema
How do I validate Rye import traceability before writing data?

To validate Rye import traceability before writing data, run a pre-write validation check on source rows, mapped records, change plans, and approval metadata. This catches compliance blockers and ensures all required audit evidence is present before any target writes occur.

What is post-write verification for data ingestion workflows?

Post-write verification confirms data ingestion workflows completed correctly by checking touched IDs, readback results, and count consistency after writes. This ensures the run finished as expected and maintains compliance after target records are committed.

How do I enforce old value preservation during a data update run?

You enforce old value preservation during a data update run by applying deterministic validation rules to your change plans and mapped records. This verifies that original values are retained and required approvals are present before marking the run complete.

Can I use import validation for source-context intake workflows?

Yes, import validation works with both standard tabular mapped record imports and source-context intake workflows. It applies specialized post-write gates to verify touched IDs and readback results for source-context use cases.

What does an import compliance check verify in a Rye tracked run?

An import compliance check verifies Rye audit record inclusion, review status resolution, and touched ID tracking. It validates traceability of source rows and mapped records to prevent unapproved or untraceable data changes from being committed.