policy-diff

Diff regulatory changes against an indexed policy library to identify required updates and coverage gaps.

Updated May 19, 2026
One-click install
npx skills add https://github.com/jrhueiueng/codex-for-legal --skill policy-diff-jrhueiueng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: policy-diff
Source: https://github.com/jrhueiueng/codex-for-legal/tree/main/plugins/jrhueiueng/codex-for-legal/skills/regulatory-legal__policy-diff
Command: npx skills add https://github.com/jrhueiueng/codex-for-legal --skill policy-diff-jrhueiueng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly identify which parts of your internal policy library are affected by a newly changed regulation, and what gaps must be addressed for compliance.

Core Features & Use Cases

  • Regulation-to-policy diffing: Extracts discrete new or changed requirements from regulatory input and matches them to the closest indexed policies.
  • Gap analysis by requirement: Produces per-requirement comparisons showing None/Partial/Full coverage, proposed change needed, and policy owner routing for follow-up.
  • Rule-status verification and guardrails: Flags uncertain “in force” status, prevents silently supplementing missing regulatory text, and supports scope-limitation warnings so you don’t accidentally treat a partial review as complete.

Quick Start

Use the policy-diff skill to diff a regulatory change against your indexed policies by asking: Diff this regulation against our policies and show the gaps by requirement.

Frequently Asked Questions about policy-diff

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

FAQPage Schema
How do I perform a policy gap analysis for new regulatory changes?

Policy gap analysis identifies coverage gaps by diffing a regulatory change against internal policies, extracting discrete requirements to match existing documentation, and flagging areas needing updates. It highlights partial or missing coverage for compliance updates.

How does regulatory change diffing match new requirements to existing policies?

Regulatory change diffing extracts discrete new or changed requirements from regulatory input and matches them to the closest indexed internal policies, producing per-requirement comparisons that show None, Partial, or Full coverage.

How do I extract regulatory compliance requirements from legal text updates?

Requirements extraction from regulatory text updates involves parsing the legal input to identify discrete new or changed obligations, then routing those requirements to policy owners for follow-up based on the structured gap analysis output.

Do I need an internal policy index to run a regulatory compliance diff?

Yes, regulatory compliance diffing requires loading a regulatory-legal policy index configured in your CLAUDE.md. This indexed library is necessary to match extracted regulatory requirements against existing policies and identify coverage gaps.

What happens when a regulatory change diff finds no matching policy?

When regulatory change diffing finds no matching policy, it reports a no-match result within the structured gap analysis, assigning a None coverage status and routing the missing requirement to the appropriate policy owner for follow-up.

How are uncertain regulatory statuses handled during policy gap analysis?

Policy gap analysis flags uncertain in-force statuses and includes a rule-status verification disclaimer. It applies scope-limitation warnings to prevent silently supplementing missing regulatory text or treating a partial review as complete.