verify

Estrellas20

Forks10

Actualizado17 de abril de 2026 a las 14:09

Run this after every code change in this Node project, before committing, before opening a PR, or whenever the user says "verify", "check", "lint", "run tests", "audit". Diff audit (architecture, security, naming, error handling) → lint → tests + coverage gate. Coverage drops → add tests, never lower thresholds. Triggers on "is this ready to commit?", "any issues?", "tests passing?".

Instalación

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.

Ejecutar en Manus

Fuente

pierreb-devkit

pierreb-devkit/Node

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Analistas de garantía de calidad de software y probadoresOcupaciones informáticas y matemáticas·SOC 15-1253

SKILL.md

readonly

name	verify
description	Run this after every code change in this Node project, before committing, before opening a PR, or whenever the user says "verify", "check", "lint", "run tests", "audit". Diff audit (architecture, security, naming, error handling) → lint → tests + coverage gate. Coverage drops → add tests, never lower thresholds. Triggers on "is this ready to commit?", "any issues?", "tests passing?".

Verify Skill

Steps

Diff audit — review all changes (git diff main...HEAD or staged changes) using your knowledge of the stack:
- Read CLAUDE.md and ERRORS.md for conventions, architecture, and known pitfalls
- Read the tasks reference module structure for layer/naming conventions
- Analyze the diff: architecture, security, logic, consistency, error handling
- No hardcoded checklist — reason from context. Examples of what to catch:
  - Routes missing auth/policy middleware
  - Mongoose docs spread without .toObject()
  - Silent error swallowing (catch + console.log)
  - Config in wrong location, missing or orphaned files
  - Cross-module import violations
  - Module-specific logic added to shared files (lib/middlewares/, lib/services/, config/)
  - Module not self-registering its capabilities (subjects, abilities, config)
  - Cross-module dependencies that should use the target module's service instead
  - Inconsistent API response formats
  - Missing null/undefined checks on async returns
- Fix all issues found before proceeding
Lint — npm run lint
Tests + coverage — check if MongoDB is reachable:
- Infra up → npm run test:coverage (all tests + coverage enforcement)
- Infra down → npm run test:coverage -- --testPathPatterns='unit' (unit only + coverage) + warn: "Integration/E2E skipped — run docker compose -f docker-compose.test.yml up -d for full coverage"
- If coverage drops below thresholds (jest.config.js) → fail. Add tests, never lower thresholds.
Summary: ✅ All passed → ready to commit | ❌ Failed → show failures, fix, re-run

Más de este repositorio

mismo repositorio

pull-request

pierreb-devkit/Node

Use this whenever the user asks to "open a PR", "ship this", "create the pull request", "make a PR", or once a feature/fix is verified and ready to push. Full lifecycle: branch → commit (commitizen) → issue → draft PR → CI → ready → autonomous monitor loop (fix comments, resolve threads, iterate until CI green + zero unresolved threads). `--perfect` adds a CodeRabbit convergence loop on top. Never works on `main`/`master`, never uses `--no-verify`.

2026-07-1720

feature

pierreb-devkit/Node

Use this whenever the user asks to "implement", "add", "build", "create", or "modify" a feature, endpoint, API, route, or module in this Node project. Three phases: Phase 0 scope analysis (flows + edge cases + plan validation, STOP for user), Phase 1 implementation (layered Routes → Controllers → Services → Repositories → Models, module-isolated), Phase 2 Definition-of-Done checklist + /verify + /pull-request. Auto-runs /create-module if the target module doesn't exist.

2026-07-1620

update-stack

pierreb-devkit/Node

Use this whenever a downstream Node project needs to absorb upstream Devkit Node changes — triggers on "update stack", "sync with devkit", "merge upstream", "pull stack updates", "resolve stack conflicts". Two-phase: ISO merge (stack modules + lib stay byte-identical to upstream) then project alignment (apply MIGRATIONS.md, diff project modules vs `tasks` reference, /verify). Stack-code failures get an issue on `pierreb-devkit/Node`.

2026-06-1620

create-module

pierreb-devkit/Node

Use this whenever the user asks to "create a module", "scaffold a feature", "add a domain", "new module called X", or starts work on a brand-new vertical (controller + service + repo + model + routes + tests). Duplicates the canonical `modules/tasks` template, applies kebab/Pascal/camel renames, and registers config-driven enums. Module stays self-contained — never modify shared `lib/` or `config/` to bolt on module logic.

2026-04-1720

naming

pierreb-devkit/Node

Use this whenever a new file/folder is created or renamed in this Node project, when reviewing a module for consistency, or when the right path for a file is unclear. Also triggers on "what should I name this?", "is this file named correctly?", "audit module naming". Enforces kebab-case folders, `{module}[.{entity}].{type}.js` files, multi-entity rules, and the layer order Routes → Controllers → Services → Repositories → Models.

2026-04-1720

name	verify
description	Run this after every code change in this Node project, before committing, before opening a PR, or whenever the user says "verify", "check", "lint", "run tests", "audit". Diff audit (architecture, security, naming, error handling) → lint → tests + coverage gate. Coverage drops → add tests, never lower thresholds. Triggers on "is this ready to commit?", "any issues?", "tests passing?".

Verify Skill

Steps

Diff audit — review all changes (git diff main...HEAD or staged changes) using your knowledge of the stack:
- Read CLAUDE.md and ERRORS.md for conventions, architecture, and known pitfalls
- Read the tasks reference module structure for layer/naming conventions
- Analyze the diff: architecture, security, logic, consistency, error handling
- No hardcoded checklist — reason from context. Examples of what to catch:
  - Routes missing auth/policy middleware
  - Mongoose docs spread without .toObject()
  - Silent error swallowing (catch + console.log)
  - Config in wrong location, missing or orphaned files
  - Cross-module import violations
  - Module-specific logic added to shared files (lib/middlewares/, lib/services/, config/)
  - Module not self-registering its capabilities (subjects, abilities, config)
  - Cross-module dependencies that should use the target module's service instead
  - Inconsistent API response formats
  - Missing null/undefined checks on async returns
- Fix all issues found before proceeding
Lint — npm run lint
Tests + coverage — check if MongoDB is reachable:
- Infra up → npm run test:coverage (all tests + coverage enforcement)
- Infra down → npm run test:coverage -- --testPathPatterns='unit' (unit only + coverage) + warn: "Integration/E2E skipped — run docker compose -f docker-compose.test.yml up -d for full coverage"
- If coverage drops below thresholds (jest.config.js) → fail. Add tests, never lower thresholds.
Summary: ✅ All passed → ready to commit | ❌ Failed → show failures, fix, re-run