keystone:check-drift

Compare current code diffs against loaded charter rules to detect drift.

42|3|Updated May 31, 2026

Search Tags:#code compliance #keystone #drift check #charter enforcement #pre-verification

Ready to run

npx skills add https://github.com/tacoda/keystone --skill keystone-check-drift

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: keystone:check-drift
Source: https://github.com/tacoda/keystone/tree/main/internal/framework/scaffold/templates/charter/skills/keystone-check-drift
Command: npx skills add https://github.com/tacoda/keystone --skill keystone-check-drift

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a fast, pre-verify check to ensure that the loaded charter rules still match the code's current behavior, helping to catch drift issues early.

Core Features & Use Cases

Pre-Implementation Check: Runs before the full computational sensor suite to catch drift before it causes further issues.
Refactoring Safety: Ensures idiom rules still apply after large refactorings.
Repeated Failure Resolution: Helps identify drift as the cause when the /keystone:verify command fails repeatedly.

Quick Start

Run the keystone:check-drift command to perform the drift sensor check.

Frequently Asked Questions about keystone:check-drift

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

FAQPage Schema

How do I check code drift against charter rules mid-implementation?▼

To check code drift against charter rules, run a pre-verify drift sensor that compares your current code diff against loaded charter rules to catch compliance issues early during implementation.

Why does my keystone verify command keep failing repeatedly?▼

Repeated verify failures often indicate drift between your code and charter rules; running a pre-verify drift check isolates this by comparing the current code diff against the active charter to identify the mismatch.

How do I ensure charter idiom rules still apply after a large refactoring?▼

To ensure idiom rules still apply after refactoring, execute a drift check that compares the updated code diff against loaded charter rules to confirm compliance before proceeding further.

What prerequisites are needed to run a drift check on a code diff?▼

Running a drift check requires the charter to be up-to-date and the code to be in a state where a diff can be generated, allowing the sensor to compare current changes against loaded rules.

When should I use a pre-verify drift check instead of full code compliance verification?▼

Use a pre-verify drift check for mid-implementation checks, refactoring safety, and troubleshooting repeated verify failures, as it runs faster than the full computational sensor suite to catch drift early.