incident-debrief

Post-incident LEARNING debrief for an infrastructure engineer growing their skills. Use when the user, after an incident or debugging session is resolved, asks to walk through what happened, how the investigation went, what the agent did and why, what the dead ends were, what they should learn, or says things like "explain what you did", "debrief me", "teach me from this incident", "how did you figure that out". Also use when the user points to a recent incident-log-*.md from the incident-response skill and asks for debrief or learning review. This is NOT root cause analysis or a formal postmortem document; the deliverable is the user's improved debugging skill.

Ir para a instalação

Repositório: delicb/dotfiles
Última atividade na origem: 7 de julho de 2026 às 21:58
Idioma detectado do SKILL.md: inglês
Estrelas: 0
Forks: 0

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/delicb/dotfiles --skill incident-debrief

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

incident-response

Live production incident investigation mode for infrastructure engineers. Use only when the user explicitly asks you to handle, investigate, or respond to an incident, or explicitly invokes the incident-response skill. Do not trigger only because the user reports a production issue, alert, error, stack trace, slow service, failed workload, or other incident-like signal.

2026-07-30

finicky-config

Interpret, explain, write, and update Finicky v4 configuration for macOS URL routing. Use when working with ~/.finicky.js or ~/.finicky.ts, reading an existing Finicky setup, authoring rewrite or handler rules, choosing browsers or profiles, debugging rule order, or migrating routing logic into Finicky.

2026-06-29

work-on

Work on a Linear issue by ID. Fetch issue details, classify it as a bug, task, or unclear request, gather the right context, create the Linear branch from latest master, implement simple changes, and verify with tests, lint, and typecheck. Bugs require root cause analysis and production evidence when useful. Tasks require clarified requirements, acceptance criteria, constraints, and tradeoffs.

2026-05-29

Ver todas deste repositório

Incident Debrief (learning mode)

The user is an infrastructure engineer building fluency with their systems and observability stack. An incident just ended. Turn the investigation into a teaching session. The output is understanding in the user's head, not a document for stakeholders. Do not produce a formal postmortem, action items, or blameless-RCA boilerplate unless explicitly asked.

Source material

In priority order:

A timestamped incident-log-*.md written by the incident-response skill during the incident. Look in the working directory and ~/.local/state/incident-logs/ if the user did not provide a path. If multiple logs exist, ask which one to use. Do not assume a stale log is the current incident.

The current conversation history, if the investigation happened in this session.

The user's own account. If neither log nor history exists, interview them briefly: what was the signal, what did they check, in what order, what did they conclude. Then debrief their process the same way you would your own.

Ground every claim in this material. If you cannot reconstruct why a step was taken, say so plainly instead of inventing a retroactive rationale. A debrief that rewrites history teaches the wrong lessons.

Debrief structure

Walk through these five parts in order. Conversational prose, not a wall of headers. Keep each part tight; depth goes where the user asks questions.