Structured method for quickly understanding recent changes in git repositories, meeting notes, sprint progress, document revisions, or system logs. Answers "what changed and what matters?" efficiently.
/plugin marketplace add athola/claude-night-market/plugin install imbue@claude-night-marketThis skill inherits all available tools. When active, it can use any tool Claude has access to.
modules/document-analysis-patterns.mdmodules/git-catchup-patterns.mdmodules/log-analysis-patterns.mdStructured method for quickly understanding recent changes in git repositories, meeting notes, sprint progress, document revisions, or system logs. Answers "what changed and what matters?" efficiently.
Keywords: catchup, summary, status, progress, context, handoff Cues: "get me up to speed", "current status", "summarize progress"
Load modules based on context:
Git: Load modules/git-catchup-patterns.md for git commands. Consider sanctum:git-workspace-review for initial data gathering.
Documents/Notes: Load modules/document-analysis-patterns.md for meeting notes, sprint tracking, document revisions.
Logs/Events: Load modules/log-analysis-patterns.md for time-series and metric analysis.
Always Available: imbue:evidence-logging, TodoWrite workflow, structured output.
catchup:context-confirmed - Boundaries establishedcatchup:delta-captured - Changes enumeratedcatchup:insights-extracted - Themes identifiedcatchup:followups-recorded - Actions capturedDefine scope (git branch, sprint, meetings), baseline (last state), and current target. See modules for commands.
Enumerate changed items with metrics. Prioritize source/config/docs over generated artifacts. See modules for strategies.
Per item: What (change), Why (motivation), Implications (tests/risks/deps). Rollup into themes.
Capture: Tests, Documentation, Reviews, Blockers, Questions. If none, state explicitly.
## Summary
[2-3 sentence theme + risk overview]
## Key Changes
- [Item]: [what/why/implication]
## Follow-ups
- [ ] [Action with owner]
## Blockers/Questions
- [Item requiring resolution]
Verification: Run the command with --help flag to verify availability.
Use imbue:diff-analysis for risk assessment, imbue:evidence-logging for reproducibility, sanctum:git-workspace-review for git data. Feed to brainstorming or writing-plans as needed.
Reference paths + lines (don't reproduce). Summarize outputs. Defer deep analysis. Use progressive loading.
Command not found Ensure all dependencies are installed and in PATH
Permission errors Check file permissions and run with appropriate privileges
Unexpected behavior
Enable verbose logging with --verbose flag
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.