Export generic guide and script improvements from a child project via PR.
npx skills add https://github.com/MizunoPK/shamt-ai-dev --skill shamt-export
Please help me install this Agent Skill. Skill: shamt-export Source: https://github.com/MizunoPK/shamt-ai-dev/tree/main/.claude/skills/shamt-export Command: npx skills add https://github.com/MizunoPK/shamt-ai-dev --skill shamt-export
Exports generic guide and script improvements from a child project back to the shamt-ai-dev master repo via PR. Covers verifying CHANGES.md, comparing the rules file against RULES_FILE.template.md, scanning for epic tag contamination, running the guide audit, running the export script, and opening a PR.
Run the export workflow to push your shared guide improvements from the child project to the master repository.
High-intent search queries and answers about installing and using this skill.
To export generic script and guide improvements, you run an export workflow that validates CHANGES.md entries, audits for epic-tag contamination, and opens a PR to the master repository. This propagates generic improvements across projects.
Epic-tag contamination occurs when project-specific tags leak into shared guides or scripts. The export workflow scans for these tags before pushing changes to the master repository to ensure only generic, master-wide improvements are exported.
You validate CHANGES.md entries by running the guide audit step within the export workflow, ensuring all modifications to .shamt/guides/ and .shamt/scripts/ are deliberate, documented, and generic before opening the PR.
No, you cannot export project-specific guide modifications. The workflow enforces that only generic, master-wide improvements are exported by checking for epic-tag contamination and auditing changes before running the export script.
Yes, you need to compare rules files. The export workflow includes a step to compare your local rules file against RULES_FILE.template.md to detect template deviations and ensure uniform guide standards before opening a PR.
Your guide audit fails because the export workflow requires an audit pass before running the export script. Failures typically occur when CHANGES.md entries are undocumented or when epic-tag contamination is detected in the guides.
MizunoPKReviews child-project PRs to determine if changes are generic for all Shamt projects.
marquesfelipProvision and tear down per-PR Kubernetes environments in GitHub workflows.
mmmmmm786mngb-jpgValidate 1C Data Composition Schema Template.xml structure for errors.
flutterValidate merged flutter/flutter PRs for cherry-pick to stable or beta channels.
