legal-sanity-review
О программе
Этот обязательный процесс проверяет код на наличие юридических рисков, таких как упоминания клиентов или ссылки на конфиденциальную информацию, перед кросс-ревью. Он блокирует цикл проверки при обнаружении нарушений, требуя их устранения. Используйте его как предварительный этап перед созданием PR, переносом кода или любым другим действием, запускающим кросс-ревью.
Быстрая установка
Claude Code
Рекомендуетсяnpx skills add vamseeachanta/workspace-hub/plugin add https://github.com/vamseeachanta/workspace-hubgit clone https://github.com/vamseeachanta/workspace-hub.git ~/.claude/skills/legal-sanity-reviewСкопируйте и вставьте эту команду в Claude Code для установки этого навыка
Документация
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 репозиторий
Похожие навыки
brainstorming
Другое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.
repo-cleanup-progress-tracking-commands
Другое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.
brainstorming-metrics
Другое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.
repo-cleanup-references-to-remove
Другое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.