gov-instruction-surface-synchronization

Synchronize sentinel-marked instruction blocks from a canonical source into editor-specific files.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/FernanSuoza/AIDD-project-bootstrap --skill gov-instruction-surface-synchronization
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gov-instruction-surface-synchronization
Source: https://github.com/FernanSuoza/AIDD-project-bootstrap/tree/main/templates/skills/gov-instruction-surface-synchronization
Command: npx skills add https://github.com/FernanSuoza/AIDD-project-bootstrap --skill gov-instruction-surface-synchronization

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Repository-wide policy and guidance changes often lead to inconsistent, duplicated, or drifting instruction surfaces across editor and tool integrations, creating governance gaps and unpredictable AI behavior; this Skill centralizes updates so a single canonical source propagates reliably to all generated instruction files.

Core Features & Use Cases

  • Canonical-to-surface synchronization: Reads docs/guidelines/canonical-instructions.md and inserts a sentinel-marked canonical block into CLAUDE.md, .github/copilot-instructions.md, .cursor/rules/repository.mdc, and optional GitHub instruction files.
  • Safe preview and CI enforcement: Supports --dry-run previews and a --check mode that exits non-zero on drift, enabling enforcement in CI pipelines.
  • Format-aware wrapping: Applies file-type specific wrappers (plain markdown, MDC frontmatter, GitHub instruction frontmatter) to preserve surrounding content while updating only the generated block.
  • Use Case: When a governance change (for example, an execution-mode policy) must be reflected identically across all editor-specific instruction surfaces before a release or audit.

Quick Start

Run the sync script to update all generated instruction surfaces from the canonical source and verify results with the check mode.

Frequently Asked Questions about gov-instruction-surface-synchronization

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

FAQPage Schema
How do I synchronize instruction files across multiple AI editors from a single source?

To synchronize instruction files across AI editors, this Skill reads a canonical source and inserts sentinel-marked blocks into CLAUDE.md, .github/copilot-instructions.md, and .cursor/rules/repository.mdc, ensuring byte-for-byte consistency across all generated instruction surfaces.

What is the best way to prevent policy drift in editor-specific instruction files?

Preventing policy drift in editor-specific instruction files requires propagating updates from a central canonical source. This Skill centralizes governance changes and applies format-aware wrapping to update only the generated blocks, preserving surrounding content.

Can I enforce instruction file consistency in CI pipelines?

You can enforce instruction file consistency in CI pipelines using the --check mode. This mode exits non-zero when it detects drift between the canonical instructions and the generated editor files, allowing automated enforcement during maintenance or audits.

How do I preview canonical instruction updates before applying them to repository files?

To preview canonical instruction updates before applying them, you can run the synchronization script with the --dry-run flag. This allows you to verify the sentinel-marked blocks and format-aware wrappers before modifying CLAUDE.md or copilot-instructions.md.

Does the synchronization process preserve existing content in copilot-instructions.md and repository.mdc files?

The synchronization process preserves existing content in copilot-instructions.md and repository.mdc files by applying file-type specific wrappers. It inserts sentinel-marked canonical blocks and updates only the generated sections while leaving surrounding content untouched.

When do I need to update instruction surfaces for AI tool integrations?

You need to update instruction surfaces for AI tool integrations during repository-wide governance changes, audits, or editor integration modifications. Synchronizing from the canonical source ensures identical execution-mode policies across all generated instruction files.