Agent-Skills.md

Agent Skills: Legal Sanity Review Workflow

Legal Sanity Review Workflow — mandatory pre-gate in the cross-review cycle

UncategorizedID: vamseeachanta/workspace-hub/legal-sanity-review

Repository

vamseeachanta/workspace-hub
vamseeachanta
44

Install this agent skill to your local

pnpm dlx add-skill https://github.com/vamseeachanta/workspace-hub/tree/HEAD/.agents/skills/_internal/workflows/legal-sanity-review

Skill Files

Browse the full folder contents for legal-sanity-review.

Download Skill

Loading file tree…

.agents/skills/_internal/workflows/legal-sanity-review/SKILL.md

Skill Metadata

Name
legal-sanity-review
Description
"Legal Sanity Review Workflow — mandatory pre-gate in the cross-review cycle"

Legal Sanity Review Workflow

Version: 1.0.0 Category: Workflows Triggers: Before cross-review (Codex/Gemini), PR creation, code porting

Purpose

Ensures no client project names, proprietary tool references, or legally sensitive content reaches the cross-review stage or a pull request. This is a mandatory pre-gate — if the legal scan fails, the review cycle does not proceed.

Review Flow

Codex/Gemini performs task
         ↓
    Commit changes
         ↓
    Legal Sanity Scan ◄── MANDATORY PRE-GATE
    ├── BLOCK → Fix violations → Re-scan
    └── PASS  → Proceed to Codex review
                    ↓
               Cross-Review Cycle

Integration Points

Cross-Review Pre-Gate

The legal scan runs before the first Codex/Gemini iteration:

| Step | Gate | Action | |------|------|--------| | 1 | Legal Scan | Run legal-sanity-scan.sh --diff-only | | 2 | Pass? | If no → fix and re-scan | | 3 | Codex Review | First cross-review iteration | | 4 | Gemini Review | Parallel cross-review |

PR Pre-Hook

Integrated into pr-manager.md hooks:

./scripts/legal/legal-sanity-scan.sh --diff-only || (echo "Legal sanity FAILED" && exit 1)

Manual Invocation

# Full repo scan
./scripts/legal/legal-sanity-scan.sh --repo=worldenergydata

# All submodules
./scripts/legal/legal-sanity-scan.sh --all

Exit Conditions

| Condition | Code | Action | |-----------|------|--------| | PASS | 0 | Proceed to cross-review | | BLOCK | 1 | Fix violations, re-scan | | SCAN_ERROR | 2 | Check script/config, retry |

Violation Response

When the scan finds block-severity violations:

  1. Stop — do not proceed to cross-review or PR creation
  2. Report — list each violation with file:line and pattern
  3. Fix — replace client references with generic equivalents
  4. Re-scan — confirm all violations are resolved
  5. Continue — proceed to the cross-review cycle

Configuration

Deny lists control what patterns are scanned:

  • Global: .legal-deny-list.yaml (workspace root)
  • Per-project: <submodule>/.legal-deny-list.yaml

See .Codex/rules/legal-compliance.md for the full policy.

Use this workflow whenever committing AI-generated or ported code to ensure legal compliance before review.