timeline-report 是做什么的？
生成一份“深入 [项目] 之旅”叙事报告，通过 claude-mem 的时间线分析项目的完整开发历史。适用于当被请求时间线报告、项目历史分析、开发历程或全面项目报告时。
生成一份“深入 [项目] 之旅”的叙事报告，通过 claude-mem 的时间线分析项目的完整开发历史。适用于当被请求时间线报告、项目历史分析、开发历程或全面项目报告时。
该技能基于 claude-mem 记录的时间线数据，生成一份详细的“深入 [项目] 之旅”叙事报告，帮助开发者全面了解项目的开发历程。它能够自动提取时间线中的关键事件、里程碑和模式，以故事化的方式呈现项目的演进过程，而非简单的日志列表。这份报告对于新成员快速上手项目、回顾团队工作或进行项目复盘尤为有用。该技能支持任何使用 claude-mem 进行时间线记录的项目，并且与多种 AI 代理平台兼容。通过分析时间线中的提交、讨论和决策点，它能生成结构化的报告，突出技术演进、挑战应对和团队协作中的亮点。
npx skills add https://github.com/thedotmack/claude-mem/tree/main/skills/timeline-reportInstalled? Explore more 研究与数据分析 skills: affaan-m/uspto-database, affaan-m/scholar-evaluation, affaan-m/literature-review · View all 6 →
生成一份“深入 [项目] 之旅”叙事报告，通过 claude-mem 的时间线分析项目的完整开发历史。适用于当被请求时间线报告、项目历史分析、开发历程或全面项目报告时。
This repo contains 11 individual skills — each has its own dedicated page.
Watch a pull request or review cycle until it is ready to merge. Use when asked to babysit, monitor, or keep checking PR comments, reviews, and CI until all actionable issues are resolved.
Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging, GitHub releases, and changelog generation. NPM publishing (so `npx [email protected]` resolves) is handed off to the human maintainer, who raised npm security.
Execute a phased implementation plan using subagents. Use when asked to execute, run, or carry out a plan — especially one created by make-plan.
Explain how claude-mem captures observations, when memory injection kicks in, and where data lives. Use when the user asks "how does claude-mem work?" or "what is this thing doing?".
Build and query AI-powered knowledge bases from claude-mem observations. Use when users want to create focused "brains" from their observation history, ask questions about past work patterns, or compile expertise on specific topics.
Prime a codebase by reading every source file in full. Use when starting work on a new or unfamiliar project, or when the user asks to "learn the codebase", "read the codebase", "prime", or "get up to speed".
Create a detailed, phased implementation plan with documentation discovery. Use when asked to plan a feature, task, or multi-step implementation — especially before executing with do.
Search claude-mem's persistent cross-session memory database. Use when user asks "did we already solve this?", "how did we do X last time?", or needs work from previous sessions.
Map a codebase into feature-grouped flowcharts, identify duplicated concerns across features, and propose a unified architecture. Use when asked to "find the ideal path," unify duplicated systems, or audit architecture before a refactor. Emits a proposed unified flowchart plus per-system /make-plan prompts.
Token-optimized structural code search using tree-sitter AST parsing. Use instead of reading full files when you need to understand code structure, find functions, or explore a codebase efficiently.
Turn one document into a kawaii NotebookLM slide-deck PDF. Use for "wowerpoint this", "make a deck about <file>", "turn this report into slides", or any request to render a single document as shareable narrative slides.
USPTO patent and trademark data workflow for official record lookup, PatentSearch queries, TSDR checks, assignment data, and reproducible IP research logs.
Structured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback.
Systematic literature-review workflow for academic, biomedical, technical, and scientific topics, including search planning, source screening, synthesis, citation checks, and evidence logging.
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Agent skill repository discovered by 10x-chat research.
Review backend code for quality, security, maintainability, and best practices based on established checklist rules. Use when the user requests a review, analysis, or improvement of backend files (e.g., `.py`) under the `api/` directory. Do NOT use for frontend files (e.g., `.tsx`, `.ts`, `.js`). Supports pending-change review, code snippets review, and file-focused review.