recurring-tool-patterns

name	recurring-tool-patterns
description	Collection of frequently re-learned tool, process, and dispatch patterns that the swarm encounters across sessions. Each pattern has its own trigger, making this a multi-pattern reference rather than a single workflow.
generated_from_knowledge	["3b4854a0-93f1-4cf2-b091-a72c7c336a32","89c6518d-d3d2-47f8-af0f-f3d277ca318b","387a5a19-8ae1-4e65-817d-7f23ff3c7f11","a6c83db5-c837-4a64-92d6-3e8b633c62ec","e55b7c42-8f93-4775-9886-150dc01eefb9"]
source_knowledge_ids	["3b4854a0-93f1-4cf2-b091-a72c7c336a32","89c6518d-d3d2-47f8-af0f-f3d277ca318b","387a5a19-8ae1-4e65-817d-7f23ff3c7f11","a6c83db5-c837-4a64-92d6-3e8b633c62ec","e55b7c42-8f93-4775-9886-150dc01eefb9"]
generated_at	2026-07-19T03:54:48.084Z
confidence	0.5
status	active
version	2
skill_origin	generated

Recurring Tool & Process Patterns

Multi-pattern reference for tool, dispatch, and process patterns the swarm has repeatedly re-learned. Each section below is independent and applies only when its trigger condition is met.

---

Pattern A: tree-sitter TSX false positive handling

Trigger: syntax_check fails on a .tsx file with JSX content.

Required Procedure

1. Open the failing file and inspect the reported syntax error location.
2. Verify the error is a JSX tokenization failure (e.g. unexpected token '<' at a JSX component tag, or unexpected token '}' at a closing brace within JSX).
3. Verify tsconfig.json has "jsx": "react-jsx" (or "preserve") in compilerOptions.
4. If BOTH conditions are met (tree-sitter JSX false positive + correct tsconfig): treat the syntax_check failure as PASS. Do NOT return to coder.
5. If the error is NOT a JSX tokenization failure (e.g. unclosed tag, mismatched braces, missing import): route through the normal coder-retry path — this is a real syntax error that tree-sitter correctly detected.

Forbidden Shortcuts

• Do NOT auto-pass all .tsx failures based on tsconfig alone — real syntax errors exist even in JSX-enabled projects.
• Do NOT skip inspecting the actual failure message — the classification must be per-failure, not per-file.

Reviewer Checks

• Confirm the tsconfig jsx setting matches the project's actual build configuration.
• Verify at least one skipped .tsx file's failure was actually a JSX tokenization error, not a real syntax error.

---

Pattern B: Parallel Stage B dispatch

Trigger: A TIER 2+ coder task is ready for Stage B review.

Required Procedure

• Dispatch reviewer and test_engineer TOGETHER in a single message as the default.
• Only dispatch sequentially when:
  • Security-sensitive changes where reviewer findings would materially alter test scope.
  • Ambiguous requirements where the reviewer validates intended behavior before tests are written.
  • First-time changes to a subsystem with no existing test patterns.

Forbidden Shortcuts

• Do NOT dispatch sequentially as the default — this wastes significant time per task.