compliance-reviewer

Validate completion and modification claims against evidence and format rules.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/jf3096/personal-configs --skill compliance-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compliance-reviewer
Source: https://github.com/jf3096/personal-configs/tree/main/.codex/skills/compliance-reviewer.backup-20260313-112938
Command: npx skills add https://github.com/jf3096/personal-configs --skill compliance-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill acts as a gatekeeper, ensuring that any "completion" or "modification" claims are backed by verifiable evidence, adhere to a consistent format, and transparently disclose any risks, preventing incomplete or unsubstantiated deliveries.

Core Features & Use Cases

  • Evidence Verification: Checks if claims of completion or modification are supported by observable evidence (e.g., test results, command outputs, logs).
  • Format Compliance: Enforces a standardized output format for status declarations.
  • Risk Transparency: Ensures that potential risks associated with changes are identified and communicated.
  • Use Case: Before a developer merges code that fixes a bug, this Skill reviews their commit message and associated test results to ensure the fix is properly verified and documented according to team standards.

Quick Start

Use the compliance-reviewer skill to review the draft response before submitting it.

Frequently Asked Questions about compliance-reviewer

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

FAQPage Schema
How do I enforce code review compliance before merging a bug fix?

Code review compliance is enforced by validating completion claims against observable evidence like test results. A compliance gate requires standardized status declarations and transparent risk disclosure before allowing delivery.

What is a delivery gate in quality assurance?

A delivery gate in quality assurance is a two-stage verification checkpoint for modification claims. It validates outputs against predefined rules, requiring verifiable evidence and standardized status declarations before passing.

How do I verify code modification claims with observable evidence?

Code modification claims are verified by checking them against observable evidence like test results and logs. This evidence verification ensures completion declarations are substantiated and meet consistent formatting standards.

Does risk transparency require standardized output formats for completion claims?

Risk transparency requires standardized output formats for completion claims to ensure clear communication. Enforcing consistent status declarations guarantees that potential risks associated with modifications are properly identified and disclosed.

When do I need a compliance gate for my development workflow?

You need a compliance gate when developers merge code changes or claim task completion. It acts as a gatekeeper preventing unsubstantiated deliveries by requiring verifiable evidence, standardized status lines, and transparent risk disclosure.