What problem does it solve? After finishing a bug fix or feature, developers often lose the reasoning, failed attempts, and validation details scattered across long AI conversations and multiple Git branches. This Skill consolidates that context into a complete, well-structured Markdown summary document. ## Core Features & Use Cases - Multi-source summarization: Combines conversation history with Git branch or commit diffs (single or multi-repository), writing the development narrative first and keeping branch/commit details as appendices. - Coverage auditing: Scans both user questions and agent answers to extract derived questions, trade-offs, risks, and boundaries, then deduplicates them via a coverage matrix before writing. - Business Q&A and knowledge archiving: Archives project-specific business questions into matched existing documents (with classification protection for legacy content) and routes reusable technical knowledge into categorized knowledge files. - Optional Git integration: Detects the documentation repository after writing and can commit and push only the generated summary file. - Use Case: After finishing a cross-repo feature, say "总结这些分支并带上对话" to get a complete summary covering requirements, solutions, pitfalls, test notes, and commit messages, saved to your docs folder and optionally pushed. ## Quick Start Ask the agent to summarize the bug or feature just completed in this conversation, optionally naming specific branches or commits to include their diffs.