import-mapping-review-gate

Enforce explicit column mapping and material creation before committing data imports.

Updated Mar 16, 2026

Search Tags:#validation #preview #mapping #gate #import #data-quality #material-remap

Ready to run

npx skills add https://github.com/BSchafer01/PanelNester --skill import-mapping-review-gate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: import-mapping-review-gate
Source: https://github.com/BSchafer01/PanelNester/tree/main/.squad/skills/import-mapping-review-gate
Command: npx skills add https://github.com/BSchafer01/PanelNester --skill import-mapping-review-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This pattern provides a gated import workflow where column mappings can be reviewed, unknown materials resolved, and new library materials created only after explicit validation.

Core Features & Use Cases

Separate the obvious-default path from the rescue-mapping path to keep imports fast when unambiguous.
Require a preview-before-commit contract to auto-resolve or explicitly map all required fields and materials.
Treat material resolution as canonicalization, avoiding silent remapping or fuzzy-matching behind the user.
Treat create-new-material as a real library mutation, making new materials immediately available and persisted.
Keep failure surfaces distinct (file errors, mapping gaps, unresolved materials, and create failures) and prevent final import until all required mappings are resolved.

Quick Start

Preview and map source columns before committing an import to ensure all required fields and materials are resolved.

Frequently Asked Questions about import-mapping-review-gate

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

FAQPage Schema

How do I safely preview and map ambiguous CSV columns before committing a data import?▼

To safely preview data imports, you can enforce a preview-before-commit contract that requires all required fields and materials to be explicitly mapped or auto-resolved before the final import is allowed to execute.

What is the best way to handle unknown materials during a file import without silent remapping?▼

Handling unknown materials during import requires treating material resolution as canonicalization, avoiding silent fuzzy-matching behind the user, and allowing on-the-fly creation only after explicit validation.

Why does my data import fail when source headers are ambiguous?▼

Data imports fail when source headers are ambiguous because gated workflows keep failure surfaces distinct, preventing the final import until all required mappings are explicitly resolved by the user.

Can I create new library materials on-the-fly during a gated import workflow?▼

Yes, you can create new library materials during an import by treating the creation as a real library mutation, making the new materials immediately available and persisted only after explicit validation.

Does this data import workflow require separate handling for mapping gaps and file errors?▼

Yes, this data import workflow requires keeping failure surfaces distinct, separating file errors, mapping gaps, unresolved materials, and create failures to prevent final import until all issues are resolved.

How do I separate obvious default mappings from rescue mappings in data imports?▼

Separating obvious default mappings from rescue mappings in data imports keeps workflows fast when source headers are unambiguous, routing only ambiguous headers to the user-driven rescue-mapping path.