Hub Context Skill

Purpose

Defines a context sensing protocol for the /epost smart hub. Before routing, the hub gathers a snapshot of the current working state to make informed routing decisions.

Context Snapshot Protocol

On every /epost invocation, gather these signals before parsing intent:

1. Git State

Run these commands and capture output:

2. Platform Detection

Determine the dominant platform from changed files:

Rules:

• If 80%+ of changed files share a platform → that platform is dominant
• If mixed → set platform to multi (triggers orchestrator delegation)
• If no changed files → check current working directory for platform signals
• Platform prefix in $ARGUMENTS always overrides auto-detection

3. Error Signals

Check for recent errors (only if platform detected):

Important: Error signal gathering should be fast (< 2 seconds). Skip checks that would be slow. TypeScript check is the most valuable — run it if web context is detected.

4. Session Hints

Context Summary Format

After gathering, produce a structured summary for the routing engine:

[Context] branch: {branch_name} | platform: {platform}
[Context] staged: {count} files ({extensions}) | unstaged: {count} files ({extensions})
[Context] errors: {error_summary} (or "none detected")
[Context] plan: {plan_file} ({status}) (or "no active plan")
[Context] hints: {branch_type}, {other_signals}

Context Boost Table

The routing engine uses context to boost intent categories:

Smart Routing

Prompt Classification

• Dev task (action verbs: cook, fix, plan, test, debug, etc.) → route via intent map
• Kit question ("which agent", "list commands", "our conventions") → epost-orchestrator
• External tech question ("how does React...", "what is gRPC") → epost-researcher
• Conversational (greetings, opinions, clarifications) → respond directly, no routing

Intent → Skill Map

Routing Rules

• If user types a slash command explicitly → execute it directly, skip routing
• If ambiguous → use context boost to break tie; if still ambiguous → ask user (max 1 question)
• If multi-intent ("plan and build X") → delegate to epost-orchestrator
• Platform detection delegates to skill-discovery — never hardcode platform logic here

Rules

• Context gathering MUST complete before intent parsing
• If a git command fails (not a git repo), skip git state gracefully
• Never run destructive commands during context gathering
• TypeScript check should timeout after 5 seconds — skip if slow
• Context snapshot is read-only — never modify working state