Results for “dev-log”

Node.js logging with Winston, Pino, and built-in console. Covers structured logging, log levels, transports, async logging, and production best practices for Express/NestJS applications. USE WHEN: user mentions "node.js logging", "express logging", "nestjs logging", asks about "how to log in node", "winston vs pino", "node logging best practices" DO NOT USE FOR: Python logging - use `python-logging` instead, Java logging - use `slf4j` or `logback`, Browser logging - different environment and APIs

Python logging with the standard library logging module and structlog. Covers log levels, handlers, formatters, structured logging, and production best practices for FastAPI/Django applications. USE WHEN: user mentions "python logging", "fastapi logging", "django logging", asks about "how to log in python", "python logging module", "logging configuration python" DO NOT USE FOR: Node.js logging - use `nodejs-logging` instead, Java logging - use `slf4j` or `logback`, structlog-specific - use `structlog` skill for deep dive

Surface and clarify unknowns before prompting, log deviations during implementation, and verify understanding after, using HTML artifacts that pair prompts with outputs.

Logback - flexible and powerful logging framework for Java and Spring Boot applications. Successor to Log4j with native SLF4J support, async logging, and automatic file rotation. USE WHEN: user mentions "logback", "spring boot logging", "java logging configuration", asks about "logback-spring.xml", "rolling file appender", "async logging in java" DO NOT USE FOR: SLF4J API usage - use `slf4j` instead, Log4j2 - use separate Log4j2 skill, Node.js logging - use `winston` or `pino` instead, Python logging - use `python-logging` instead

Automates browser testing and interaction with Playwright, including form filling, screenshots, responsive checks, and login flows, with automatic dev server detection.

Winston - versatile logging library for Node.js with multiple transports, custom formatting, and log rotation. Supports structured logging, custom levels, and enterprise integration. USE WHEN: user mentions "winston", "node.js logging", "multiple transports", "log rotation", asks about "how to log to multiple destinations", "rotate log files in Node.js", "custom log formats" DO NOT USE FOR: Pino logging - use `pino` instead, Python logging - use `python-logging` instead, Java logging - use `slf4j` or `logback` instead

Automates browser interactions and testing with Playwright, including form filling, screenshots, responsive checks, and login flows, with automatic dev server detection.

Pino - extremely fast and low overhead Node.js logger with JSON-native structured logging. 10x faster than Winston. Optimized for high-performance APIs and production environments. USE WHEN: user mentions "pino", "fast logging", "high performance logging", "fastify logging", asks about "fastest node.js logger", "JSON structured logging", "low overhead logging" DO NOT USE FOR: Winston logging - use `winston` instead, Python logging - use `python-logging` instead, Complex transport requirements - use `winston` instead

Unified Diary System: A context-preserving automated logger for multi-project development.

Unified Diary System: A context-preserving automated logger for multi-project development.

Unified developer workflow for fixing bugs. Analyzes issue-tracker context, cross-checks docs/code, proposes a solution, implements the fix, verifies locally, and delivers a PR/MR.

Unified Diary System: A context-preserving automated logger for multi-project development.

Investigate a problem, log it to the debug changelog, cross-check past issues, and suggest a non-duplicate fix.

debug-logging

Automatically log daily development progress, archive project-specific diaries locally, and sync a fused global diary to Notion or Obsidian.

Audits a project's developer experience by scoring devcontainer, git hooks, linting, build caching, environment setup, and release pipeline, then generates a DX health report with prioritized recommendations.

Unified Diary System: A context-preserving automated logger for multi-project development.

Unified Diary System: A context-preserving automated logger for multi-project development.

コード品質改善の全サイクルを実行するスキル。品質スイープ→コードレビュー→Issue化→自律実装ループ→完了通知の5フェーズ。ユーザーが「dev-cycle」「開発サイクル」「品質改善」「自律ループ」などと言った時、または /dev-cycle を呼び出した時にトリガーする。

Diagnose Apex behavior with debug logs, structured production logging, and async job monitoring, replacing ad-hoc System.debug habits with durable, queryable observability.

Turn engineering work into evidence-backed impact statements for performance reviews, self-reviews, promotion packets, and weekly updates by mining Copilot CLI session logs, git history, and GitHub PRs.

Analyzes git commit history and generates structured changelogs categorized by change type.

Generates a single unified changelog from git history, written in plain language for the whole company, defaulting to Slovak and comparing the release branch against develop for unreleased changes.

Live developer experience audit. Uses the browse tool to actually TEST the developer experience: navigates docs, tries the getting started flow, times TTHW, screenshots error messages, evaluates CLI help text. Produces a DX scorecard with evidence. Compares against /plan-devex-review scores if they exist (the boomerang: plan said 3 minutes, reality says 8). Use when asked to "test the DX", "DX audit", "developer experience test", or "try the onboarding". Proactively suggest after shipping a developer-facing feature. (gstack) Voice triggers (speech-to-text aliases): "dx audit", "test the developer experience", "try the onboarding", "developer experience test".

Summarize each day's Git activity into a concise daily work log, for a single date or a range. Uses the current repository, optional configured work projects, or paths named in conversation; configuration is never required.

Unified Diary System: A context-preserving automated logger for multi-project development.

Use only for developer-facing products; plan adoption loops, examples, templates, community, and proof artifacts

Iterates through pending development plans in .cursor/plans, implementing tasks, running self-tests, reviewing code, committing locally, and moving completed plans to docs/plans/done.

Generate user-facing or internal release notes and changelogs. Load when the user prepares a release, tags a version, or wants to summarize recent progress. Also triggers on "write a changelog", "prepare release notes", "what's new in this version", "summarize my commits", or "create a release summary". Auto-triggered by library-skill after major repo changes (new skills added, skills renamed, structure changes). Applicable to any project, including this skill library itself.

Unified Diary System: A context-preserving automated logger for multi-project development.