Menú
Full quality check — formatting, static analysis, dead code, flake validation, and skill pin verification.
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
| name | audit |
| description | Full quality check — formatting, static analysis, dead code, flake validation, and skill pin verification. |
| metadata | {"when_to_use":"audit, lint, format, check quality, verify dotfiles, run checks"} |
Run in order; stop and fix if any step fails.
just fmtdeadnix -o .statix check .just check (or just check --keep-going for skip-on-failure)grep -A4 '"disko"' flake.lock | grep narHash| Tool | Catches |
|---|---|
nixfmt | Formatting violations |
deadnix | Unused let bindings, dead code |
statix | with anti-patterns, inefficient list ops, redundant rec |
flake-checker | Outdated/unpinned flake inputs |
nix flake check | Eval errors, broken modules, failed assertions, VM test failures |
just check builds ISO + VM tests on x86_64 — 30+ minutes first run. Use --keep-going for partial.deadnix may flag bindings used only in commented-out code/conditionals — verify before deleting.just check --keep-going --show-trace
All git-tracked files must remain unchanged after formatting.
After `nix flake update`, sync `input_rev` and `input_hash` metadata in all flake-input skill files to match new `flake.lock`.
Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.
Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured.
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.
Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.