Results for “logback”

Provides Quarkus 3.x architecture patterns for building cloud-native, event-driven services with Apache Camel, covering REST APIs, CDI services, data access with Panache, async processing, and logging.

Writes a structured standup update as a session.standup LogEntry — capturing what was done, what is in progress, what comes next, and any blockers. Use when the user says "write a standup", "standup update", "what did I do today", "write a status update for the team", or at the end of a session on projects that run daily standups.

セッション再開時に最新5件のhandoffを読み込み文脈を復元するスキル。「おはよう」「こんにちは」「こんばんは」「再開」「restart」または /resume-session を呼んだ時にトリガーする。new-session の対（読込側）。

Systematic debugging — reproduce, read the error, isolate, hypothesize, fix, verify, document. Use when tracking down a bug, unexpected behavior, or test failure — including phrases like "this doesn't work", "why is this failing", or "help me debug".

Generate a project-level context snapshot for resuming work in a fresh session

Redis in-memory data store. Covers data structures, caching, and pub/sub. Use for caching and real-time features. USE WHEN: user mentions "redis", "caching", "session storage", "rate limiting", "pub/sub", "sorted sets", "in-memory database", "cache invalidation" DO NOT USE FOR: relational data - use `postgresql` or `mysql` instead, document storage - use `mongodb` instead, full-text search - use `elasticsearch` instead

Retro

Generic webapp QA fallback — use only when no project-specific QA skill applies (project-local QA wins; native builds → mobile-emulator-test). Use when "QA the app", "test CRUD", or "smoke test". Monkey / guest vs logged-in → test-exploratory. Dead buttons → plan-stub-checker. Pixel diffs → test-visual-regression.

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

Close a work session without losing what just happened. Write a handoff brief that captures progress, the decisions you made, the unfinished items and their next steps, and the details that would evaporate overnight, then it asks whether to commit or save it, never automatically. Trigger on "wrap up this session", "write a handoff", "close out for the day", "hand this off", "what did we get done", or the end of any working session you might have to resume later.

debug-logging

Search and analyze your own session logs (older/parent conversations) using jq.

Weekly engineering retrospective. (gstack)

Search and analyze your own session logs (older/parent conversations) using jq.

Search and analyze your own session logs (older/parent conversations) using jq.

Write an end-of-session handover LogEntry capturing current state, open threads, next action, and git context for session continuity.

A runbook written in a wiki decays silently: the dashboard is renamed, the

当遭遇挫折、失败或结果不如预期时，用于将负面经验转化为成长燃料

Use when investigating a bug, runtime error, unexpected behavior, test failure, or crash. For systematic root cause analysis, error message interpretation, stack trace reading, reproduction steps, and targeted fixes. Activate when the user says "it's broken", "this doesn't work", "I'm getting an error", or "help me debug".

Weekly engineering retrospective. (gstack)

Imported skill history from langchain

Diagnose your own behavior by reading the structured logs you leave behind — turns.jsonl, events.jsonl, chat_history.jsonl, scheduler.yaml. Use when something has gone wrong (a message didn't land, a scheduled job isn't firing, a communication pattern feels off), when you need to understand a pattern over many turns, or when cost / token usage needs auditing. Covers jq query recipes and points at the debugging-jobs / debugging-communication / debugging-drift companion guides for specific failure modes.

Facilitate a structured sprint retrospective to surface insights and produce actionable improvements with owners and deadlines.

Close out a work session safely. Verifies every change is committed, pushed, and green, confirms the work is live and verified, updates the notes for next time, and hands back a summary with links and a rollback path. Trigger on "close out the session", "wrap up", "lock it up", "are we good to close", "session QA", "end of session", or any moment before you stop or hand off.

Save the current diagnosis state to disk for cross-session recall, including conclusions, rejected directions, and next steps.

週次リフレクション（1週の振り返りサマリ）を生成するスキル。直近の完了週の日記から4要素（作業傾向/思考癖/繰り返す課題/CCアドバイス）を生成し、_INDEX気づきTop3はユーザー承認後に反映。ユーザーが「リフレクション」「今週の振り返り」「思考癖まとめて」と言った時、または /reflection を呼んだ時に発動。resume-sessionの検知提案からも起動される。

Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.

Codify the most recent successful /scrape flow into a permanent browser-skill on disk. (gstack)

Restore working context saved earlier by /context-save. (gstack)

Runs a full retrospective and dev cycle analysis, chaining /recall and /new-features to reconstruct what went wrong, extract lessons learned, identify rework patterns, and synthesize feature ideas from the findings.

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