Results for “logback”

Provides Quarkus 3.x architecture patterns for cloud-native, event-driven services with Apache Camel, including REST API design, CDI services, data access with Panache, and async processing.

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.

Turn vague "what did I do?" into evidence-backed impact statements for performance reviews, self-reviews, promotion packets, and weekly updates. Uniquely mines Copilot CLI session logs to reconstruct forgotten work, plus git commits and GitHub PRs. Enforces a 3-part impact contract (action → result → evidence). Works standalone with zero dependencies. Trigger for: "brag", "log work", "what did I do", "backfill my work history", "performance review", "self-review", "self assessment", "write impact statement", "review prep", "promo packet", "promotion case", "weekly update", "status report", "accomplishments", "what did I ship", "I forgot to log my work", "summarize my work", "track my wins", "what should I highlight", "end of half", "career growth", "work journal", or any request to document, summarize, or organize work accomplishments.

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.

Manage Kafka consumer groups on Redpanda with rpk group: list, describe, seek, delete groups, and delete offsets.

debug-logging

Persistent memory CLI for LLM agents. Store facts, recall past knowledge, link related memories, manage lifecycle.

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.

`analysis-agent`/`task-agent`/`review-agent`: use for release identity, compatibility, exposure, stop, rollback, or recovery; skip pipeline-only and no-release work.

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.

Stop re-litigating decisions you already made. Keep a decision record where each entry captures the decision, the context that forced it, the options you weighed, why you chose, and when to revisit, one entry at a time, in plain searchable markdown you can grep later. Trigger on "log this decision", "why did we choose X", "write a decision record", "record why we're doing this", "what did we decide about", or any moment a real call gets made and would otherwise be forgotten.

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)

Streams change data capture from Oracle Database into Redpanda or Kafka using the oracledb_cdc input in Redpanda Connect, which reads redo logs via LogMiner. Covers configuration, Oracle setup, checkpointing, and enterprise features.

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.

Capture structured feedback on the Han skills and agents used in the current session and optionally post it as a GitHub issue to testdouble/han. Use at the end of any session where one or more han-* skills or agents ran, to rate a run, log what worked and what didn't, or submit observations for maintainers. Does not review code, investigate bugs, or research options; use code-review, investigate, or research for those. Does not provide feedback on skills or agents from non-Han plugins.

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.