roblourens

Release or publish ahp-inspector to npm. Use when preparing an ahp-inspector npm release, running the publish.yml GitHub Action, checking a release action, or verifying the npm version and Git tag after shipping.

Generate tests for a completed phase based on UAT criteria and implementation

Generate an AI-SPEC.md design contract for phases that involve building AI systems.

Autonomous audit-to-fix pipeline — find issues, classify, fix, test, commit

Audit milestone completion against original intent before archiving

Run all remaining phases autonomously — discuss→plan→execute per phase

Archive accumulated phase directories from completed milestones

Review source files changed during a phase for bugs, security issues, and code quality problems

Use when: an agent needs to debug, inspect, or control a local program from shell commands with dap-cli; trigger for DAP debugging, breakpoints, stack/variables inspection, launch.json debugging, js-debug, debugpy, CodeLLDB, Rust, Chrome debugging, Playwright interop, or poll-then-inspect debug loops. Assumes dap-cli is already on PATH.

Use when: cutting a new dap-cli release to npm. Walks through bumping the version, pushing the tag, and creating the GitHub Release that triggers the publish workflow.

Show available GSD commands and usage guide

Ingest external plans with conflict detection against project decisions before writing anything.

Interactive command center for managing multiple phases from one terminal

Create context handoff when pausing work mid-phase

Create detailed phase plan (PLAN.md) with verification loop

Generate developer behavioral profile and create Claude-discoverable artifacts

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.

Re-import an updated Ancestry GEDCOM into the family-tree site, research the newly-added people, find images and famous-person connections for them, surface data found online that is NOT in the GEDCOM (for porting back to Ancestry), and rebuild/QA the site. Use whenever the owner says they updated/exported a new "Lourens Family Tree.ged", added people on Ancestry, or wants the site refreshed from the latest GEDCOM.