shamt-import

Automate post-import validation for Shamt projects after running import.sh.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/MizunoPK/shamt-ai-dev --skill shamt-import
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shamt-import
Source: https://github.com/MizunoPK/shamt-ai-dev/tree/main/.claude/skills/shamt-import
Command: npx skills add https://github.com/MizunoPK/shamt-ai-dev --skill shamt-import

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-import validation is automated to ensure the integrity of master-child synchronization after an import. It checks for diffs, aligns supplements and pointers, handles new/deleted files, and ensures a clean commit only after verification.

Core Features & Use Cases

  • Automates reading and interpreting import diffs produced during master sync.
  • Validates project-specific supplements and pointers for consistency.
  • Supports a comprehensive validation loop with optional sub-agents and a final commit step.

Quick Start

Use after running import.sh to trigger the post-import validation workflow and ensure changes are aligned before committing.

Frequently Asked Questions about shamt-import

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

FAQPage Schema
How do I validate post-import diffs for master-child syncs?

To validate post-import diffs for master-child syncs, apply this Skill after running import.sh to automatically read diffs, check supplements, validate pointers, and ensure changes are aligned before committing.

What is the best way to automate post-import validation workflows?

The best way to automate post-import validation workflows is by triggering a multi-step protocol that enforces diff reading, supplement checks, pointer validation, and a final commit step after verification.

Why does my master-child synchronization have broken pointers after an import?

Broken pointers after an import occur when synchronization validation is skipped. Applying a post-import validation protocol aligns supplements and validates pointers to restore consistency across master-child syncs.

When do I need to run post-import validation for new and deleted files?

You need to run post-import validation for new and deleted files immediately after executing import.sh, ensuring that diff file handling and RULES_FILE updates are correctly processed before committing changes.

Can I use sub-agents during the import diff validation loop?

Yes, you can use optional sub-agents during the import diff validation loop. The post-import validation process supports a comprehensive validation loop with sub-agents to verify supplements and pointers before the final commit.

Does post-import validation enforce a commit only after verifying supplements and pointers?

Yes, post-import validation enforces a clean commit only after verifying that supplements, pointers, and new-file handling are fully aligned, ensuring the integrity of master-child synchronization.