keystone:verify

Detect policy drift and strict violations in vendored policy files.

42|3|Updated May 31, 2026
One-click install
npx skills add https://github.com/tacoda/keystone --skill keystone-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: keystone:verify
Source: https://github.com/tacoda/keystone/tree/main/internal/framework/scaffold/templates/charter/skills/keystone-verify
Command: npx skills add https://github.com/tacoda/keystone --skill keystone-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the verification of vendored policies for drift and strict violations, ensuring project integrity and catching policy issues early.

Core Features & Use Cases

  • Policy Drift Detection: Checks vendored policy files for changes that may indicate drift from the expected state.
  • Strict Violation Reporting: Reports any project files that violate strict policy rules, helping maintain code quality.
  • Use Case: Before committing any charter change, use this Skill to ensure policy items are not accidentally shadowed and to confirm that the project is in a clean state.

Quick Start

Run the keystone verify command to check for policy drift and strict violations.

Frequently Asked Questions about keystone:verify

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

FAQPage Schema
How do I check my project for policy drift?

You can automate policy drift checks by scanning vendored policy files and project files for consistency. This detects any changes indicating drift from the expected state to maintain project integrity.

What is strict policy violation reporting for code quality?

Strict policy violation reporting identifies project files that violate strict policy rules. It ensures project adherence and maintains code quality by catching policy issues early before they are committed.

How do I verify vendored policy consistency before committing a charter change?

Verify vendored policy consistency by running an automated check to ensure policy items are not accidentally shadowed. This confirms your project is in a clean state and maintains strict enforcement before committing changes.

Can I use a script to automate strict enforcement and policy verification?

Yes, you can use a script to automate strict enforcement and policy verification. Running the verification command scans your files to detect drift and strict violations, preventing policy issues automatically.

When should I run a policy verification check to prevent issues?

You should run a policy verification check before committing any charter changes. This ensures your project files adhere to strict policy rules and detects drift early to maintain code quality and prevent policy issues.