← ClaudeAtlas

conclude-roundslisted

Conclude the last N rounds of the CURRENT conversation, in Chinese by default, AND hand back 5 evidence-based insights for working more efficiently with Claude Code. Read back over the recent exchanges — both the user's questions AND the assistant's answers, including code written, decisions made, and progress — then give a tight conclusion (what was asked, what was actually done and verified vs merely proposed, current state, open decisions) followed by 5 concrete Claude-Code-usage insights drawn from patterns in those rounds. N defaults to 4 and is read from what the user says (前4轮 / past 3 / 前面5个来回 / 前面两个问题). This is an IN-conversation recap, read-only — it never changes files, and it is NOT a cross-session daily digest. Run whenever the user says 总结前面N轮 / 总结一下前面 / 小结一下 / 结论一下 / 回顾前面几轮 / 前4轮 / 这几轮做了啥 / conclude the last N rounds / recap the last few rounds / summarize what we just did / catch me up on this thread — even without naming the skill. Works identically in Claude Code and Codex.
m1nga/skill-builder · ★ 0 · AI & Automation · score 72
Install: claude install-skill m1nga/skill-builder
# conclude-rounds — conclude the last N rounds of this conversation The user wants to step back and see the recent stretch of THIS conversation clearly: what they asked, what actually got done, and what's still hanging. Everything you need is already in your context — you are not reading transcripts from disk (that would be a cross-session digest, a different job). You are re-reading the last N exchanges you can already see and distilling them. ## What counts as a "round" and how many - A **round** = one real user message + the assistant's reply to it (one Q&A exchange). - Count only genuine user turns — skip system notifications, tool results, and background-task events; they are not the user talking. - **N** defaults to **4**. Take an explicit count from the request and honor its unit: `前4轮`/`past 4` → 4 exchanges; `前面两个问题` → 2; a vague `前面几轮` → judge 3–5 by where a natural topic boundary falls. If fewer than N real rounds exist, conclude what there is and say so. Most recent round is always included. - If earlier context was summarized/compacted, work from the summary for the older rounds and say which rounds are reconstructed vs. read verbatim. ## The one rule that makes this useful: separate done from claimed The reason a recap is worth more than scrolling up is that it tells the truth about STATE. For each thing that happened, sort it honestly: - **已完成且验证过** — done and demonstrated (tests ran, file written, command succeeded, output shown). - **做了但没验证** —