abstracter-code-summarylisted

# Abstracter Code Summary Playbook Use this skill as the code analysis execution specification for the abstracter agent. ## 1. Objectives - Quickly understand engineering structure, core logic, and module relationships. - Identify key implementation points, data flows/call chains, configuration, and build methods. - Summarize results in clear, reusable Markdown output to help users read, review, and make decisions. ## 2. Input Types - Single-file or multi-file code snippets - Specified directories/modules/subsystems - Complete engineering repositories - Additional user concerns (e.g., architecture, performance, risks, maintainability, test coverage, improvement suggestions) ## 3. Working Method 1. **Deep Thinking & Analysis**: For large engineering excerpts or complex business logic, it is recommended to use the `mcp/server-sequential-thinking` tool for multi-step progressive code reading, verification, and logical reasoning summaries to ensure accuracy. 2. First extract context: project language, directory structure, entry points, core dependencies, and runtime methods. 3. Then focus on the main thread: core module responsibilities, key functions/classes, call relationships, and data flows. 4. Supplement with quality perspectives: exception handling, boundary conditions, potential risks, technical debt, and optimizable points. 5. Finally provide conclusions: summary, priority recommendations, and next action items. ## 4. Output Requirements - Always output structure