wiring
npx machina-cli add skill parcadei/Continuous-Claude-v3/wiring --openclawWiring Verification
When building infrastructure components, ensure they're actually invoked in the execution path.
Pattern
Every module needs a clear entry point. Dead code is worse than no code - it creates maintenance burden and false confidence.
The Four-Step Wiring Check
Before marking infrastructure "done", verify:
- Entry Point Exists: How does user action trigger this code?
- Call Graph Traced: Can you follow the path from entry to execution?
- Integration Tested: Does an end-to-end test exercise this path?
- No Dead Code: Is every built component actually reachable?
DO
Verify Entry Points
# Hook registered?
grep -r "orchestration" .claude/settings.json
# Skill activated?
grep -r "skill-name" .claude/skill-rules.json
# Script executable?
ls -la scripts/orchestrate.py
# Module imported?
grep -r "from orchestration_layer import" .
Trace Call Graphs
# Entry point (hook)
.claude/hooks/pre-tool-use.sh
↓
# Shell wrapper calls TypeScript
npx tsx pre-tool-use.ts
↓
# TypeScript calls Python script
spawn('scripts/orchestrate.py')
↓
# Script imports module
from orchestration_layer import dispatch
↓
# Module executes
dispatch(agent_type, task)
Test End-to-End
# Don't just unit test the module
pytest tests/unit/orchestration_layer_test.py # NOT ENOUGH
# Test the full invocation path
echo '{"tool": "Task"}' | .claude/hooks/pre-tool-use.sh # VERIFY THIS WORKS
Document Wiring
## Wiring
- **Entry Point**: PreToolUse hook on Task tool
- **Registration**: `.claude/settings.json` line 45
- **Call Path**: hook → pre-tool-use.ts → scripts/orchestrate.py → orchestration_layer.py
- **Test**: `tests/integration/task_orchestration_test.py`
DON'T
Build Without Wiring
# BAD: Created orchestration_layer.py with 500 lines
# But nothing imports it or calls it
# Result: Dead code, wasted effort
# GOOD: Start with minimal wiring, then expand
# 1. Create hook (10 lines)
# 2. Test hook fires
# 3. Add script (20 lines)
# 4. Test script executes
# 5. Add module logic (iterate)
Create Parallel Routing
# BAD: Agent router has dispatch logic
# AND skill-rules.json has agent selection logic
# AND hooks have agent filtering logic
# Result: Three places to update, routing conflicts
# GOOD: Single source of truth for routing
# skill-rules.json activates skill → skill calls router → router dispatches
Assume Imports Work
# BAD: Assume because you wrote the code, it's imported
from orchestration_layer import dispatch # Does this path exist?
# GOOD: Verify imports at integration test time
uv run python -c "from orchestration_layer import dispatch; print('OK')"
Skip Integration Tests
# BAD: Only unit test
pytest tests/unit/ # All pass, but nothing works end-to-end
# GOOD: Integration test the wiring
pytest tests/integration/ # Verify full call path
Common Wiring Gaps
Hook Not Registered
// .claude/settings.json - hook definition exists but not in hooks section
{
"hooks": {
"PreToolUse": [] // Empty! Your hook never fires
}
}
Fix: Add hook registration:
{
"hooks": {
"PreToolUse": [{
"matcher": ["Task"],
"hooks": [{
"type": "command",
"command": "$CLAUDE_PROJECT_DIR/.claude/hooks/orchestration.sh"
}]
}]
}
}
Script Not Executable
# Script exists but can't execute
-rw-r--r-- scripts/orchestrate.py
# Fix: Make executable
chmod +x scripts/orchestrate.py
Module Not Importable
# Script tries to import but path is wrong
from orchestration_layer import dispatch
# ModuleNotFoundError
# Fix: Add to Python path or use proper package structure
sys.path.insert(0, str(Path(__file__).parent.parent))
Router Has No Dispatch Path
# BAD: Router has beautiful mapping
AGENT_MAP = {
"implement": ImplementAgent,
"research": ResearchAgent,
# ... 18 agent types
}
# But no dispatch function uses the map
def route(task):
return "general-purpose" # Hardcoded! Map is dead code
# GOOD: Dispatch actually uses the map
def route(task):
agent_type = classify(task)
return AGENT_MAP[agent_type]
Wiring Checklist
Before marking infrastructure "complete":
- Entry point identified and tested (hook/skill/CLI)
- Call graph documented (entry → module execution)
- Integration test exercises full path
- No orphaned modules (everything imported/called)
- Registration complete (settings.json/skill-rules.json)
- Permissions correct (scripts executable)
- Import paths verified (manual import test passes)
Real-World Examples
Example 1: DAG Orchestration (This Session)
What was built:
opc/orchestration/orchestration_layer.py(500+ lines)opc/orchestration/dag/(DAG builder, validator, executor)- 18 agent type definitions
- Sophisticated routing logic
Wiring gap:
- No hook calls orchestration_layer.py
- No script imports the DAG modules
- Agent routing returns hardcoded "general-purpose"
- Result: 100% dead code
Fix:
- Create PreToolUse hook for Task tool
- Hook calls
scripts/orchestrate.py - Script imports and calls
orchestration_layer.dispatch() - Dispatch uses AGENT_MAP to route to actual agents
- Integration test: Submit Task → verify correct agent type used
Example 2: Artifact Index (Previous Session)
What was built:
- SQLite database schema
- Indexing logic
- Query functions
Wiring gap:
- No hook triggered indexing
- Files created but never indexed
Fix:
- PostToolUse hook on Write tool
- Hook calls indexing script immediately
- Integration test: Write file → verify indexed
Detection Strategy
Grep for Orphans
# Find Python modules
find . -name "*.py" -type f
# Check if each is imported
for file in $(find . -name "*.py"); do
module=$(basename $file .py)
grep -r "from.*$module import\|import.*$module" . || echo "ORPHAN: $file"
done
Check Hook Registration
# List all hooks in .claude/hooks/
ls .claude/hooks/*.sh
# Check each is registered
for hook in $(ls .claude/hooks/*.sh); do
basename_hook=$(basename $hook)
grep -q "$basename_hook" .claude/settings.json || echo "UNREGISTERED: $hook"
done
Verify Script Execution
# Find all Python scripts
find scripts/ -name "*.py"
# Test each can be imported
for script in $(find scripts/ -name "*.py"); do
uv run python -c "import sys; sys.path.insert(0, 'scripts'); import $(basename $script .py)" 2>/dev/null || echo "IMPORT FAIL: $script"
done
Source
- This session: DAG orchestration wiring gap - 500+ lines of dead code discovered
- Previous sessions: Artifact Index, LMStudio integration - wiring added after initial build
Source
git clone https://github.com/parcadei/Continuous-Claude-v3/blob/main/.claude/skills/wiring/SKILL.mdView on GitHub Overview
Wiring Verification ensures infrastructure components are actually invoked in the execution path. It guards against dead code and miswired interfaces by enforcing a four-step check: entry point, call graph, integration tests, and no dead code.
How This Skill Works
The process scans for defined entry points, traces the call graph from trigger to execution, validates end-to-end tests exercise the path, and confirms every built component is reachable. It provides concrete DO/DON'T guidance and highlights common gaps to fix wiring issues quickly.
When to Use It
- When wiring a new infrastructure component and you need to confirm it’s actually invoked in the execution path
- When you’ve added hooks or orchestration scripts and must verify the end-to-end path from trigger to execution
- When you see dead code or unreachable modules and want to eliminate false confidence
- When preparing integration tests and want to validate the full invocation path across layers
- When auditing a project for maintainability and documenting wiring rules for future changes
Quick Start
- Step 1: Verify Entry Points - ensure hooks, script executables, and module imports exist
- Step 2: Trace the Call Graph - follow the flow from trigger to execution across layers
- Step 3: Run Integration Tests - exercise end-to-end paths and fix any wiring gaps
Best Practices
- Verify that every module has a clearly defined entry point that is triggered by the runtime
- Trace the full call graph from trigger to execution (hook -> script -> module)
- Test end-to-end paths with integration tests, not just unit tests
- Document wiring: registration, call path, and how components are wired together
- Avoid parallel routing and ensure a single source of truth for routing decisions
Example Use Cases
- Hook registered for a Task tool, with a clear call path from pre-tool-use hook to orchestrate.py
- A failing integration test reveals a missing dispatch path in orchestration_layer
- README-like wiring doc showing Entry Point, Registration, and Call Path
- Common gap: script exists but is not executable; fix by making it executable
- Invalid import path detected during integration tests and corrected by adjusting PYTHONPATH