rule-check-skill

Collects bounded governance and rule-check evidence for Verify-stage policy gating.

29|2|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/OceanEyeFF/servo --skill rule-check-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rule-check-skill
Source: https://github.com/OceanEyeFF/servo/tree/main/product/harness/skills/rule-check-skill
Command: npx skills add https://github.com/OceanEyeFF/servo --skill rule-check-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns rule and governance checks during a Verify worktrack into structured, policy-ready evidence outputs instead of prematurely producing a final gate decision.

Core Features & Use Cases

  • Evidence collection for policy lane: Captures rules/governance evidence for the policy lane and prepares inputs for the subsequent gate-skill policy-gate.
  • Verify-scoped rule checking: Runs only within the current active worktrack scope in WorktrackScope.Verify under 范围内 boundaries, avoiding full-repo auditing behavior.
  • Structured handoff instead of裁决: Produces a fixed-format rule check report plus a policy evidence handover (e.g., evidence items, violations/missing evidence, required sync items, and deferred checks).

Quick Start

Use rule-check-skill when your Harness is in an active Verify phase and you need a bounded round of governance/rule evidence collection for policy gating rather than final pass/fail adjudication.

Frequently Asked Questions about rule-check-skill

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

FAQPage Schema
How do I collect governance evidence for policy gating without issuing a final pass or fail verdict?

To collect governance evidence without a final verdict, use a Verify-scoped rule check process that produces structured policy evidence handoffs, capturing violations and required sync items separately from gate decisions.

What is the difference between audit readiness checks and final compliance gate adjudication?

Audit readiness checks gather required policy evidence within a bounded scope, whereas compliance gate adjudication uses that collected evidence to render a final pass or fail decision for the workflow.

How do I perform a bounded scope rule check during a Verify worktrack phase?

To perform a bounded scope rule check during a Verify worktrack, run governance checks only against touched surfaces and active synchronization obligations, avoiding full-repo auditing behavior outside the defined boundaries.

Can I run full-repo auditing checks for policy evidence within an active Verify worktrack scope?

No, you cannot run full-repo auditing within an active Verify worktrack scope. The process enforces bounded scope constraints, focusing exclusively on touched surfaces and required synchronization obligations for accurate policy evidence.

Why are my governance violations and missing evidence items mixed into ambiguous summaries?

Governance violations and missing evidence items get mixed into ambiguous summaries when rule checks lack structured handoff formatting, which can be resolved by enforcing a fixed-format report that separates violations, missing evidence, and deferred checks.

Does policy evidence collection work without a dedicated gate-skill for final compliance decisions?

Policy evidence collection can function independently to capture rules and governance data, but a dedicated gate-skill is required downstream to consume the structured handoff and execute the final compliance gate adjudication.