MCP HubMCP Hub
스킬 목록으로 돌아가기

legal-sanity-review

vamseeachanta
업데이트됨 Today
87 조회
3
2
3
GitHub에서 보기
기타

정보

이 필수 워크플로우는 크로스 리뷰 전에 클라이언트 이름이나 전유권 참조 같은 법적 위험 요소를 코드에서 검사합니다. 위반 사항이 발견되면 리뷰 주기를 차단하며, 먼저 수정이 요구됩니다. PR 생성, 코드 포팅 또는 모든 크로스 리뷰 트리거에 사전 게이트로 활용하세요.

빠른 설치

Claude Code

추천
기본
npx skills add vamseeachanta/workspace-hub
플러그인 명령대체
/plugin add https://github.com/vamseeachanta/workspace-hub
Git 클론대체
git 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:

StepGateAction
1Legal ScanRun legal-sanity-scan.sh --diff-only
2Pass?If no → fix and re-scan
3Codex ReviewFirst cross-review iteration
4Gemini ReviewParallel 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

ConditionCodeAction
PASS0Proceed to cross-review
BLOCK1Fix violations, re-scan
SCAN_ERROR2Check 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 .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 저장소

vamseeachanta/workspace-hub
경로: .claude/skills/_internal/workflows/legal-sanity-review

연관 스킬

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.

스킬 보기

brainstorming-error-handling

기타

This Claude Skill provides structured guidance for handling common brainstorming roadblocks like conflicting requirements or scope creep. It offers specific action templates to resolve issues such as unclear responses or analysis paralysis. Developers should use this reference skill to maintain productive brainstorming sessions within Claude Code.

스킬 보기

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-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.

스킬 보기