repository-drift-control
npx machina-cli add skill MSiccDev/ai-context-kit/repository-drift-control --openclawFiles (1)
SKILL.md
1.8 KB
Repository Drift Control
Purpose
Prevent divergence between authoritative specification, operational prompts/templates, and repository-facing documentation.
When To Use
- Use this skill when specification or governance files change.
- Use this skill during repo-wide refactors affecting canonical paths or precedence rules.
- Do not use this skill for isolated content edits without cross-artifact impact.
Required Inputs
- Changed authoritative artifact(s), especially
specs/context_aware_ai_session_spec.md. - Current canonical path map.
- List of dependent files expected to be audited.
Workflow
- Identify source-of-truth changes and affected dependency set.
- Audit templates, prompts, samples, README, and AGENTS for alignment.
- Apply consistent terminology and path references.
- Verify policy and precedence remain coherent after updates.
- Record drift-control outcomes in commit/PR summary.
Output Expectations
- Aligned artifacts with no stale references.
- Stable canonical paths and precedence documentation.
- Clear audit trail of what was updated and why.
Resources
- Governance contract:
../../AGENTS.md - Repository guide:
../../README.md - Authoritative model:
../../specs/context_aware_ai_session_spec.md
Constraints And Safety
- Treat specification as authoritative when conflicts exist.
- Keep guidance provider-neutral.
- Preserve canonical path stability unless explicitly migrating.
- Avoid partial updates that leave dependent artifacts inconsistent.
Source
git clone https://github.com/MSiccDev/ai-context-kit/blob/development/skills/repository-drift-control/SKILL.mdView on GitHub Overview
This skill ensures that any change to the authoritative specification or governance files is followed by aligned updates across prompts, templates, samples, and repository docs. By preventing divergence among canonical artifacts, it maintains governance integrity and consistent guidance across the repository.
How This Skill Works
Identify the source-of-truth changes and affected dependencies. Audit templates, prompts, samples, README, and AGENTS for alignment and update terminology and path references. Finally, verify that policy and precedence remain coherent after updates and record the outcome in the commit/PR summary.
When to Use It
- When specification or governance files change.
- During repo-wide refactors that affect canonical paths or precedence rules.
- When updating authoritative docs, AGENTS, or README links to reflect new standards.
- Before merging PRs that touch multiple artifacts (templates, prompts, samples, docs) to prevent drift.
- Not to be used for isolated edits that do not impact cross-artifact consistency.
Quick Start
- Step 1: Identify source-of-truth changes and affected dependency set.
- Step 2: Audit templates, prompts, samples, README, and AGENTS for alignment.
- Step 3: Apply consistent terminology and path references; record outcomes in the commit/PR.
Best Practices
- Identify source-of-truth changes and affected dependency set.
- Audit templates, prompts, samples, README, and AGENTS for alignment.
- Apply consistent terminology and path references across all artifacts.
- Verify policy and precedence remain coherent after updates.
- Record drift-control outcomes in the commit/PR summary with rationale.
Example Use Cases
- After updating specs/context_aware_ai_session_spec.md, audit AGENTS.md, README, templates, and prompts for alignment.
- Refactoring canonical paths required updating prompts and documentation to reflect new paths.
- A governance change prompted aligning prompts, samples, and docs with the new precedence rules.
- A multi-file PR touched templates, prompts, samples, and docs; drift-control ensured consistent terminology across artifacts.
- Migrating to a new canonical path map included updating dependent artifacts and recording the audit trail.
Frequently Asked Questions
Add this skill to your agents
