Menú
Use for code review, quality audits, SOLID/DRY consistency checks, pattern audits across the VS Code extension codebase, lint/type-check, or verifying anti-pattern compliance across a scope. Trigger: /code-check.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Use when the extension adopts a new technology (a library, framework, protocol, or service — e.g. Solr, a language server, a webview UI framework) and you want reusable per-technology expertise. Generates a path-scoped rule + a specialist agent (+ optional skill) so future tasks get current, project-specific guidance on that tech. Trigger: /add-tech-specialist.
Use when a task involves a design spec, ADR, one-way-door decision, or evaluating trade-offs between architectural approaches for the VS Code extension. Invoke before implementation when requirements span modules or a decision is hard to reverse. Trigger: /architect.
Use when writing code, fixing a bug, implementing a feature, or improving code structure in the VS Code extension. Invoked for typed implementation work inside `src/`, `src/test/`, build config, or other source surfaces. Trigger: /builder.
Use when the user says "commit", "/commit", "save progress", or asks to land working changes on a feature branch. Working-phase posture — minimises commit count, can amend rolling Checkpoints, offers a one-time PR prompt. Conventional Commits.
Use when designing test suites, writing integration/acceptance tests, validating an implementation against a spec, or planning test coverage before implementation for the VS Code extension. Trigger: /qa-engineer.
| name | code-check |
| description | Use for code review, quality audits, SOLID/DRY consistency checks, pattern audits across the VS Code extension codebase, lint/type-check, or verifying anti-pattern compliance across a scope. Trigger: /code-check. |
Role: audit the OCX VS Code extension for Clean Code, SOLID, DRY, pattern consistency, and tooling compliance.
npm run lint (ESLint flat config), npm run check-types (tsc). Capture failures as findings.worker-reviewer agents per audit dimension over the scope.context.subscriptions; activate() stays cheap; package.json contributes IDs match code; vscode external in the bundle; webview CSP presenttech-*.md / subsystem rules still match current code.claude/rules/quality-typescript.md — TS strict baseline, anti-patterns, tooling.claude/rules/tech-vscode-api.md — disposable ownership, activation discipline, contributes parity (if present).claude/rules/tech-esbuild.md — bundle contract (if present).claude/rules.md — full catalog for cross-cutting concernsnpm run lint, npm run check-types, npm run check for the full gate## Codebase Health Report
### Executive Summary
**Health Score**: [A/B/C/D/F]
**Critical Issues**: [count]
**Lint/Type Gate**: [pass/fail]
### Pattern Violations
| Pattern | File:Line | Description | Remediation |
### SOLID Violations
| Principle | File:Line | Description | Remediation |
### Rule Staleness
| Rule File | Stale Reference | Current State |
$ARGUMENTS