constraint-check

Audit conversation history for SKILL.md HARD-GATE constraint violations.

82|23|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/Rune-kit/rune --skill constraint-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: constraint-check
Source: https://github.com/Rune-kit/rune/tree/main/skills/constraint-check
Command: npx skills add https://github.com/Rune-kit/rune --skill constraint-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill acts as an internal auditor for Rune skills, ensuring that mandatory constraints and HARD-GATEs defined in SKILL.md files are actually followed during a workflow, not just claimed.

Core Features & Use Cases

  • Discipline Audit: Verifies adherence to process rules (e.g., tests before code, user approval).
  • Compliance Reporting: Identifies and categorizes violations (BLOCK, WARN, INFO) with evidence.
  • Use Case: After a complex development workflow, run constraint-check to automatically verify that all required steps, like writing tests before implementation and obtaining user sign-off, were completed correctly.

Quick Start

Run a manual audit of the current session's constraints.

Frequently Asked Questions about constraint-check

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

FAQPage Schema
How do I audit workflow compliance with mandatory process constraints?

To audit workflow compliance, run a constraint-check to parse conversation history and tool call ordering, verifying adherence to mandatory constraints defined in SKILL.md files. It classifies violations as BLOCK, WARN, or INFO with specific evidence and remediation steps.

What is a HARD-GATE in software workflow validation?

A HARD-GATE in software workflow validation is a mandatory constraint defined in SKILL.md files that must be satisfied during a workflow. The audit checks tool call ordering against these gates to enforce process discipline like writing tests before implementation.

How do I verify if tests were written before code implementation in a session?

You can verify tests were written before code by running a discipline audit that parses tool call ordering. It checks the conversation history against mandatory constraints to ensure required steps were completed in the correct sequence.

Can I get specific evidence and remediation steps for process rule violations?

Yes, you can get specific evidence and remediation steps for process rule violations. The compliance reporting feature identifies violations and categorizes them as BLOCK, WARN, or INFO, providing detailed evidence from the conversation history.

Do I need any external dependencies to run compliance reporting on my development workflow?

No external dependencies are required to run compliance reporting. The audit operates by internally parsing conversation history and tool call ordering against constraints defined in SKILL.md files without needing external libraries.

When should I run an audit for skill compliance and process discipline?

You should run an audit for skill compliance after a complex development workflow to automatically verify that all required steps, such as writing tests before implementation and obtaining user sign-off, were completed correctly.