Menu
Debug Chrome or VSCode extension issues — auth, tools, build, IPC
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when bringing the harness method to a NEW or non-sentropic repo — maps the repo's conventions into a harness profile so the same scope/branch/verify kernel applies anywhere.
Use before any creative/design work (a feature, a package, an evolution) — explores intent and design via the spec-ladder with multi-peer adversarial review BEFORE implementation.
Use on any bug, test failure, or unexpected behaviour BEFORE proposing a fix — runs the generic evidence-first root-cause loop.
Use when you have a spec/decisions and need an executable plan — writes a lot-based BRANCH.md from the template and completes with track for realization state.
Use when completing a feature, a design step, or before merging — runs a ≥2-peer consensus review and reconciles the findings, instead of a single rubber-stamp pass.
Use when adding or evolving tests for a feature/bugfix — applies the sentropic test-pyramid, scoped-test loop, environment isolation, and AI-flaky policy.
| name | debug-extension |
| description | Debug Chrome or VSCode extension issues — auth, tools, build, IPC |
| paths | ui/chrome-ext/**,ui/vscode-ext/** |
| allowed-tools | Read Bash Grep Glob |
make build-ext-chromechrome.storage.local) → session token (.session). JWT decode for expiry. 60s refresh skew.make build-ext-vscodeextension.ts) and webview. RequestId correlation, 10s timeout..env*, .pem, id_rsa, secrets/, .aws/, .ssh/).make up-e2e-vscode ENV=e2e-$BRANCH
make test-e2e-vscode E2E_SPEC=tests/vscode/01-vscode-chat-streaming.spec.ts ENV=e2e-$BRANCH