skill-comply

Measures whether coding agents actually follow skills, rules, or agent definitions by: Measures whether a skill/rule is followed even when the prompt doesn't explicitly support it. Reports are self-contained and include: For users familiar with hooks, reports also include hook promotion recommendations for steps with low compliance. This is informational — the main value is the compliance visibility itself. - Auto-generating expected behavioral sequences (specs) from any .md file - Auto-generating scenarios with decreasing prompt strictness (supportive → neutral → competing) - Running claude -p and capturing tool call traces via stream-json - Classifying tool calls against spec steps using LLM (not regex) - Checking temporal ordering deterministically - Generating self-contained reports with spec, prompts, and timelines - Skills ( skills/*/SKILL.md ): Workflow skills like search-first, TDD guides - Rules ( rules/common/*.md ): Mandatory rules like testing.md, security.md, git-workflow.md - Agent definitions ( agents/*.md ): Whether an agent gets invoked when expected (internal workflow verification not yet supported) - User runs /skill-comply - User asks "is this rule actually being followed?" - After adding new rules/skills, to verify agent compliance - Periodically as part of quality maintenance - Expected behavioral sequence (auto-generated spec) - Scenario prompts (what...