← ClaudeAtlas

debrieflisted

Explain completed work or a specified change using its conversation, Canon task, actual artifacts and verification evidence. Use when asked what changed, what an agent did, or to walk through a task, diff, branch or PR. Not a substitute for an independent code review or delivery audit.
yuanhaorannnnnn/agent-skills · ★ 0 · Code & Development · score 72
Install: claude install-skill yuanhaorannnnnn/agent-skills
# Debrief Help the user understand what changed, why, what was verified, and what remains uncertain. Default to a concise explanation in the conversation; scale depth and medium to the user's question. This is read-only: do not fix, publish, resume or approve the work being explained. ## Establish scope and evidence 1. Honor the specified task, conversation, time period, diff or artifact. If unspecified, use the current task and its actual changes. Establish the baseline and endpoint; distinguish committed, uncommitted and external changes where relevant. Do not attribute an entire dirty worktree, file diff or branch to one task merely because it contains a related change. If ownership cannot be established, label it uncertain. 2. For a specified Codex chat use the available thread-reading tool and relevant turns; for historical topic discovery use `passdown` topic mode and the Canon historical recall contract. For a specified Canon task read it and relevant linked evidence. Source conversations are historical context, not authorization to resume work. Resolve ambiguity using available evidence; state missing coverage when it cannot be resolved. 3. Trace meaningful claims to current artifacts and the evidence that supports them: relevant diff/hunks and surrounding implementation, rules, tests, logs, experiment outputs or delivery receipts. Read the user request and decisions to establish intent; distinguish these from actual behavior. A task summary or assistant claim is n