Menu
Apply Tau-specific canonical-contract, ownership-boundary, protocol-alignment, and regression patterns during deslop cleanup. Use only alongside the deslop skill in the Tau repository. Trigger: explicit.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Clean up, canonicalize, and tighten a specified target (often a branch of PR work from a junior or AI agent, but also a package, the current changes, or any other bounded slice), refactoring freely within the target when that raises overall quality. Trigger: explicit.
Split large diffs or change sets into natural review chunks, then guide the user through focused diff_review sessions. Trigger: explicit.
Create implementation plans in two phases: clarify requirements first, then produce a concrete step-by-step plan without writing code. Trigger: explicit.
Conduct rigorous code review for git changes and return prioritized, actionable findings in a strict verdict/findings format. Trigger: explicit.
| name | deslop-patterns |
| description | Apply Tau-specific canonical-contract, ownership-boundary, protocol-alignment, and regression patterns during deslop cleanup. Use only alongside the deslop skill in the Tau repository. Trigger: explicit. |
Use these patterns alongside deslop.
Tau is pre-v1. Treat compatibility scaffolding for unshipped behavior as slop and converge on one explicit contract.
Flag code that creates a second owner or bypasses an existing boundary:
Move behavior to its single owning layer. When new behavior does not fit cleanly, reshape that abstraction instead of adding another path.
Hunt Tau-specific drift across:
Parser and serializer behavior must be symmetric. Collapse independently declared representations when their contracts are identical; keep a boundary-specific type only when it encodes a real semantic difference, with an explicit transformation. Derive values from canonical state instead of plumbing redundant metadata across layers.
Streaming and recovery must preserve one snapshot-owned source of truth. Do not hide protocol drift behind optional fields, permissive parsers, duplicate state, or client-specific shortcuts.
Keep tests when they protect protocol reconstruction, streaming, interruption, persistence, recovery, execution boundaries, hosted/local parity, tool dispatch, sandboxing, or another non-obvious invariant. Delete tests for simple rendering, visible literals, and direct delegation when stronger coverage already protects the behavior.
