agentsclimarketplace
Sign in

Repository drift control

Skill MSiccDev/ai-context-kit/skills/repository-drift-control

Enforce coordinated updates across specs, templates, prompts, samples, and docs to prevent repository guidance drift.From its SKILL.md

Install
npx -y skills add MSiccDev/ai-context-kit --skill repository-drift-control

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 12 stars12 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.2 KB, 369 tokens by cl100k_base, as published. Nobody here has run it

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.

How to Invoke

Load or attach this file's contents into your AI session to activate the workflow (paste, upload, or reference with #file:skills/repository-drift-control/SKILL.md in VS Code Copilot Chat). In Claude Projects, add it to project knowledge. See Invoking Skills in the README for full platform guidance.

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

  1. Identify source-of-truth changes and affected dependency set.
  2. Audit templates, prompts, samples, README, and AGENTS for alignment.
  3. Apply consistent terminology and path references.
  4. Verify policy and precedence remain coherent after updates.
  5. 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.

What ships with it: 1 file

1.7 KB alongside SKILL.md

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.