Loading...
Loading...
Found 20 Skills
Use this agent when you need to understand the historical context and evolution of code changes, trace the origins of specific code patterns, identify key contributors and their expertise areas, or analyze patterns in commit history. This agent excels at archaeological analysis of git repositories to provide insights about code evolution and development patterns. <example>Context: The user wants to understand the history and evolution of recently modified files.\nuser: "I've just refactored the authentication module. Can you analyze the historical context?"\nassistant: "I'll use the git-history-analyzer agent to examine the evolution of the authentication module files."\n<commentary>Since the user wants historical context about code changes, use the git-history-analyzer agent to trace file evolution, identify contributors, and extract patterns from the git history.</commentary></example> <example>Context: The user needs to understand why certain code patterns exist.\nuser: "Why does this payment processing...
Capture architectural decisions and changes made during a GSDL project into a structured markdown document. Analyzes git history and diffs, extracts key decisions, and optionally pushes the doc to Slite or Notion as a child page. Called by the gsdl orchestrator after all implementation tasks are complete.
Search and restore AI conversation context from git history
Use when generating performance hypotheses backed by git history and code evidence.
Analyze how code changed over time. Use when investigating regressions, understanding why code was written a certain way, or finding when a behavior changed.
Use this skill to quickly understand "what changed and what matters". Use when resuming work after absence, preparing handoff documentation, reviewing sprint progress, analyzing git history for context. Do not use when doing detailed diff analysis - use diff-analysis instead. DO NOT use when: full code review needed - use review-core instead.
Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas.
Analyze command history to identify which skills work, which fail, and where to improve.