跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
法律与合规

constraint-check

Meta-validator for HARD-GATEs. Use when auditing whether a skill's mandatory constraints were actually followed during a workflow (not just claimed). Called by cook, team, and audit for discipline compliance.

Rune-kit · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add Rune-kit/rune --skill constraint-check

技能说明


name: constraint-check description: "Meta-validator for HARD-GATEs. Use when auditing whether a skill's mandatory constraints were actually followed during a workflow (not just claimed). Called by cook, team, and audit for discipline compliance." user-invocable: false metadata: author: runedev version: "1.1.0" layer: L3 model: sonnet group: validation tools: "Read, Glob, Grep"

constraint-check

Purpose

The internal affairs department for Rune skills. Checks whether HARD-GATEs and mandatory constraints were actually followed during a workflow — not just claimed to be followed. Reads the constraint definitions from skill files and audits the conversation trail for compliance.

While completion-gate checks if claims have evidence, constraint-check checks if the PROCESS was followed. Did you actually write tests before code? Did you actually get plan approval? Did you actually run sentinel?

Triggers

  • Called by cook (L1) at end of workflow as discipline audit
  • Called by team (L1) to verify stream agents followed constraints
  • Called by audit (L2) during quality dimension assessment
  • /rune constraint-check — manual audit of current session

Calls (outbound)

None — pure read-only validator.

Called By (inbound)

  • cook (L1): end-of-workflow discipline audit
  • team (L1): verify stream agent compliance
  • audit (L2): quality dimension
  • User: manual session audit

Execution

Step 1 — Identify Active Skills

Parse the conversation/workflow to identify which skills were invoked:

Extract from context:
  - Skills invoked via Skill tool (exact list)
  - Skills referenced in agent narrative
  - Phase progression (cook phases completed)

Step 2 — Load Constraint Definitions

For each invoked skill, extract HARD-GATEs and numbered constraints:

For each skill in invoked_skills:
  Read: skills/<skill>/SKILL.md
  Extract:
    - <HARD-GATE> blocks → mandatory, violation = BLOCK
    - ## Constraints numbered list → required, violation = WARN
    - ## Mesh Gates table → required gates

Step 3 — Audit Compliance

Check each constraint against the conversation evidence:

Constraint TypeHow to VerifyEvidence Source
"MUST write tests BEFORE code"Test file Write/Edit timestamps before implementation Write/EditTool call ordering
"MUST get user approval"User message containing "go"/"yes"/"proceed" after planConversation history
"MUST run verification"Bash command with test/lint/build outputTool call results
"MUST show actual output"Stdout captured in agent responseAgent messages
"MUST NOT modify files outside scope"Git diff files vs plan file listGit + plan comparison
"Iron Law: delete code before test"No implementation code exists before test creationTool call ordering

Step 4 — Classify Violations

Violation TypeSeverityMeaning
HARD-GATE violationBLOCKSkill says this is non-negotiable
Constraint violationWARNSkill says this is required but not fatal
Best practice skipINFORecommended but optional

Step 5 — Report

## Constraint Check Report
- **Status**: COMPLIANT | VIOLATIONS_FOUND | CRITICAL_VIOLATION
- **Skills Audited**: [count]
- **Constraints Checked**: [count]
- **Violations**: [count by severity]

### HARD-GATE Violations (BLOCK)
- [skill:test] Iron Law: implementation code written at tool_call #12 BEFORE test file created at #15
- [skill:cook] Plan Gate: Phase 4 started without user approval message

### Constraint Violations (WARN)
- [skill:verification] Constraint 2: "All tests pass" claimed at message #20 without stdout evidence
- [skill:sentinel] Constraint 3: files scanned list not included in report

### Compliance Summary
| Skill | HARD-GATEs | Constraints | Status |
|-------|-----------|-------------|--------|
| cook | 3/3 ✓ | 6/7 (1 WARN) | WARN |
| test | 0/1 ✗ | 8/9 (1 WARN) | BLOCK |
| verification | 1/1 ✓ | 4/6 (2 WARN) | WARN |
| sentinel | 1/1 ✓ | 7/7 ✓ | PASS |

### Remediation
- BLOCK: test Iron Law — delete implementation, restart with test-first
- WARN: verification — re-run and capture stdout

Constraint Catalog (Quick Reference)

Key HARD-GATEs across skills that constraint-check audits:

SkillHARD-GATECheck Method
testTests BEFORE code (Iron Law)Tool call ordering
cookScout before plan, plan before codePhase progression
planEvery code phase has test entryPlan content
verificationEvidence for every claimStdout capture
sentinelBLOCK = halt pipelineNo commit after BLOCK
preflightBLOCK = halt pipelineNo commit after BLOCK
debugNo code changes during debugNo Write/Edit in debug
debug3-fix escalationFix attempt counter
brainstormNo implementation before approvalUser message check

Output Format

Constraint Check Report with status (COMPLIANT/VIOLATIONS_FOUND/CRITICAL_VIOLATION), HARD-GATE violations, constraint violations, compliance summary table, and remediation steps. See Step 5 Report above for full template.

Constraints

  1. MUST check all HARD-GATEs for every invoked skill — not just the ones that seem relevant
  2. MUST use tool call ordering (not agent narrative) to verify temporal constraints
  3. MUST distinguish HARD-GATE violations (BLOCK) from constraint violations (WARN)
  4. MUST report specific evidence for each violation — not just "violated"
  5. MUST NOT accept agent's self-report as compliance evidence — check independently

Sharp Edges

Failure ModeSeverityMitigation
Agent self-reports compliance and constraint-check trusts itCRITICALConstraint 5: check tool calls independently, not agent narrative
Only checking cook constraints, missing test/sentinel/etcHIGHConstraint 1: audit ALL invoked skills, not just the orchestrator
Temporal check wrong
阅读完整来源 ↗