skills.rest
michaelarutyunov
michaelarutyunovCOMMUNITY
Explore all skills by this author →
GitHub

cr

Validate session changes against codified context governance principles.

Updated Jan 21, 2026
Search Tags:#documentation#governance#session-review#drift-check#context-principles#doc-mapping
One-click install
npx skills add https://github.com/michaelarutyunov/interview-system-v2 --skill cr-michaelarutyunov
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cr
Source: https://github.com/michaelarutyunov/interview-system-v2/tree/main/.claude/skills/cr
Command: npx skills add https://github.com/michaelarutyunov/interview-system-v2 --skill cr-michaelarutyunov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Codified context governance checks at session end to verify that changes to agents, context docs, or CLAUDE.md align with defined principles, surfacing gaps and actionable updates.

Core Features & Use Cases

  • Drift-detection of session changes against codified context principles to identify missing or inconsistent updates.
  • Tiered update recommendations (Tier 2/3) and doc-mapping suggestions when governance gaps are found.
  • Structured, export-ready session review reports that guide product teams on next steps and traceability.

Quick Start

Review the latest session changes and determine whether CLAUDE.md, agents, or context docs need updates to maintain governance alignment.

Frequently Asked Questions about cr

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

FAQPage Schema
How do I audit session changes against codified context governance principles?▼

Session context governance checks validate multi-file changes at session end to detect structural drift, verify cross-references, and produce actionable doc-mapping recommendations for agents or CLAUDE.md files.

What is context drift detection and when do I need to run a drift-check?▼

Context drift detection identifies missing or inconsistent updates after multi-file changes. Run a drift-check at session end to verify modifications align with codified context principles before finalizing updates.

How do I validate context docs and CLAUDE.md updates after modifying multiple files?▼

Validate context docs and CLAUDE.md updates by cross-referencing session changes against defined governance principles, surfacing gaps and generating structured, export-ready session review reports with traceability.

Can I safely edit CLAUDE.md directly during a session context review?▼

No, safe operations avoid isolated Tier 1 CLAUDE.md edits during a session review. The process proposes Tier 2 and Tier 3 context doc updates or mapping changes only when clearly justified by governance gaps.

What are the limitations of automated doc-mapping for context governance?▼

Automated doc-mapping limitations include avoiding direct Tier 1 CLAUDE.md modifications in isolation and restricting recommendations to Tier 2 or Tier 3 updates only when governance gaps clearly justify changes.

Related Skills

Explore More Content & Communication Skills→
serejarisserejaris
215

claude-md-writer

Enforce a modular 3-tier structure and size limits for CLAUDE.md files.

Community
Basic
changoo89changoo89
19

three-tier-docs

Synchronize CLAUDE.md, CONTEXT.md, and docs/ai-context files across three tiers.

Community
Advanced
l3ochol3ocho

drift-detection

Identify and flag drift between documentation references and the codebase.

Community
Advanced
I2olanDI2olanD

documentation-sync

Detect documentation drift by comparing code changes against related docs and generate update proposals.

Community
Intermediate