一键导入
donegraph-recap
One-click session recap. AI-analyzes git history, runs checks, and generates a visual dashboard with narrative story, insights, and risks.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
One-click session recap. AI-analyzes git history, runs checks, and generates a visual dashboard with narrative story, insights, and risks.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
AI Accountability Infrastructure. Use /donegraph-recap to auto-summarize what this session accomplished with a visual dashboard, or use sub-commands to track progress step by step.
Automatically capture local project context into a clean-room DoneGraph collaboration graph.
Record a meaningful DoneGraph progress checkpoint for the current AI collaboration.
Build and open the local DoneGraph dashboard for the current project.
Record a DoneGraph completion milestone and regenerate handoff artifacts.
Record verification evidence in DoneGraph, including pass, fail, blocked, or unknown status.
| name | donegraph-recap |
| description | One-click session recap. AI-analyzes git history, runs checks, and generates a visual dashboard with narrative story, insights, and risks. |
| argument-hint | ["[--last <n>] [--since <time>] [--lang en|zh]"] |
Generate an AI-powered visual recap of the current working session.
Run these commands and read the output:
git log --oneline -20
git diff --stat HEAD~5 2>/dev/null || git diff --stat
Based on the git output, write your analysis to .donegraph/analysis.json in this exact format:
{
"version": "1",
"summary": "One-sentence summary of what this session accomplished",
"story": "A 2-3 sentence narrative telling the story of this work session — what problem was tackled, how it was approached, and what the outcome was. Write like a thoughtful colleague summarizing the day, not like a changelog.",
"items": [
{
"title": "Short title of what was done",
"detail": "Why this matters or what it achieved",
"type": "goal|decision|action|artifact|verification|completion",
"status": "pass|fail|unknown"
}
],
"risks": ["Any risks or concerns spotted in the changes"],
"insights": ["Non-obvious observations about the work pattern or code quality"],
"next_steps": ["What should happen next based on this session"]
}
Guidelines for writing the analysis:
items should be 5-10 meaningful events, NOT one per commit — group related commits into logical stepsstory should be warm and human, not mechanical — tell what happened and why it mattersrisks should flag real concerns (missing tests, breaking changes, security implications), not generic warningsinsights should be genuinely useful observations (patterns, architecture decisions, quality trends)type: "goal" for the first item, type: "completion" for the last, and appropriate types in between../../scripts/donegraph recap --analysis .donegraph/analysis.json --lang en $ARGUMENTS
This will:
Use this when the user says any of: