logging — for Claude Code logging, BrainBox_v2, community, for Claude Code, ide skills, logger.ts, DEBUG_MODE=false, check-env.js, logger.error, check-shared-ui

v1.0.0

Acerca de este Skill

Escenario recomendado: Ideal for AI agents that need rules (non-negotiable). Resumen localizado: logging helps AI agents handle repository-specific developer workflows with documented implementation details.

Características

Rules (non-negotiable)
Zero console.log/error/warn/debug in source code — use logger.ts only
DEBUG MODE=false in production — enforced by check-env.js
Every phase MUST create an INDEX.json entry before starting
Every async error path MUST log via logger.error

# Core Topics

HackamViGo HackamViGo
[0]
[0]
Updated: 3/27/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 8/11

This page remains useful for teams, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution
Review Score
8/11
Quality Score
49
Canonical Locale
en
Detected Body Locale
en

Escenario recomendado: Ideal for AI agents that need rules (non-negotiable). Resumen localizado: logging helps AI agents handle repository-specific developer workflows with documented implementation details.

¿Por qué usar esta habilidad?

Recomendacion: logging helps agents rules (non-negotiable). logging helps AI agents handle repository-specific developer workflows with documented implementation details.

Mejor para

Escenario recomendado: Ideal for AI agents that need rules (non-negotiable).

Casos de uso accionables for logging

Caso de uso: Applying Rules (non-negotiable)
Caso de uso: Applying Zero console.log/error/warn/debug in source code — use logger.ts only
Caso de uso: Applying DEBUG MODE=false in production — enforced by check-env.js

! Seguridad y limitaciones

  • Limitacion: Zero console.log/error/warn/debug in source code — use logger.ts only
  • Limitacion: Every phase MUST create an INDEX.json entry before starting
  • Limitacion: Every async error path MUST log via logger.error

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.
  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is logging?

Escenario recomendado: Ideal for AI agents that need rules (non-negotiable). Resumen localizado: logging helps AI agents handle repository-specific developer workflows with documented implementation details.

How do I install logging?

Run the command: npx killer-skills add HackamViGo/BrainBox_v2/logging. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for logging?

Key use cases include: Caso de uso: Applying Rules (non-negotiable), Caso de uso: Applying Zero console.log/error/warn/debug in source code — use logger.ts only, Caso de uso: Applying DEBUG MODE=false in production — enforced by check-env.js.

Which IDEs are compatible with logging?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for logging?

Limitacion: Zero console.log/error/warn/debug in source code — use logger.ts only. Limitacion: Every phase MUST create an INDEX.json entry before starting. Limitacion: Every async error path MUST log via logger.error.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add HackamViGo/BrainBox_v2/logging. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use logging immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

logging

Install logging, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Rules (non-negotiable)

  • Zero console.log/error/warn/debug in source code — use logger.ts only
  • DEBUG_MODE=false in production — enforced by check-env.js
  • Every phase MUST create an INDEX.json entry before starting
  • Every async error path MUST log via logger.error
  • Log files are append-only — never overwrite
  • Filesystem MCP MUST be used for running enforcement scripts (like check-shared-ui or check-boundaries) and to perform log file writes in ops/logs.

Patterns

logger.ts API (packages/shared/src/utils/logger.ts)

typescript
1import { logger } from '@/lib/logger' // web-app 2import { logger } from '@/lib/logger' // extension (re-export from shared) 3 4logger.debug('ModuleName', 'Short message', { context: data }) 5logger.info('ModuleName', 'Something happened') 6logger.warn('ModuleName', 'Possible issue', details) 7logger.error('ModuleName', 'Failed to do X', error)

logger.ts implementation

typescript
1// packages/shared/src/utils/logger.ts 2const DEBUG = typeof process !== 'undefined' 3 ? process.env['DEBUG_MODE'] === 'true' 4 : false 5 6type Level = 'debug' | 'info' | 'warn' | 'error' 7 8function log(level: Level, module: string, message: string, data?: unknown): void { 9 if (level === 'debug' && !DEBUG) return 10 const entry = { ts: new Date().toISOString(), level, module, message, ...(data ? { data } : {}) } 11 if (level === 'error') { 12 // In production: send to telemetry (Sentry etc.) 13 // In development: console.error is allowed only here 14 if (DEBUG) console.error(JSON.stringify(entry)) 15 } else { 16 if (DEBUG) console.log(JSON.stringify(entry)) 17 } 18} 19 20export const logger = { 21 debug: (m: string, msg: string, d?: unknown) => log('debug', m, msg, d), 22 info: (m: string, msg: string, d?: unknown) => log('info', m, msg, d), 23 warn: (m: string, msg: string, d?: unknown) => log('warn', m, msg, d), 24 error: (m: string, msg: string, d?: unknown) => log('error', m, msg, d), 25}

Phase logging — ops/logs/INDEX.json schema

json
1{ 2 "version": "1.0", 3 "last_updated": "ISO timestamp", 4 "logs": [ 5 { 6 "id": "LOG-001", 7 "name": "monorepo-scaffold", 8 "phase": "PHASE-1", 9 "file": "ops/logs/LOG-001-monorepo-scaffold.log", 10 "status": "running", 11 "started_at": "ISO timestamp", 12 "completed_at": null, 13 "summary": null, 14 "mcp_gate": null 15 } 16 ] 17}

mcp_gate when applicable:

json
1"mcp_gate": { "result": "pass", "notes": "Extension syncs to Web App", "timestamp": "ISO" }

update-log.js commands

bash
1node scripts/update-log.js start LOG-001 "monorepo-scaffold" "PHASE-1" 2node scripts/update-log.js log LOG-001 info "Creating pnpm-workspace.yaml" 3node scripts/update-log.js log LOG-001 warn "Node version mismatch, continuing" 4node scripts/update-log.js finish LOG-001 "7 packages created, 0 errors" 5node scripts/update-log.js fail LOG-001 "pnpm install failed — missing peer dep" 6node scripts/update-log.js mcp-gate LOG-001 "pass" "Auth verified in real browser" 7node scripts/update-log.js status # human-readable phase overview

Log file format

[2026-03-18T10:00:00Z] [START] PHASE-1 monorepo-scaffold
[2026-03-18T10:00:01Z] [INFO] Creating pnpm-workspace.yaml
[2026-03-18T10:00:05Z] [WARN] Node version mismatch — continuing
[2026-03-18T10:00:08Z] [SUCCESS] pnpm install — 0 errors
[2026-03-18T10:00:11Z] [COMPLETE] monorepo-scaffold — 7 packages, 0 errors

Levels: START INFO WARN ERROR SUCCESS COMPLETE SKIP

Anti-patterns (forbidden)

typescript
1console.log('data:', data) // use logger.info 2console.error('failed:', err) // use logger.error 3console.debug(...) // use logger.debug 4// skipping log entry for a phase // always update-log.js start first 5catch (_) {} // always logger.error in catch

Verification checklist

  • Zero console.* calls in source (run pnpm check:boundaries)
  • logger.ts imported from @brainbox/shared or @/lib/logger
  • Every phase has update-log.js start called before work begins
  • Every async error path has logger.error call
  • DEBUG_MODE=false in .env.production

Habilidades relacionadas

Looking for an alternative to logging or another community skill for your workflow? Explore these related open-source skills.

Ver todo

openclaw-release-maintainer

Logo of openclaw
openclaw

Resumen localizado: 🦞 # OpenClaw Release Maintainer Use this skill for release and publish-time workflow. It covers ai, assistant, crustacean workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

333.8k
0
Inteligencia Artificial

widget-generator

Logo of f
f

Resumen localizado: Generate customizable widget plugins for the prompts.chat feed system # Widget Generator Skill This skill guides creation of widget plugins for prompts.chat . It covers ai, artificial-intelligence, awesome-list workflows. This AI agent skill supports Claude Code, Cursor, and

149.6k
0
Inteligencia Artificial

flags

Logo of vercel
vercel

Resumen localizado: The React Framework # Feature Flags Use this skill when adding or changing framework feature flags in Next.js internals. It covers blog, browser, compiler workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

138.4k
0
Navegador

pr-review

Logo of pytorch
pytorch

Resumen localizado: Usage Modes No Argument If the user invokes /pr-review with no arguments, do not perform a review . It covers autograd, deep-learning, gpu workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

98.6k
0
Desarrollador