post-start-validationlisted

# /post-start-validation Run **after completing any task**. Discovers what changed, applies governance gates, captures knowledge, commits and verifies. --- ## 0. Shell Rule Detect OS. Use Git Bash syntax on Windows (forward slashes, /dev/null). --- ## 1. Determine Scope ``` git diff --name-only HEAD 2>/dev/null || git status --short ``` Classify changes by detecting file patterns: - **Frontend?** — `.ts`, `.tsx`, `.js`, `.jsx`, `.css`, `.vue`, `.svelte` files - **Backend?** — `.java`, `.kt`, `.py`, `.go`, `.rs`, `.rb` files - **Infrastructure?** — `Dockerfile`, `docker-compose*`, `k8s/`, `.github/workflows/`, `*.tf` - **Docs-only?** — `.md` files only outside source directories > **Skip rules:** Docs-only → skip code checks. Infra-only → skip local checks. --- ## 2. Read Governance Gates ``` Read .claude/governance.md ``` > The governance file defines which gates to run and in what order. If it specifies "biome → tsc → build" — run exactly that. If it specifies "pytest" — run that. The gates are project-specific; this skill is not. --- ## 3. Run Gates ### 3.0. Workspace-aware gate execution If the discovery cache indicates a workspace: 1. Read root governance gates (from workspace root `.claude/governance.md`) 2. Identify which members have changes: check `git diff --name-only HEAD` paths 3. For changed members with their own governance: read member governance, merge with root gates 4. Execute merged gates in order: root cross-stack gates first, then member-s