vp-debug

name	vp-debug
description	Systematic debugging with persistent state tracking across sessions
version	0.2.0

## Invocation Banner

Output this banner as the first thing on every invocation — before questions, work, or any other output:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 VIEPILOT ► VP-DEBUG  v0.2.0 (fw 2.19.0)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

## Version Update Check (ENH-072)

After displaying the greeting banner, run:

node "$HOME/.claude/viepilot/bin/vp-tools.cjs" check-update --silent

If exit code = 1 (update available — new version printed to stdout): Display notice banner before any other output:

┌──────────────────────────────────────────────────────────────────┐
│ ✨ ViePilot {latest_version} available  (installed: {current})   │
│    npm i -g viepilot && vp-tools install --target {adapter_id}   │
└──────────────────────────────────────────────────────────────────┘

Replace {latest_version} with stdout from the command, {current} with the installed version, {adapter_id} with the active adapter (claude-code / cursor / antigravity / codex / copilot).

If exit code = 0 or command unavailable: silent, continue.

Suppression rules:

• --no-update-check flag on skill invocation → skip this step entirely
• config.json → update.check: false → skip this step entirely
• Show at most once per session (update_check_done session guard) </version_check> <persona_context>

Persona Context Injection (ENH-073)

At skill start, run:

node "$HOME/.claude/viepilot/bin/vp-tools.cjs" persona auto-switch
node "$HOME/.claude/viepilot/bin/vp-tools.cjs" persona context

Inject the output as ## User Persona context before any task execution. Silent if command unavailable or errors. </persona_context>

## A. Skill Invocation - Skill được gọi khi user mention `vp-debug`, `/vp-debug`, "debug", "gỡ lỗi" - Treat all user text after the skill mention as `{{VP_ARGS}}`

B. User Prompting

Prompt user conversationally. Guide through systematic debugging steps.

C. Tool Usage

Use Claude Code tools: Bash (shell), Read (file), Edit + Write (file write/patch), Grep (search), Glob (file patterns), LS, WebSearch, WebFetch, Agent (spawn subagent — multi-level nesting supported) Interactive: AskUserQuestion (deferred — preload via ToolSearch before first call)

## A. Skill Invocation Same trigger keywords as claude-code adapter.

C. Tool Usage

Use Cursor tools: run_terminal_cmd (shell), read_file (read), edit_file (write/edit), grep_search (search), web_search, codebase_search, list_dir, file_search Interactive: text list fallback (AskQuestion available in Plan Mode only; Agent Mode = text) Subagent: /multitask (user command, single-level only — not a callable tool) MCP limit: 40 tools

## A. Skill Invocation Same trigger keywords as claude-code adapter. Skill discovery: LLM-driven (automatic, no slash command needed).

C. Tool Usage

Use Antigravity tools: shell (cmd), file_read, file_write, MCP plugins Interactive: text fallback (TUI-based; no formal AskUserQuestion) Skill path: .agents/skills/<skill>/SKILL.md (project) or ~/.gemini/antigravity/skills/ (global) Note: Gemini CLI deprecated June 18, 2026 — use Antigravity CLI.

## A. Skill Invocation Same trigger keywords as claude-code adapter.

C. Tool Usage

Use Codex tools: container.exec (sandboxed shell), apply_patch (file write), web_search Interactive: text fallback (TUI Tab/Enter injection) Config: ~/.codex/config.toml

## A. Skill Invocation Same trigger keywords as claude-code adapter. Discovery: User-driven (`@agent-name` in GitHub Copilot Chat).

C. Tool Usage

Use Copilot tools: runCommands (shell), read/readfile (read), edit/editFiles (write), code_search, find_references Interactive: askQuestions (main agent only — NOT available in subagents; VS Code issue #293745) Skill path: .github/agents/<name>.agent.md <scope_policy>

ViePilot Namespace Guard (BUG-004)

• Default mode: only use and reference vp-* skills in ViePilot workflows.
• External skills (non vp-*) are out of framework scope unless user explicitly opts in.
• If external skills appear in runtime context, ignore them and route with the closest built-in vp-* skill. </scope_policy>

<implementation_routing_guard>

Implementation routing guard (ENH-021)

• Investigate + log session; does not merge default shipping fixes until user explicit (fix now, hotfix) or routes /vp-request → /vp-evolve → /vp-auto. Small patches only to reproduce are OK if the user agrees. See workflows/debug.md. </implementation_routing_guard>

Systematic debugging with persistent state tracking. Helps track issues across multiple sessions.

Creates/Updates:

• .viepilot/debug/session-{id}.json - Debug session state
• .viepilot/debug/CURRENT.json - Active session pointer

Modes:

• new - Start new debug session
• continue - Continue current session
• list - List all sessions
• close - Close current session with resolution

Architecture diagram intake (ENH-018):

• If .viepilot/ARCHITECTURE.md has diagram applicability matrix, consume it before deep debugging.
• Prioritize investigation context from diagrams marked required.
• For optional diagrams: use when available; do not block debug flow if missing.
• For N/A diagrams: respect rationale and avoid forcing diagram creation during debug.

<execution_context> @$HOME/{envToolDir}/workflows/debug.md </execution_context>

Optional flags: - `--new` : Force new session - `--continue` : Continue current session - `--list` : List all sessions - `--close [resolved|unresolved|wontfix]` : Close session - `--id ` : Work with specific session Execute workflow from `@$HOME/{envToolDir}/workflows/debug.md`

Debug Session Structure

{
  "id": "debug-{timestamp}",
  "status": "active|resolved|unresolved|wontfix",
  "created_at": "ISO timestamp",
  "updated_at": "ISO timestamp",
  "problem": {
    "description": "User's problem description",
    "symptoms": ["symptom1", "symptom2"],
    "error_messages": ["error1"],
    "affected_files": ["file1.js"]
  },
  "investigation": {
    "hypotheses": [
      {"id": 1, "description": "...", "status": "testing|confirmed|rejected"}
    ],
    "tests_run": [
      {"command": "...", "output": "...", "timestamp": "..."}
    ],
    "findings": ["finding1", "finding2"]
  },
  "resolution": {
    "root_cause": "Description of root cause",
    "fix_applied": "Description of fix",
    "files_changed": ["file1.js"],
    "verification": "How it was verified"
  }
}

Key Steps

1. Start Session: Gather problem description
2. Load Architecture Context: Read .viepilot/ARCHITECTURE.md matrix status (required|optional|N/A) and relevant Mermaid diagrams if present
3. Hypothesize: Generate possible causes
4. Test: Run tests to confirm/reject hypotheses
5. Track: Log all findings
6. Resolve: Document fix and root cause
7. Close: Mark session complete

<success_criteria>

• Session created with problem description
• Hypotheses tracked with status
• Tests logged with outputs
• Findings documented
• Resolution recorded (if resolved)
• State persists across sessions </success_criteria>