legal-sanity-review

vamseeachanta

Updated Today

112 views

Other

About

This mandatory workflow scans code for legal risks like client names or proprietary references before cross-review. It blocks the review cycle if violations are found, requiring fixes first. Use it as a pre-gate for PR creation, code porting, or any cross-review trigger.

Quick Install

Claude Code

Recommended

Primary

npx skills add vamseeachanta/workspace-hub

Plugin CommandAlternative

/plugin add https://github.com/vamseeachanta/workspace-hub

Git CloneAlternative

git clone https://github.com/vamseeachanta/workspace-hub.git ~/.claude/skills/legal-sanity-review

Copy and paste this command in Claude Code to install this skill

Documentation

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

Claude/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:

Stop — do not proceed to cross-review or PR creation
Report — list each violation with file:line and pattern
Fix — replace client references with generic equivalents
Re-scan — confirm all violations are resolved
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 .claude/rules/legal-compliance.md for the full policy.

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

GitHub Repository

vamseeachanta/workspace-hub

Path: .claude/skills/_internal/workflows/legal-sanity-review

Related Skills

brainstorming

Other

The brainstorming skill transforms initial ideas into detailed specifications through iterative questioning and collaborative dialogue. It helps developers explore design options, evaluate trade-offs, and create shared understanding before implementation. This prevents rework by systematically refining concepts into actionable plans.

View skill

repo-cleanup-progress-tracking-commands

Other

This sub-skill provides shell commands for tracking file counts during repository cleanup operations, specifically for hidden folders like `.claude` and `.agent-os`. It includes verification scripts to ensure no files are lost after merging changes. Use it when consolidating or reorganizing project directories to monitor progress and validate results.

View skill

brainstorming-metrics

Other

This skill provides structured metrics for evaluating brainstorming sessions, including targets for questions per design, validation rates, and stakeholder alignment. It helps developers measure brainstorming effectiveness and implementation quality. Use it to establish clear success criteria and track rework during project planning phases.

View skill

repo-cleanup-references-to-remove

Other

This skill identifies legacy directories and files that should be removed or consolidated during repository cleanup. It provides a specific checklist for developers, including paths like `.agent-os/` and `.drcode/` that are obsolete or have been moved to new locations. Use this reference when cleaning up a Claude Code project to ensure proper migration and deletion of outdated assets.

View skill