Menú
Audit and improve logging practices. Review logging for a specific feature, audit the entire project, or set up logging infrastructure.
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
Vercel AI SDK expert guidance. Use when building AI-powered features — chat interfaces, text generation, structured output, tool calling, agents, MCP integration, streaming, embeddings, reranking, image generation, or working with any LLM provider.
Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.
Implement a feature. Supports resuming interrupted work and team mode (--team flag). Reads spec/feature/[name]/spec.md and design.md, generates PLAN.md inside the feature directory, waits for user confirmation, then implements and verifies the feature.
Generate or update MSW mock handlers and fixtures from feature spec API contracts. Use to set up mock infrastructure, generate feature-specific mocks, or check mock status.
AI-driven browser testing against feature specs. Default mode reads spec REQs and autonomously tests in a real browser via Playwright MCP. Also supports running existing Playwright test files, visual regression, and accessibility audits.
Check how well the current implementation matches the feature spec and evaluate code quality. Runs spec compliance review followed by code quality review. Optionally runs unit/integration test audit, logging audit, and security audit when strategy files exist. Does not modify code.
| name | log |
| description | Audit and improve logging practices. Review logging for a specific feature, audit the entire project, or set up logging infrastructure. |
| argument-hint | [feature-name] | --audit | --setup |
| context | fork |
Before routing, check if spec/LOG_STRATEGY.md exists:
--setup AND mode is NOT --audit:
→ Output: "No LOG_STRATEGY.md found. Run /log --setup to configure your logging strategy, or /log --audit for a baseline audit." → STOP--setup and --audit modes proceed without strategy file.Parse $ARGUMENTS to determine mode:
--setup: Spawn log-auditor agent (haiku) with:
Set up logging infrastructure for this project.
Ask the user about their logging preferences (library, structured logging, correlation IDs, PII redaction, console.log blocking).
Write the result to spec/LOG_STRATEGY.md.
Provide setup guidance for the chosen library.
If log-analysis skill is not installed, suggest: "npx nextjs-claude-code skill-add log-analysis"
--audit: Spawn log-auditor agent (haiku) with:
Audit logging practices across the entire project.
Generate a project-wide logging health report.
Do not modify any code.
Feature mode (default): Spawn log-auditor agent (haiku) with:
Audit and fix logging for feature: [feature-name from $ARGUMENTS]
Read spec/LOG_STRATEGY.md for rules.
Propose fixes and apply after user confirmation.