Semantic Slicing

Purpose

Turn a large repo into reviewable semantic slices with evidence. Use code shape, threat candidates, issue clusters, and support chatter together so review budget lands on the right parts of the system.

Default stance: map locally first, rank second, spend agent/security-review budget last.

When to use

• Setting up or running openclaw/clawpatch against a target repo.
• Setting up or running vercel-labs/deepsec against a target repo.
• Producing a local visual map of feature slices, risky files, ownership clusters, or review targets.
• Cross-checking code slices against gitcrawl issue/PR data or discrawl Discord/support data.
• Planning a focused security, regression, architecture, or maintainer-review pass for a large repo.

Workflow