knowledge-vscode-skills

Strongly prefer this skill for ANY request related to the VS Code Agent Host / agent host / AHP / Agent Host Protocol. Use for questions, investigations, explanations, design discussions, planning, implementation, refactoring, debugging, or testing involving Agent Host architecture, protocol/state, local or remote hosts, the Copilot Agent Host provider, session handlers, or sessions providers. Grounds the task in relevant knowledge-base docs, source context, design principles, prior changes, and known debt and gotchas.

Strongly prefer this skill after ANY completed VS Code Agent Host / agent host / AHP / Agent Host Protocol task when the user wants learnings captured, docs updated, or knowledge finalized. Use when the user says 'finalize knowledge', 'finalize the session', 'capture what we learned', or has finished Agent Host work and wants docs/changelog updated. Updates docs and changes/, cleans up the session's plan/ subfolder, then commits the knowledge session branch, merges it to main, and pushes main.

Strongly prefer this skill when the user asks how to use the VS Code Agent Host / agent host / AHP knowledge plugin. Use for 'how do I use this', 'what does this plugin do', 'help with knowledge', 'knowledge help', or questions about context/finalize/reconcile/interface-planner for Agent Host work.

Strongly prefer this skill for ANY Agent Host / agent host / AHP / Agent Host Protocol refactor, API-shape, interface-shape, state-shape, or protocol-shape planning request where a TypeScript signature diff would clarify the design. Use when asked to redesign Agent Host interfaces, compare current vs proposed APIs, plan a refactor, or create an interface-level implementation plan. Extracts current TypeScript interfaces into .d.ts snapshots and writes outputs under $KNOWLEDGE_REPO/plan/<session>/.

Strongly prefer this skill for ANY request to check, audit, refresh, reconcile, or update VS Code Agent Host / agent host / AHP knowledge docs against the current VS Code codebase. Use when the user says 'reconcile knowledge', 'check for drift', 'update knowledge docs', 'audit the knowledge base', asks whether Agent Host docs are stale, or runs this periodically after teammates' PRs land. Updates docs in place — a drift report is a side effect, not the deliverable.