Compliance Policy Check

Name: Compliance Policy Check
Author: oimiragieo

oimiragieo/agent-studio

58 installs
36 repo stars
Updated July 14, 2026
oimiragieo/agent-studio

Helps with ai & agent building tasks.

About

compliance-policy-check is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted development.

compliance-policy-check
AI & Agent Building
AI-coding skill

Compliance Policy Check by the numbers

58 all-time installs (skills.sh)
Ranked #6,517 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
Data as of Aug 4, 2026 (Skillselion catalog sync)

npx skills add https://github.com/oimiragieo/agent-studio --skill compliance-policy-check

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

[![Listed on Skillselion](https://skillselion.com/badge/skills/oimiragieo/agent-studio/compliance-policy-check.svg)](https://skillselion.com/skills/oimiragieo/agent-studio/compliance-policy-check)

Installs	58
repo stars	★ 36
Last updated	July 14, 2026
Repository	oimiragieo/agent-studio ↗

What it does

Helps with ai & agent building tasks.

Files

SKILL.mdMarkdownGitHub ↗

Compliance Policy Check

Overview

Evaluate a design/plan against framework policy and rule constraints before execution. Use this for regulated or high-risk changes.

When to Use

Before creator workflows for new artifacts
Before HIGH/EPIC implementation phases
During reflection when repeated policy violations are observed

Iron Laws

1. NEVER execute or modify code during compliance checks — this skill assesses policy alignment only; any implementation must happen separately after compliance is confirmed. 2. ALWAYS run compliance check before HIGH/EPIC implementation — high-risk changes that bypass compliance checks create undetected policy drift that compounds over time into systemic violations. 3. ALWAYS report findings with specific remediation tasks and owning agent — vague "policy violation" reports without actionable remediation steps don't produce fixes; every FAIL and CONDITIONAL must include a concrete task. 4. NEVER report PASS on partial compliance — a plan that satisfies 80% of policies is a CONDITIONAL, not a PASS; partial compliance masks the remaining violations and gives false confidence. 5. ALWAYS recheck after remediation, not just once — a single compliance check before implementation is insufficient; verify again after major changes to confirm remediations are complete.

Workflow

Step 1: Gather Policy Context

Read relevant files in .claude/rules/
Read applicable workflow/agent constraints
Read enforcement hook docs if needed

Step 2: Evaluate Proposed Change

Assess against:

1. Creator guard and artifact lifecycle rules 2. Routing and specialist-first requirements 3. Security and quality gate requirements 4. Memory/search/token-saver policy expectations

Step 3: Produce Decision

Return one policy decision:

PASS: policy-aligned
CONDITIONAL: allowed with required mitigations
FAIL: not policy-compliant

Use this output shape:

{
  "decision": "PASS|CONDITIONAL|FAIL",
  "policyFindings": ["..."],
  "requiredMitigations": [],
  "evidencePaths": ["..."],
  "recommendedNextStep": "..."
}

Output Protocol

For CONDITIONAL and FAIL, include precise remediation tasks and ownership (agent type).

Anti-Patterns

Anti-Pattern	Why It Fails	Correct Approach
Implementing code during compliance check	Conflates assessment with implementation	Assess only; implementation happens separately after PASS
Skipping compliance for "small" changes	Small changes introduce policy violations silently	Run compliance check proportionally for all HIGH/EPIC work
Reporting PASS on partial compliance	Masks unresolved violations; gives false confidence	Report CONDITIONAL with specific remediation required
Vague violation reports without remediation	Violations aren't fixed without clear next steps	Include agent, task, and target file for every FAIL/CONDITIONAL
Only checking once before implementation	Post-change compliance drift goes undetected	Recheck compliance after major implementation changes

Memory Protocol

Record recurring policy drift patterns in .claude/context/memory/issues.md and stabilized controls in .claude/context/memory/decisions.md.

'use strict';
/**
 * Post-execute hook for compliance-policy-check
 * Auto-generated by enterprise-bundle-scaffolder
 *
 * Records metrics after skill execution.
 */

function postExecute(_context) {
  // Record execution metrics
  return { ok: true, skill: 'compliance-policy-check' };
}

module.exports = { postExecute };

'use strict';
/**
 * Pre-execute hook for compliance-policy-check
 * Auto-generated by enterprise-bundle-scaffolder
 *
 * Validates inputs before skill execution.
 */

function preExecute(context) {
  // Validate skill invocation context
  if (!context || typeof context !== 'object') {
    return { allow: true, message: 'compliance-policy-check: no context to validate' };
  }
  return { allow: true };
}

module.exports = { preExecute };

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "title": "compliance-policy-checkInput",
  "description": "Input schema for Validate planned changes against local framework rules and policy guardrails before implementation or creation.",
  "type": "object",
  "additionalProperties": true,
  "properties": {
    "target": {
      "type": "string",
      "description": "Target file or path for the skill to operate on"
    },
    "options": {
      "type": "object",
      "description": "Additional options for skill execution",
      "additionalProperties": true
    }
  }
}

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "title": "compliance-policy-checkOutput",
  "type": "object",
  "additionalProperties": true,
  "properties": {
    "ok": {
      "type": "boolean"
    },
    "summary": {
      "type": "string"
    }
  }
}

#!/usr/bin/env node
'use strict';
/**
 * compliance-policy-check - Enterprise Skill Script
 * Auto-generated by enterprise-bundle-scaffolder
 */

const fs = require('fs');
const path = require('path');

// Parse arguments
const args = process.argv.slice(2);
const options = {};
for (let i = 0; i < args.length; i++) {
  if (args[i].startsWith('--')) {
    const key = args[i].slice(2);
    const value = args[i + 1] && !args[i + 1].startsWith('--') ? args[++i] : true;
    options[key] = value;
  }
}

if (options.help) {
  console.log(`
compliance-policy-check - Enterprise Skill

Usage:
  node main.cjs --check <file>    Check a file against guidelines
  node main.cjs --list            List all guidelines
  node main.cjs --help            Show this help

Description:
  Validate planned changes against local framework rules and policy guardrails before implementation or creation.
`);
  process.exit(0);
}

if (options.list) {
  console.log('Guidelines for compliance-policy-check:');
  console.log('See SKILL.md for full guidelines');
  process.exit(0);
}

console.log('compliance-policy-check skill loaded. Use with Claude for code review.');