{"id":"beed9666-163a-4e8a-9e5a-c5fae6b7ff24","entityType":"agent","slug":"clawhub-athola-nm-imbue-catchup","name":"catchup","canonicalUrl":"https://www.xpersona.co/agent/clawhub-athola-nm-imbue-catchup","canonicalPath":"/agent/clawhub-athola-nm-imbue-catchup","generatedAt":"2026-10-10T06:44:20.885Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-10T05:43:22.487Z","emptyReason":null},"description":"Summarizes recent git changes for context recovery after session breaks Skill: catchup Owner: athola Summary: Summarizes recent git changes for context recovery after session breaks Tags: latest:1.9.19 Version history: v1.9.19 | 2026-08-26T13:12:11.370Z | user Release v1.9.19 v1.9.17 | 2026-07-30T05:33:56.974Z | user Release v1.9.17 v1.9.16 | 2026-07-14T19:50:40.418Z | user Release v1.9.16 v1.9.14 | 2026-06-30T17:59:48.795Z | user Release v1.9.14 v1.9.13 | 2026-06-27T16:18:35.730Z | user","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1.6K downloads reported by the source. Last updated 10/10/2026.","installCommand":"clawhub skill install s17emme0e2m3cpf7k2jvp3a84984b8z9:nm-imbue-catchup","sourceUrl":"https://clawhub.ai/athola/nm-imbue-catchup","homepage":"https://clawhub.ai/athola/skills/nm-imbue-catchup","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/athola/nm-imbue-catchup","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/athola/skills/nm-imbue-catchup","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":40,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Summarizes recent git changes for context recovery after session breaks Skill: catchup Owner: athola Summary: Summarizes recent git changes for context recovery"},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-10T05:43:22.487Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-10T05:43:22.487Z","emptyReason":null},"stars":null,"forks":null,"downloads":1644,"packageName":null,"latestVersion":"1.9.19","tractionLabel":"1.6K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-10T05:43:22.487Z","emptyReason":null},"lastUpdatedAt":"2026-10-10T05:43:22.487Z","lastCrawledAt":"2026-10-10T05:43:22.487Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-11T05:43:22.487Z","lastVerifiedAt":null,"highlights":[{"version":"1.9.19","createdAt":"2026-08-26T13:12:11.370Z","changelog":"Release v1.9.19","fileCount":6,"zipByteSize":7756},{"version":"1.9.17","createdAt":"2026-07-30T05:33:56.974Z","changelog":"Release v1.9.17","fileCount":6,"zipByteSize":7689},{"version":"1.9.16","createdAt":"2026-07-14T19:50:40.418Z","changelog":"Release v1.9.16","fileCount":6,"zipByteSize":7705},{"version":"1.9.14","createdAt":"2026-06-30T17:59:48.795Z","changelog":"Release v1.9.14","fileCount":6,"zipByteSize":7763},{"version":"1.9.13","createdAt":"2026-06-27T16:18:35.730Z","changelog":"Release v1.9.13","fileCount":6,"zipByteSize":7780},{"version":"1.9.12","createdAt":"2026-06-19T03:12:40.609Z","changelog":"Release v1.9.12","fileCount":6,"zipByteSize":7731},{"version":"1.0.3","createdAt":"2026-06-18T14:07:50.932Z","changelog":"Release v1.9.12","fileCount":6,"zipByteSize":7765},{"version":"1.0.2","createdAt":"2026-05-09T02:17:12.755Z","changelog":"Release v1.9.5","fileCount":6,"zipByteSize":7792}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s17emme0e2m3cpf7k2jvp3a84984b8z9:nm-imbue-catchup","setupComplexity":"low","setupSteps":["Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-imbue-catchup/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-imbue-catchup/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-imbue-catchup/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-imbue-catchup/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-imbue-catchup/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-imbue-catchup/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-10T06:44:20.883Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-imbue-catchup/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-imbue-catchup/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-imbue-catchup/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-imbue-catchup/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-10T05:43:22.487Z","emptyReason":null},"readme":"Skill: catchup\n\nOwner: athola\n\nSummary: Summarizes recent git changes for context recovery after session breaks\n\nTags: latest:1.9.19\n\nVersion history:\n\nv1.9.19 | 2026-08-26T13:12:11.370Z | user\n\nRelease v1.9.19\n\nv1.9.17 | 2026-07-30T05:33:56.974Z | user\n\nRelease v1.9.17\n\nv1.9.16 | 2026-07-14T19:50:40.418Z | user\n\nRelease v1.9.16\n\nv1.9.14 | 2026-06-30T17:59:48.795Z | user\n\nRelease v1.9.14\n\nv1.9.13 | 2026-06-27T16:18:35.730Z | user\n\nRelease v1.9.13\n\nv1.9.12 | 2026-06-19T03:12:40.609Z | user\n\nRelease v1.9.12\n\nv1.0.3 | 2026-06-18T14:07:50.932Z | user\n\nRelease v1.9.12\n\nv1.0.2 | 2026-05-09T02:17:12.755Z | user\n\nRelease v1.9.5\n\nv1.0.1 | 2026-05-06T14:17:51.495Z | user\n\nRelease v1.9.4\n\nv1.0.0 | 2026-04-12T11:01:47.635Z | auto\n\nInitial release of the catchup skill for summarizing recent changes and context in git and documents.\n\n- Provides a 4-step methodology for quickly understanding recent changes: confirm context, capture delta, extract insights, and record follow-ups.\n- Supports progressive loading for git history, documents, and logs.\n- Includes structured output format for easy handoffs and sprint reviews.\n- Designed for \"what changed and what matters\" use cases; not suitable for detailed diff or code review.\n- Integrates with TodoWrite workflow and other Night Market plugins for reproducibility and risk assessment.\n\nArchive index:\n\nArchive v1.9.19: 6 files, 7756 bytes\n\nFiles: modules/document-analysis-patterns.md (2358b), modules/git-catchup-patterns.md (3338b), modules/log-analysis-patterns.md (2540b), skill-card.md (2036b), SKILL.md (3757b), _meta.json (136b)\n\nFile v1.9.19:SKILL.md\n\n---\nname: catchup\ndescription: Summarizes recent git changes for context recovery after session breaks\nversion: 1.9.8\ntriggers:\n - summarization\n - context-acquisition\n - insights\n - follow-ups\n - resuming work after a gap or handing off to another session\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/imbue\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.imbue:proof-of-work\"]}}}\nsource: claude-night-market\nsource_plugin: imbue\n---\n\n> **Night Market Skill** — ported from [claude-night-market/imbue](https://github.com/athola/claude-night-market/tree/master/plugins/imbue). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n## Table of Contents\n\n- [Overview](#overview)\n- [When to Use](#when-to-use)\n- [Activation](#activation)\n- [Progressive Loading](#progressive-loading)\n- [4-Step Methodology](#4-step-methodology)\n- [Output Format](#output-format)\n\n# Catchup Analysis Methodology\n\n## Overview\n\nStructured 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.\n\n## When To Use\n- Joining ongoing work or returning after absence\n- Before planning or reviewing handoffs\n- Any \"what happened and what's next\" context\n\n## When NOT To Use\n\n- Doing detailed\n diff analysis - use diff-analysis instead\n- Full code review needed\n - use review-core instead\n\n## Activation\n**Keywords**: catchup, summary, status, progress, context, handoff\n**Cues**: \"get me up to speed\", \"current status\", \"summarize progress\"\n\n## Progressive Loading\n\nLoad modules based on context:\n\n**Git**: Load `modules/git-catchup-patterns.md` for git commands. Consider `sanctum:git-workspace-review` for initial data gathering.\n\n**Documents/Notes**: Load `modules/document-analysis-patterns.md` for meeting notes, sprint tracking, document revisions.\n\n**Logs/Events**: Load `modules/log-analysis-patterns.md` for time-series and metric analysis.\n\n**Always Available**: `imbue:proof-of-work`, TodoWrite workflow, structured output.\n\n## Required TodoWrite Items\n1. `catchup:context-confirmed` - Boundaries established\n2. `catchup:delta-captured` - Changes enumerated\n3. `catchup:insights-extracted` - Themes identified\n4. `catchup:followups-recorded` - Actions captured\n\n## 4-Step Methodology\n\n### Step 1: Confirm Context\nDefine scope (git branch, sprint, meetings), baseline (last state), and current target. See modules for commands.\n\n### Step 2: Capture Delta\nEnumerate changed items with metrics. Prioritize source/config/docs over generated artifacts. See modules for strategies.\n\n### Step 3: Extract Insights\nPer item: **What** (change), **Why** (motivation), **Implications** (tests/risks/deps). Rollup into themes.\n\n### Step 4: Record Follow-ups\nCapture: Tests, Documentation, Reviews, Blockers, Questions. If none, state explicitly.\n\n## Output Format\n```\n## Summary\n[2-3 sentence theme + risk overview]\n\n## Key Changes\n- [Item]: [what/why/implication]\n\n## Follow-ups\n- [ ] [Action with owner]\n\n## Blockers/Questions\n- [Item requiring resolution]\n```\n**Verification:** Run the command with `--help` flag to verify availability.\n\n## Integration\nUse `imbue:diff-analysis` for risk assessment, `imbue:proof-of-work` for reproducibility, `sanctum:git-workspace-review` for git data. Feed to `brainstorming` or `writing-plans` as needed.\n\n## Token Conservation\nReference paths and lines (don't reproduce). Summarize outputs. Defer deep analysis. Use progressive loading.\n\n## Exit Criteria\n- Four TodoWrite items completed\n- Context/delta/insights/follow-ups captured\n- Stakeholders understand state without re-reading sources\n\nFile v1.9.19:_meta.json\n\n{\n \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n \"slug\": \"nm-imbue-catchup\",\n \"version\": \"1.9.19\",\n \"publishedAt\": 1787749931370\n}\n\nFile v1.9.19:modules/document-analysis-patterns.md\n\n---\nname: document-analysis-patterns\ndescription: Document and meeting notes analysis patterns for catchup\nparent_skill: imbue:catchup\ncategory: analysis-patterns\ntags: [documents, meetings, notes, tracking]\nestimated_tokens: 300\n---\n\n# Document Analysis Patterns\n\n## Meeting Notes Analysis\n\nWhen catching up on meeting notes or discussions:\n\n**Context Establishment:**\n- Identify date range: \"Last meeting I attended was [date]\"\n- Note participants involved\n- Identify meeting series or project name\n\n**Delta Capture:**\n- List topics discussed (agenda items)\n- Enumerate decisions made\n- Identify action items assigned\n- Note open questions or blocked items\n\n**Insight Extraction:**\n- What changed since last meeting?\n- What decisions affect ongoing work?\n- What consensus emerged on contentious topics?\n- What new information affects project direction?\n\n## Sprint/Ticket Catchup Patterns\n\nFor Jira, GitHub Issues, or similar tracking systems:\n\n**Context:**\n- Last sprint/milestone reviewed\n- Current sprint/milestone\n- Team velocity or capacity changes\n\n**Delta:**\n- Tickets completed since baseline\n- Tickets in progress\n- New tickets added to backlog\n- Priority shifts or re-ordering\n\n**Insights:**\n- Velocity trends (ahead/behind schedule?)\n- Risk indicators (blocked tickets, dependencies)\n- Scope changes (new requirements, deferred items)\n- Team capacity changes\n\n## Document Revision Tracking\n\nWhen reviewing evolving documents (specs, designs, RFCs):\n\n**Context:**\n- Last version reviewed (version number, date, or commit)\n- Current version\n- Document type and audience\n\n**Delta:**\n- Sections added, modified, or removed\n- Comments or review feedback incorporated\n- Status changes (draft → review → approved)\n\n**Insights:**\n- Requirements changes and rationale\n- Design decisions made or reversed\n- Unresolved discussions or open questions\n- Approval status and blockers\n\n## Generic Document Delta Patterns\n\n**Efficient Enumeration:**\n- Focus on substantive changes (ignore typos, formatting)\n- Identify authors/contributors to understand perspective\n- Note timestamp for context\n- Track references to external decisions or dependencies\n\n**Token Conservation:**\n- Summarize content rather than quoting verbatim\n- Reference section headings + key points\n- List decisions/actions rather than narrative\n- Use bullet points for scanning efficiency\n\nFile v1.9.19:modules/git-catchup-patterns.md\n\n---\nname: git-catchup-patterns\ndescription: Git-specific commands and patterns for catchup analysis\nparent_skill: imbue:catchup\ncategory: technical-patterns\ntags: [git, version-control, delta-capture]\nestimated_tokens: 400\n---\n\n# Git Catchup Patterns\n\n## Git Context Establishment\n\nUse these commands to establish git repository context:\n\n```bash\npwd # Show current directory\ngit status -sb | head -n 1 # Show current branch and status\ngit rev-parse --abbrev-ref --symbolic-full-name @{u} # Show the upstream branch, if one is being tracked\n```\n\nThese help answer:\n- Where am I working?\n- What branch am I on?\n- Is this branch tracking a remote?\n\n## Git Delta Capture\n\nEfficiently capture changes between states:\n\n```bash\ngit diff --stat ${BASE}...HEAD # Show summary statistics\ngit diff --name-only ${BASE}...HEAD # List changed files\ngit log --oneline ${BASE}...HEAD # Show commit history\n```\n\n**Key Patterns:**\n- Use `--stat` for high-level overview (files changed, insertions/deletions)\n- Use `--name-only` for enumeration without content\n- Use `...` three-dot syntax to show changes on current branch since divergence\n\n## Semantic Delta Capture (sem)\n\nWhen sem is available (see `leyline:sem-integration`),\nenhance delta capture with entity-level diffs:\n\n```bash\n# Entity-level change summary across commits\nsem diff --format json ${BASE}...HEAD\n\n# Track a specific entity's evolution\nsem log \n```\n\n> **Note:** sem may not support three-dot (`...`) range\n> syntax directly. If `sem diff` fails with a range,\n> resolve the merge base first:\n> `BASE=$(git merge-base main HEAD)` then pass\n> `sem diff --format json $BASE HEAD`.\n\n**Key advantages over git diff --stat:**\n\n- Shows which functions/classes changed, not just files\n- Distinguishes additions from modifications from renames\n- `sem log` tracks an entity across renames\n\nWhen sem is unavailable, fall back to the git commands\nin the section above.\n\n## Git-Specific Insights Extraction\n\nTargeted inspection commands:\n\n```bash\ngit show --stat # Show specific commit changes\ngit diff ${BASE}...HEAD -- path/to/file # Examine specific file changes\ngit log -p --follow -- path/to/file # File history with patches\n```\n\n**Efficient Reading:**\n- Use `git show` for commit-level understanding\n- Use `git diff` with file paths for focused analysis\n- Avoid `git log -p` without limits (token-heavy)\n\n## Integration with Sanctum\n\n**Before running catchup analysis**, use `sanctum:git-workspace-review` to gather:\n- Repository confirmation (pwd, branch)\n- Status overview (staged vs unstaged)\n- Diff statistics\n- Diff details\n\nThen proceed with catchup-specific insight extraction and follow-up identification.\n\n**Sanctum provides the raw data; catchup extracts insights and concrete next steps.**\n\n## Common Patterns\n\n**Feature Branch Catchup:**\n```bash\nBASE=$(git merge-base main HEAD)\ngit diff --stat main...HEAD\ngit log --oneline main...HEAD\n```\n\n**Release Catchup:**\n```bash\ngit diff --stat v1.0.0...v1.1.0\ngit log --oneline --graph v1.0.0...v1.1.0\n```\n\n**Daily Standup Catchup:**\n```bash\ngit log --since=\"yesterday\" --oneline --all\ngit diff --stat HEAD@{yesterday}...HEAD\n```\n\nFile v1.9.19:modules/log-analysis-patterns.md\n\n---\nname: log-analysis-patterns\ndescription: System log and event stream analysis patterns for catchup\nparent_skill: imbue:catchup\ncategory: analysis-patterns\ntags: [logs, events, monitoring, time-series]\nestimated_tokens: 300\n---\n\n# Log Analysis Patterns\n\n## System Log Catchup\n\nWhen catching up on system behavior via logs:\n\n**Context Establishment:**\n- Identify time window: \"Last check was [timestamp]\"\n- Note log sources (application, system, service)\n- Identify environment (prod, staging, dev)\n- Baseline normal behavior\n\n**Delta Capture:**\n- Count log entries by severity (ERROR, WARN, INFO)\n- Enumerate unique error types\n- Identify anomalies or patterns\n- Note frequency changes (spike, drop, stable)\n\n**Efficient Commands:**\n```bash\n# Count by severity\ngrep -c \"ERROR\" logfile.log\ngrep -c \"WARN\" logfile.log\n\n# Unique error messages\ngrep \"ERROR\" logfile.log | cut -d: -f3 | sort | uniq -c | sort -rn | head -20\n\n# Time-based filtering\nawk '$1 >= \"2025-12-04\" && $1 <= \"2025-12-05\"' logfile.log\n```\n\n## Event Stream Analysis\n\nFor application events, audit logs, or metrics:\n\n**Context:**\n- Event source and schema\n- Baseline event rate\n- Time window of interest\n- Expected vs actual patterns\n\n**Delta:**\n- New event types introduced\n- Event rate changes (throughput)\n- Failed vs successful event ratios\n- Outliers or anomalies\n\n**Insights:**\n- Performance trends (response times, throughput)\n- Error patterns (recurring, transient, progressive)\n- User behavior changes\n- System health indicators\n\n## Time-Window Analysis\n\n**Comparing time windows:**\n```bash\n# Events today vs yesterday\ncomm -13 <(grep \"2025-12-04\" events.log | sort) \\\n <(grep \"2025-12-05\" events.log | sort)\n\n# Hourly breakdown\nawk '{print substr($1,12,2)}' logfile.log | sort | uniq -c\n```\n\n**Pattern Detection:**\n- Periodic patterns (hourly, daily, weekly cycles)\n- Correlation between events\n- Cascading failures\n- Recovery patterns\n\n## Metric-Based Catchup\n\nWhen logs include metrics or measurements:\n\n**Delta:**\n- Min/max/avg changes\n- Percentile shifts (p50, p95, p99)\n- Threshold violations\n- Trend direction (improving, degrading, stable)\n\n**Insights:**\n- Capacity planning needs\n- Performance regression sources\n- Resource utilization trends\n- SLA compliance status\n\n## Token Conservation\n\n- Use aggregation (counts, uniques) over raw logs\n- Sample representative entries, don't reproduce all\n- Reference log files + line numbers for detail\n- Summarize patterns rather than listing every entry\n- Defer deep debugging to specialized tools/skills\n\nFile v1.9.19:skill-card.md\n\n## Description:\n\nSummarizes recent git changes for context recovery after session breaks.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[athola](https://clawhub.ai/user/athola)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and project contributors use this skill to catch up on recent repository, document, meeting-note, sprint, or log changes and identify important follow-ups after a gap or handoff.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Broad activation on status or summary requests may lead the agent to inspect more repository, document, or log context than intended.\n\nMitigation: Invoke the skill with a clear scope, such as a specific branch, baseline, date range, project, meeting series, or log file.\n\nRisk: Catchup summaries can miss important detail or overstate implications when the baseline or target context is unclear.\n\nMitigation: Confirm context boundaries first and review the captured follow-ups, blockers, and referenced paths before acting on the summary.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/athola/skills/nm-imbue-catchup)\n- [Configured homepage](https://github.com/athola/claude-night-market/tree/master/plugins/imbue)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, shell commands, guidance]\n\n**Output Format:** [Markdown summary with bullet lists, follow-up checkboxes, and scoped command snippets when useful]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [References paths and lines instead of reproducing long source content; uses progressive loading for git, document, and log catchup patterns.]\n\n## Skill Version(s):\n\n1.9.19 (source: server release metadata; artifact frontmatter reports 1.9.8)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.9.17: 6 files, 7689 bytes\n\nFiles: modules/document-analysis-patterns.md (2358b), modules/git-catchup-patterns.md (3338b), modules/log-analysis-patterns.md (2540b), skill-card.md (1986b), SKILL.md (3757b), _meta.json (136b)\n\nFile v1.9.17:SKILL.md\n\n---\nname: catchup\ndescription: Summarizes recent git changes for context recovery after session breaks\nversion: 1.9.8\ntriggers:\n - summarization\n - context-acquisition\n - insights\n - follow-ups\n - resuming work after a gap or handing off to another session\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/imbue\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.imbue:proof-of-work\"]}}}\nsource: claude-night-market\nsource_plugin: imbue\n---\n\n> **Night Market Skill** — ported from [claude-night-market/imbue](https://github.com/athola/claude-night-market/tree/master/plugins/imbue). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n## Table of Contents\n\n- [Overview](#overview)\n- [When to Use](#when-to-use)\n- [Activation](#activation)\n- [Progressive Loading](#progressive-loading)\n- [4-Step Methodology](#4-step-methodology)\n- [Output Format](#output-format)\n\n# Catchup Analysis Methodology\n\n## Overview\n\nStructured 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.\n\n## When To Use\n- Joining ongoing work or returning after absence\n- Before planning or reviewing handoffs\n- Any \"what happened and what's next\" context\n\n## When NOT To Use\n\n- Doing detailed\n diff analysis - use diff-analysis instead\n- Full code review needed\n - use review-core instead\n\n## Activation\n**Keywords**: catchup, summary, status, progress, context, handoff\n**Cues**: \"get me up to speed\", \"current status\", \"summarize progress\"\n\n## Progressive Loading\n\nLoad modules based on context:\n\n**Git**: Load `modules/git-catchup-patterns.md` for git commands. Consider `sanctum:git-workspace-review` for initial data gathering.\n\n**Documents/Notes**: Load `modules/document-analysis-patterns.md` for meeting notes, sprint tracking, document revisions.\n\n**Logs/Events**: Load `modules/log-analysis-patterns.md` for time-series and metric analysis.\n\n**Always Available**: `imbue:proof-of-work`, TodoWrite workflow, structured output.\n\n## Required TodoWrite Items\n1. `catchup:context-confirmed` - Boundaries established\n2. `catchup:delta-captured` - Changes enumerated\n3. `catchup:insights-extracted` - Themes identified\n4. `catchup:followups-recorded` - Actions captured\n\n## 4-Step Methodology\n\n### Step 1: Confirm Context\nDefine scope (git branch, sprint, meetings), baseline (last state), and current target. See modules for commands.\n\n### Step 2: Capture Delta\nEnumerate changed items with metrics. Prioritize source/config/docs over generated artifacts. See modules for strategies.\n\n### Step 3: Extract Insights\nPer item: **What** (change), **Why** (motivation), **Implications** (tests/risks/deps). Rollup into themes.\n\n### Step 4: Record Follow-ups\nCapture: Tests, Documentation, Reviews, Blockers, Questions. If none, state explicitly.\n\n## Output Format\n```\n## Summary\n[2-3 sentence theme + risk overview]\n\n## Key Changes\n- [Item]: [what/why/implication]\n\n## Follow-ups\n- [ ] [Action with owner]\n\n## Blockers/Questions\n- [Item requiring resolution]\n```\n**Verification:** Run the command with `--help` flag to verify availability.\n\n## Integration\nUse `imbue:diff-analysis` for risk assessment, `imbue:proof-of-work` for reproducibility, `sanctum:git-workspace-review` for git data. Feed to `brainstorming` or `writing-plans` as needed.\n\n## Token Conservation\nReference paths and lines (don't reproduce). Summarize outputs. Defer deep analysis. Use progressive loading.\n\n## Exit Criteria\n- Four TodoWrite items completed\n- Context/delta/insights/follow-ups captured\n- Stakeholders understand state without re-reading sources\n\nFile v1.9.17:_meta.json\n\n{\n \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n \"slug\": \"nm-imbue-catchup\",\n \"version\": \"1.9.17\",\n \"publishedAt\": 1785389636974\n}\n\nFile v1.9.17:modules/document-analysis-patterns.md\n\n---\nname: document-analysis-patterns\ndescription: Document and meeting notes analysis patterns for catchup\nparent_skill: imbue:catchup\ncategory: analysis-patterns\ntags: [documents, meetings, notes, tracking]\nestimated_tokens: 300\n---\n\n# Document Analysis Patterns\n\n## Meeting Notes Analysis\n\nWhen catching up on meeting notes or discussions:\n\n**Context Establishment:**\n- Identify date range: \"Last meeting I attended was [date]\"\n- Note participants involved\n- Identify meeting series or project name\n\n**Delta Capture:**\n- List topics discussed (agenda items)\n- Enumerate decisions made\n- Identify action items assigned\n- Note open questions or blocked items\n\n**Insight Extraction:**\n- What changed since last meeting?\n- What decisions affect ongoing work?\n- What consensus emerged on contentious topics?\n- What new information affects project direction?\n\n## Sprint/Ticket Catchup Patterns\n\nFor Jira, GitHub Issues, or similar tracking systems:\n\n**Context:**\n- Last sprint/milestone reviewed\n- Current sprint/milestone\n- Team velocity or capacity changes\n\n**Delta:**\n- Tickets completed since baseline\n- Tickets in progress\n- New tickets added to backlog\n- Priority shifts or re-ordering\n\n**Insights:**\n- Velocity trends (ahead/behind schedule?)\n- Risk indicators (blocked tickets, dependencies)\n- Scope changes (new requirements, deferred items)\n- Team capacity changes\n\n## Document Revision Tracking\n\nWhen reviewing evolving documents (specs, designs, RFCs):\n\n**Context:**\n- Last version reviewed (version number, date, or commit)\n- Current version\n- Document type and audience\n\n**Delta:**\n- Sections added, modified, or removed\n- Comments or review feedback incorporated\n- Status changes (draft → review → approved)\n\n**Insights:**\n- Requirements changes and rationale\n- Design decisions made or reversed\n- Unresolved discussions or open questions\n- Approval status and blockers\n\n## Generic Document Delta Patterns\n\n**Efficient Enumeration:**\n- Focus on substantive changes (ignore typos, formatting)\n- Identify authors/contributors to understand perspective\n- Note timestamp for context\n- Track references to external decisions or dependencies\n\n**Token Conservation:**\n- Summarize content rather than quoting verbatim\n- Reference section headings + key points\n- List decisions/actions rather than narrative\n- Use bullet points for scanning efficiency\n\nFile v1.9.17:modules/git-catchup-patterns.md\n\n---\nname: git-catchup-patterns\ndescription: Git-specific commands and patterns for catchup analysis\nparent_skill: imbue:catchup\ncategory: technical-patterns\ntags: [git, version-control, delta-capture]\nestimated_tokens: 400\n---\n\n# Git Catchup Patterns\n\n## Git Context Establishment\n\nUse these commands to establish git repository context:\n\n```bash\npwd # Show current directory\ngit status -sb | head -n 1 # Show current branch and status\ngit rev-parse --abbrev-ref --symbolic-full-name @{u} # Show the upstream branch, if one is being tracked\n```\n\nThese help answer:\n- Where am I working?\n- What branch am I on?\n- Is this branch tracking a remote?\n\n## Git Delta Capture\n\nEfficiently capture changes between states:\n\n```bash\ngit diff --stat ${BASE}...HEAD # Show summary statistics\ngit diff --name-only ${BASE}...HEAD # List changed files\ngit log --oneline ${BASE}...HEAD # Show commit history\n```\n\n**Key Patterns:**\n- Use `--stat` for high-level overview (files changed, insertions/deletions)\n- Use `--name-only` for enumeration without content\n- Use `...` three-dot syntax to show changes on current branch since divergence\n\n## Semantic Delta Capture (sem)\n\nWhen sem is available (see `leyline:sem-integration`),\nenhance delta capture with entity-level diffs:\n\n```bash\n# Entity-level change summary across commits\nsem diff --format json ${BASE}...HEAD\n\n# Track a specific entity's evolution\nsem log \n```\n\n> **Note:** sem may not support three-dot (`...`) range\n> syntax directly. If `sem diff` fails with a range,\n> resolve the merge base first:\n> `BASE=$(git merge-base main HEAD)` then pass\n> `sem diff --format json $BASE HEAD`.\n\n**Key advantages over git diff --stat:**\n\n- Shows which functions/classes changed, not just files\n- Distinguishes additions from modifications from renames\n- `sem log` tracks an entity across renames\n\nWhen sem is unavailable, fall back to the git commands\nin the section above.\n\n## Git-Specific Insights Extraction\n\nTargeted inspection commands:\n\n```bash\ngit show --stat # Show specific commit changes\ngit diff ${BASE}...HEAD -- path/to/file # Examine specific file changes\ngit log -p --follow -- path/to/file # File history with patches\n```\n\n**Efficient Reading:**\n- Use `git show` for commit-level understanding\n- Use `git diff` with file paths for focused analysis\n- Avoid `git log -p` without limits (token-heavy)\n\n## Integration with Sanctum\n\n**Before running catchup analysis**, use `sanctum:git-workspace-review` to gather:\n- Repository confirmation (pwd, branch)\n- Status overview (staged vs unstaged)\n- Diff statistics\n- Diff details\n\nThen proceed with catchup-specific insight extraction and follow-up identification.\n\n**Sanctum provides the raw data; catchup extracts insights and concrete next steps.**\n\n## Common Patterns\n\n**Feature Branch Catchup:**\n```bash\nBASE=$(git merge-base main HEAD)\ngit diff --stat main...HEAD\ngit log --oneline main...HEAD\n```\n\n**Release Catchup:**\n```bash\ngit diff --stat v1.0.0...v1.1.0\ngit log --oneline --graph v1.0.0...v1.1.0\n```\n\n**Daily Standup Catchup:**\n```bash\ngit log --since=\"yesterday\" --oneline --all\ngit diff --stat HEAD@{yesterday}...HEAD\n```\n\nFile v1.9.17:modules/log-analysis-patterns.md\n\n---\nname: log-analysis-patterns\ndescription: System log and event stream analysis patterns for catchup\nparent_skill: imbue:catchup\ncategory: analysis-patterns\ntags: [logs, events, monitoring, time-series]\nestimated_tokens: 300\n---\n\n# Log Analysis Patterns\n\n## System Log Catchup\n\nWhen catching up on system behavior via logs:\n\n**Context Establishment:**\n- Identify time window: \"Last check was [timestamp]\"\n- Note log sources (application, system, service)\n- Identify environment (prod, staging, dev)\n- Baseline normal behavior\n\n**Delta Capture:**\n- Count log entries by severity (ERROR, WARN, INFO)\n- Enumerate unique error types\n- Identify anomalies or patterns\n- Note frequency changes (spike, drop, stable)\n\n**Efficient Commands:**\n```bash\n# Count by severity\ngrep -c \"ERROR\" logfile.log\ngrep -c \"WARN\" logfile.log\n\n# Unique error messages\ngrep \"ERROR\" logfile.log | cut -d: -f3 | sort | uniq -c | sort -rn | head -20\n\n# Time-based filtering\nawk '$1 >= \"2025-12-04\" && $1 <= \"2025-12-05\"' logfile.log\n```\n\n## Event Stream Analysis\n\nFor application events, audit logs, or metrics:\n\n**Context:**\n- Event source and schema\n- Baseline event rate\n- Time window of interest\n- Expected vs actual patterns\n\n**Delta:**\n- New event types introduced\n- Event rate changes (throughput)\n- Failed vs successful event ratios\n- Outliers or anomalies\n\n**Insights:**\n- Performance trends (response times, throughput)\n- Error patterns (recurring, transient, progressive)\n- User behavior changes\n- System health indicators\n\n## Time-Window Analysis\n\n**Comparing time windows:**\n```bash\n# Events today vs yesterday\ncomm -13 <(grep \"2025-12-04\" events.log | sort) \\\n <(grep \"2025-12-05\" events.log | sort)\n\n# Hourly breakdown\nawk '{print substr($1,12,2)}' logfile.log | sort | uniq -c\n```\n\n**Pattern Detection:**\n- Periodic patterns (hourly, daily, weekly cycles)\n- Correlation between events\n- Cascading failures\n- Recovery patterns\n\n## Metric-Based Catchup\n\nWhen logs include metrics or measurements:\n\n**Delta:**\n- Min/max/avg changes\n- Percentile shifts (p50, p95, p99)\n- Threshold violations\n- Trend direction (improving, degrading, stable)\n\n**Insights:**\n- Capacity planning needs\n- Performance regression sources\n- Resource utilization trends\n- SLA compliance status\n\n## Token Conservation\n\n- Use aggregation (counts, uniques) over raw logs\n- Sample representative entries, don't reproduce all\n- Reference log files + line numbers for detail\n- Summarize patterns rather than listing every entry\n- Defer deep debugging to specialized tools/skills\n\nFile v1.9.17:skill-card.md\n\n## Description:
\nSummarizes recent git changes for context recovery after session breaks.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[athola](https://clawhub.ai/user/athola)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and teams use this skill to get back up to speed on recent repository, document, meeting, sprint, or log changes after a gap or handoff.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: Broad activation on status, progress, or summary requests may cause the agent to inspect more local repository, document, or log content than intended.
\nMitigation: Confirm the intended scope, baseline, and target before running catchup analysis, especially in private or large workspaces.
\nRisk: Catchup summaries can omit important detail or overstate the significance of recent changes.
\nMitigation: Use the summary as a navigation aid and verify important conclusions against referenced files, commits, documents, or logs.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/athola/skills/nm-imbue-catchup)
\n- [clawdis homepage](https://github.com/athola/claude-night-market/tree/master/plugins/imbue)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, shell commands, guidance]
\n**Output Format:** [Markdown summary with bullets, checkboxes, and optional shell commands]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Summaries are structured around context, delta, insights, follow-ups, and blockers.]
\n\n## Skill Version(s):
\n1.9.17 (source: server release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.9.16: 6 files, 7705 bytes\n\nFiles: modules/document-analysis-patterns.md (2358b), modules/git-catchup-patterns.md (3338b), modules/log-analysis-patterns.md (2540b), skill-card.md (2064b), SKILL.md (3757b), _meta.json (136b)\n\nFile v1.9.16:SKILL.md\n\n---\nname: catchup\ndescription: Summarizes recent git changes for context recovery after session breaks\nversion: 1.9.8\ntriggers:\n - summarization\n - context-acquisition\n - insights\n - follow-ups\n - resuming work after a gap or handing off to another session\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/imbue\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.imbue:proof-of-work\"]}}}\nsource: claude-night-market\nsource_plugin: imbue\n---\n\n> **Night Market Skill** — ported from [claude-night-market/imbue](https://github.com/athola/claude-night-market/tree/master/plugins/imbue). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n## Table of Contents\n\n- [Overview](#overview)\n- [When to Use](#when-to-use)\n- [Activation](#activation)\n- [Progressive Loading](#progressive-loading)\n- [4-Step Methodology](#4-step-methodology)\n- [Output Format](#output-format)\n\n# Catchup Analysis Methodology\n\n## Overview\n\nStructured 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.\n\n## When To Use\n- Joining ongoing work or returning after absence\n- Before planning or reviewing handoffs\n- Any \"what happened and what's next\" context\n\n## When NOT To Use\n\n- Doing detailed\n diff analysis - use diff-analysis instead\n- Full code review needed\n - use review-core instead\n\n## Activation\n**Keywords**: catchup, summary, status, progress, context, handoff\n**Cues**: \"get me up to speed\", \"current status\", \"summarize progress\"\n\n## Progressive Loading\n\nLoad modules based on context:\n\n**Git**: Load `modules/git-catchup-patterns.md` for git commands. Consider `sanctum:git-workspace-review` for initial data gathering.\n\n**Documents/Notes**: Load `modules/document-analysis-patterns.md` for meeting notes, sprint tracking, document revisions.\n\n**Logs/Events**: Load `modules/log-analysis-patterns.md` for time-series and metric analysis.\n\n**Always Available**: `imbue:proof-of-work`, TodoWrite workflow, structured output.\n\n## Required TodoWrite Items\n1. `catchup:context-confirmed` - Boundaries established\n2. `catchup:delta-captured` - Changes enumerated\n3. `catchup:insights-extracted` - Themes identified\n4. `catchup:followups-recorded` - Actions captured\n\n## 4-Step Methodology\n\n### Step 1: Confirm Context\nDefine scope (git branch, sprint, meetings), baseline (last state), and current target. See modules for commands.\n\n### Step 2: Capture Delta\nEnumerate changed items with metrics. Prioritize source/config/docs over generated artifacts. See modules for strategies.\n\n### Step 3: Extract Insights\nPer item: **What** (change), **Why** (motivation), **Implications** (tests/risks/deps). Rollup into themes.\n\n### Step 4: Record Follow-ups\nCapture: Tests, Documentation, Reviews, Blockers, Questions. If none, state explicitly.\n\n## Output Format\n```\n## Summary\n[2-3 sentence theme + risk overview]\n\n## Key Changes\n- [Item]: [what/why/implication]\n\n## Follow-ups\n- [ ] [Action with owner]\n\n## Blockers/Questions\n- [Item requiring resolution]\n```\n**Verification:** Run the command with `--help` flag to verify availability.\n\n## Integration\nUse `imbue:diff-analysis` for risk assessment, `imbue:proof-of-work` for reproducibility, `sanctum:git-workspace-review` for git data. Feed to `brainstorming` or `writing-plans` as needed.\n\n## Token Conservation\nReference paths and lines (don't reproduce). Summarize outputs. Defer deep analysis. Use progressive loading.\n\n## Exit Criteria\n- Four TodoWrite items completed\n- Context/delta/insights/follow-ups captured\n- Stakeholders understand state without re-reading sources\n\nFile v1.9.16:_meta.json\n\n{\n \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n \"slug\": \"nm-imbue-catchup\",\n \"version\": \"1.9.16\",\n \"publishedAt\": 1784058640418\n}\n\nFile v1.9.16:modules/document-analysis-patterns.md\n\n---\nname: document-analysis-patterns\ndescription: Document and meeting notes analysis patterns for catchup\nparent_skill: imbue:catchup\ncategory: analysis-patterns\ntags: [documents, meetings, notes, tracking]\nestimated_tokens: 300\n---\n\n# Document Analysis Patterns\n\n## Meeting Notes Analysis\n\nWhen catching up on meeting notes or discussions:\n\n**Context Establishment:**\n- Identify date range: \"Last meeting I attended was [date]\"\n- Note participants involved\n- Identify meeting series or project name\n\n**Delta Capture:**\n- List topics discussed (agenda items)\n- Enumerate decisions made\n- Identify action items assigned\n- Note open questions or blocked items\n\n**Insight Extraction:**\n- What changed since last meeting?\n- What decisions affect ongoing work?\n- What consensus emerged on contentious topics?\n- What new information affects project direction?\n\n## Sprint/Ticket Catchup Patterns\n\nFor Jira, GitHub Issues, or similar tracking systems:\n\n**Context:**\n- Last sprint/milestone reviewed\n- Current sprint/milestone\n- Team velocity or capacity changes\n\n**Delta:**\n- Tickets completed since baseline\n- Tickets in progress\n- New tickets added to backlog\n- Priority shifts or re-ordering\n\n**Insights:**\n- Velocity trends (ahead/behind schedule?)\n- Risk indicators (blocked tickets, dependencies)\n- Scope changes (new requirements, deferred items)\n- Team capacity changes\n\n## Document Revision Tracking\n\nWhen reviewing evolving documents (specs, designs, RFCs):\n\n**Context:**\n- Last version reviewed (version number, date, or commit)\n- Current version\n- Document type and audience\n\n**Delta:**\n- Sections added, modified, or removed\n- Comments or review feedback incorporated\n- Status changes (draft → review → approved)\n\n**Insights:**\n- Requirements changes and rationale\n- Design decisions made or reversed\n- Unresolved discussions or open questions\n- Approval status and blockers\n\n## Generic Document Delta Patterns\n\n**Efficient Enumeration:**\n- Focus on substantive changes (ignore typos, formatting)\n- Identify authors/contributors to understand perspective\n- Note timestamp for context\n- Track references to external decisions or dependencies\n\n**Token Conservation:**\n- Summarize content rather than quoting verbatim\n- Reference section headings + key points\n- List decisions/actions rather than narrative\n- Use bullet points for scanning efficiency\n\nFile v1.9.16:modules/git-catchup-patterns.md\n\n---\nname: git-catchup-patterns\ndescription: Git-specific commands and patterns for catchup analysis\nparent_skill: imbue:catchup\ncategory: technical-patterns\ntags: [git, version-control, delta-capture]\nestimated_tokens: 400\n---\n\n# Git Catchup Patterns\n\n## Git Context Establishment\n\nUse these commands to establish git repository context:\n\n```bash\npwd # Show current directory\ngit status -sb | head -n 1 # Show current branch and status\ngit rev-parse --abbrev-ref --symbolic-full-name @{u} # Show the upstream branch, if one is being tracked\n```\n\nThese help answer:\n- Where am I working?\n- What branch am I on?\n- Is this branch tracking a remote?\n\n## Git Delta Capture\n\nEfficiently capture changes between states:\n\n```bash\ngit diff --stat ${BASE}...HEAD # Show summary statistics\ngit diff --name-only ${BASE}...HEAD # List changed files\ngit log --oneline ${BASE}...HEAD # Show commit history\n```\n\n**Key Patterns:**\n- Use `--stat` for high-level overview (files changed, insertions/deletions)\n- Use `--name-only` for enumeration without content\n- Use `...` three-dot syntax to show changes on current branch since divergence\n\n## Semantic Delta Capture (sem)\n\nWhen sem is available (see `leyline:sem-integration`),\nenhance delta capture with entity-level diffs:\n\n```bash\n# Entity-level change summary across commits\nsem diff --format json ${BASE}...HEAD\n\n# Track a specific entity's evolution\nsem log \n```\n\n> **Note:** sem may not support three-dot (`...`) range\n> syntax directly. If `sem diff` fails with a range,\n> resolve the merge base first:\n> `BASE=$(git merge-base main HEAD)` then pass\n> `sem diff --format json $BASE HEAD`.\n\n**Key advantages over git diff --stat:**\n\n- Shows which functions/classes changed, not just files\n- Distinguishes additions from modifications from renames\n- `sem log` tracks an entity across renames\n\nWhen sem is unavailable, fall back to the git commands\nin the section above.\n\n## Git-Specific Insights Extraction\n\nTargeted inspection commands:\n\n```bash\ngit show --stat # Show specific commit changes\ngit diff ${BASE}...HEAD -- path/to/file # Examine specific file changes\ngit log -p --follow -- path/to/file # File history with patches\n```\n\n**Efficient Reading:**\n- Use `git show` for commit-level understanding\n- Use `git diff` with file paths for focused analysis\n- Avoid `git log -p` without limits (token-heavy)\n\n## Integration with Sanctum\n\n**Before running catchup analysis**, use `sanctum:git-workspace-review` to gather:\n- Repository confirmation (pwd, branch)\n- Status overview (staged vs unstaged)\n- Diff statistics\n- Diff details\n\nThen proceed with catchup-specific insight extraction and follow-up identification.\n\n**Sanctum provides the raw data; catchup extracts insights and concrete next steps.**\n\n## Common Patterns\n\n**Feature Branch Catchup:**\n```bash\nBASE=$(git merge-base main HEAD)\ngit diff --stat main...HEAD\ngit log --oneline main...HEAD\n```\n\n**Release Catchup:**\n```bash\ngit diff --stat v1.0.0...v1.1.0\ngit log --oneline --graph v1.0.0...v1.1.0\n```\n\n**Daily Standup Catchup:**\n```bash\ngit log --since=\"yesterday\" --oneline --all\ngit diff --stat HEAD@{yesterday}...HEAD\n```\n\nFile v1.9.16:modules/log-analysis-patterns.md\n\n---\nname: log-analysis-patterns\ndescription: System log and event stream analysis patterns for catchup\nparent_skill: imbue:catchup\ncategory: analysis-patterns\ntags: [logs, events, monitoring, time-series]\nestimated_tokens: 300\n---\n\n# Log Analysis Patterns\n\n## System Log Catchup\n\nWhen catching up on system behavior via logs:\n\n**Context Establishment:**\n- Identify time window: \"Last check was [timestamp]\"\n- Note log sources (application, system, service)\n- Identify environment (prod, staging, dev)\n- Baseline normal behavior\n\n**Delta Capture:**\n- Count log entries by severity (ERROR, WARN, INFO)\n- Enumerate unique error types\n- Identify anomalies or patterns\n- Note frequency changes (spike, drop, stable)\n\n**Efficient Commands:**\n```bash\n# Count by severity\ngrep -c \"ERROR\" logfile.log\ngrep -c \"WARN\" logfile.log\n\n# Unique error messages\ngrep \"ERROR\" logfile.log | cut -d: -f3 | sort | uniq -c | sort -rn | head -20\n\n# Time-based filtering\nawk '$1 >= \"2025-12-04\" && $1 <= \"2025-12-05\"' logfile.log\n```\n\n## Event Stream Analysis\n\nFor application events, audit logs, or metrics:\n\n**Context:**\n- Event source and schema\n- Baseline event rate\n- Time window of interest\n- Expected vs actual patterns\n\n**Delta:**\n- New event types introduced\n- Event rate changes (throughput)\n- Failed vs successful event ratios\n- Outliers or anomalies\n\n**Insights:**\n- Performance trends (response times, throughput)\n- Error patterns (recurring, transient, progressive)\n- User behavior changes\n- System health indicators\n\n## Time-Window Analysis\n\n**Comparing time windows:**\n```bash\n# Events today vs yesterday\ncomm -13 <(grep \"2025-12-04\" events.log | sort) \\\n <(grep \"2025-12-05\" events.log | sort)\n\n# Hourly breakdown\nawk '{print substr($1,12,2)}' logfile.log | sort | uniq -c\n```\n\n**Pattern Detection:**\n- Periodic patterns (hourly, daily, weekly cycles)\n- Correlation between events\n- Cascading failures\n- Recovery patterns\n\n## Metric-Based Catchup\n\nWhen logs include metrics or measurements:\n\n**Delta:**\n- Min/max/avg changes\n- Percentile shifts (p50, p95, p99)\n- Threshold violations\n- Trend direction (improving, degrading, stable)\n\n**Insights:**\n- Capacity planning needs\n- Performance regression sources\n- Resource utilization trends\n- SLA compliance status\n\n## Token Conservation\n\n- Use aggregation (counts, uniques) over raw logs\n- Sample representative entries, don't reproduce all\n- Reference log files + line numbers for detail\n- Summarize patterns rather than listing every entry\n- Defer deep debugging to specialized tools/skills\n\nFile v1.9.16:skill-card.md\n\n## Description:
\nSummarizes recent git changes for context recovery after session breaks.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[athola](https://clawhub.ai/user/athola)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and team members use this skill to get up to speed after time away, handoffs, or session breaks by summarizing recent repository, document, meeting, sprint, or log changes into key changes, follow-ups, and open questions.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill may activate on generic status or progress requests and inspect private repositories or sensitive logs.
\nMitigation: Confirm the catch-up scope first and review the files, repositories, or logs the agent plans to inspect before analysis.
\nRisk: Summaries of changes, logs, or documents may omit important details or produce misleading follow-up guidance.
\nMitigation: Require concise source references and review the summary before using it for planning, review, or handoff decisions.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/athola/skills/nm-imbue-catchup)
\n- [Claude Night Market Imbue plugin](https://github.com/athola/claude-night-market/tree/master/plugins/imbue)
\n\n\n## Skill Output:
\n**Output Type(s):** [markdown, shell commands, guidance]
\n**Output Format:** [Markdown summary with optional inline shell commands]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Uses concise summaries, referenced paths or lines, and explicit follow-up items.]
\n\n## Skill Version(s):
\n1.9.16 (source: server release evidence; artifact frontmatter reports 1.9.8)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.9.14: 6 files, 7763 bytes\n\nFiles: modules/document-analysis-patterns.md (2358b), modules/git-catchup-patterns.md (3338b), modules/log-analysis-patterns.md (2540b), skill-card.md (2179b), SKILL.md (3757b), _meta.json (136b)\n\nFile v1.9.14:SKILL.md\n\n---\nname: catchup\ndescription: Summarizes recent git changes for context recovery after session breaks\nversion: 1.9.8\ntriggers:\n - summarization\n - context-acquisition\n - insights\n - follow-ups\n - resuming work after a gap or handing off to another session\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/imbue\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.imbue:proof-of-work\"]}}}\nsource: claude-night-market\nsource_plugin: imbue\n---\n\n> **Night Market Skill** — ported from [claude-night-market/imbue](https://github.com/athola/claude-night-market/tree/master/plugins/imbue). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n## Table of Contents\n\n- [Overview](#overview)\n- [When to Use](#when-to-use)\n- [Activation](#activation)\n- [Progressive Loading](#progressive-loading)\n- [4-Step Methodology](#4-step-methodology)\n- [Output Format](#output-format)\n\n# Catchup Analysis Methodology\n\n## Overview\n\nStructured 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.\n\n## When To Use\n- Joining ongoing work or returning after absence\n- Before planning or reviewing handoffs\n- Any \"what happened and what's next\" context\n\n## When NOT To Use\n\n- Doing detailed\n diff analysis - use diff-analysis instead\n- Full code review needed\n - use review-core instead\n\n## Activation\n**Keywords**: catchup, summary, status, progress, context, handoff\n**Cues**: \"get me up to speed\", \"current status\", \"summarize progress\"\n\n## Progressive Loading\n\nLoad modules based on context:\n\n**Git**: Load `modules/git-catchup-patterns.md` for git commands. Consider `sanctum:git-workspace-review` for initial data gathering.\n\n**Documents/Notes**: Load `modules/document-analysis-patterns.md` for meeting notes, sprint tracking, document revisions.\n\n**Logs/Events**: Load `modules/log-analysis-patterns.md` for time-series and metric analysis.\n\n**Always Available**: `imbue:proof-of-work`, TodoWrite workflow, structured output.\n\n## Required TodoWrite Items\n1. `catchup:context-confirmed` - Boundaries established\n2. `catchup:delta-captured` - Changes enumerated\n3. `catchup:insights-extracted` - Themes identified\n4. `catchup:followups-recorded` - Actions captured\n\n## 4-Step Methodology\n\n### Step 1: Confirm Context\nDefine scope (git branch, sprint, meetings), baseline (last state), and current target. See modules for commands.\n\n### Step 2: Capture Delta\nEnumerate changed items with metrics. Prioritize source/config/docs over generated artifacts. See modules for strategies.\n\n### Step 3: Extract Insights\nPer item: **What** (change), **Why** (motivation), **Implications** (tests/risks/deps). Rollup into themes.\n\n### Step 4: Record Follow-ups\nCapture: Tests, Documentation, Reviews, Blockers, Questions. If none, state explicitly.\n\n## Output Format\n```\n## Summary\n[2-3 sentence theme + risk overview]\n\n## Key Changes\n- [Item]: [what/why/implication]\n\n## Follow-ups\n- [ ] [Action with owner]\n\n## Blockers/Questions\n- [Item requiring resolution]\n```\n**Verification:** Run the command with `--help` flag to verify availability.\n\n## Integration\nUse `imbue:diff-analysis` for risk assessment, `imbue:proof-of-work` for reproducibility, `sanctum:git-workspace-review` for git data. Feed to `brainstorming` or `writing-plans` as needed.\n\n## Token Conservation\nReference paths and lines (don't reproduce). Summarize outputs. Defer deep analysis. Use progressive loading.\n\n## Exit Criteria\n- Four TodoWrite items completed\n- Context/delta/insights/follow-ups captured\n- Stakeholders understand state without re-reading sources\n\nFile v1.9.14:_meta.json\n\n{\n \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n \"slug\": \"nm-imbue-catchup\",\n \"version\": \"1.9.14\",\n \"publishedAt\": 1782842388795\n}\n\nFile v1.9.14:modules/document-analysis-patterns.md\n\n---\nname: document-analysis-patterns\ndescription: Document and meeting notes analysis patterns for catchup\nparent_skill: imbue:catchup\ncategory: analysis-patterns\ntags: [documents, meetings, notes, tracking]\nestimated_tokens: 300\n---\n\n# Document Analysis Patterns\n\n## Meeting Notes Analysis\n\nWhen catching up on meeting notes or discussions:\n\n**Context Establishment:**\n- Identify date range: \"Last meeting I attended was [date]\"\n- Note participants involved\n- Identify meeting series or project name\n\n**Delta Capture:**\n- List topics discussed (agenda items)\n- Enumerate decisions made\n- Identify action items assigned\n- Note open questions or blocked items\n\n**Insight Extraction:**\n- What changed since last meeting?\n- What decisions affect ongoing work?\n- What consensus emerged on contentious topics?\n- What new information affects project direction?\n\n## Sprint/Ticket Catchup Patterns\n\nFor Jira, GitHub Issues, or similar tracking systems:\n\n**Context:**\n- Last sprint/milestone reviewed\n- Current sprint/milestone\n- Team velocity or capacity changes\n\n**Delta:**\n- Tickets completed since baseline\n- Tickets in progress\n- New tickets added to backlog\n- Priority shifts or re-ordering\n\n**Insights:**\n- Velocity trends (ahead/behind schedule?)\n- Risk indicators (blocked tickets, dependencies)\n- Scope changes (new requirements, deferred items)\n- Team capacity changes\n\n## Document Revision Tracking\n\nWhen reviewing evolving documents (specs, designs, RFCs):\n\n**Context:**\n- Last version reviewed (version number, date, or commit)\n- Current version\n- Document type and audience\n\n**Delta:**\n- Sections added, modified, or removed\n- Comments or review feedback incorporated\n- Status changes (draft → review → approved)\n\n**Insights:**\n- Requirements changes and rationale\n- Design decisions made or reversed\n- Unresolved discussions or open questions\n- Approval status and blockers\n\n## Generic Document Delta Patterns\n\n**Efficient Enumeration:**\n- Focus on substantive changes (ignore typos, formatting)\n- Identify authors/contributors to understand perspective\n- Note timestamp for context\n- Track references to external decisions or dependencies\n\n**Token Conservation:**\n- Summarize content rather than quoting verbatim\n- Reference section headings + key points\n- List decisions/actions rather than narrative\n- Use bullet points for scanning efficiency\n\nFile v1.9.14:modules/git-catchup-patterns.md\n\n---\nname: git-catchup-patterns\ndescription: Git-specific commands and patterns for catchup analysis\nparent_skill: imbue:catchup\ncategory: technical-patterns\ntags: [git, version-control, delta-capture]\nestimated_tokens: 400\n---\n\n# Git Catchup Patterns\n\n## Git Context Establishment\n\nUse these commands to establish git repository context:\n\n```bash\npwd # Show current directory\ngit status -sb | head -n 1 # Show current branch and status\ngit rev-parse --abbrev-ref --symbolic-full-name @{u} # Show the upstream branch, if one is being tracked\n```\n\nThese help answer:\n- Where am I working?\n- What branch am I on?\n- Is this branch tracking a remote?\n\n## Git Delta Capture\n\nEfficiently capture changes between states:\n\n```bash\ngit diff --stat ${BASE}...HEAD # Show summary statistics\ngit diff --name-only ${BASE}...HEAD # List changed files\ngit log --oneline ${BASE}...HEAD # Show commit history\n```\n\n**Key Patterns:**\n- Use `--stat` for high-level overview (files changed, insertions/deletions)\n- Use `--name-only` for enumeration without content\n- Use `...` three-dot syntax to show changes on current branch since divergence\n\n## Semantic Delta Capture (sem)\n\nWhen sem is available (see `leyline:sem-integration`),\nenhance delta capture with entity-level diffs:\n\n```bash\n# Entity-level change summary across commits\nsem diff --format json ${BASE}...HEAD\n\n# Track a specific entity's evolution\nsem log \n```\n\n> **Note:** sem may not support three-dot (`...`) range\n> syntax directly. If `sem diff` fails with a range,\n> resolve the merge base first:\n> `BASE=$(git merge-base main HEAD)` then pass\n> `sem diff --format json $BASE HEAD`.\n\n**Key advantages over git diff --stat:**\n\n- Shows which functions/classes changed, not just files\n- Distinguishes additions from modifications from renames\n- `sem log` tracks an entity across renames\n\nWhen sem is unavailable, fall back to the git commands\nin the section above.\n\n## Git-Specific Insights Extraction\n\nTargeted inspection commands:\n\n```bash\ngit show --stat # Show specific commit changes\ngit diff ${BASE}...HEAD -- path/to/file # Examine specific file changes\ngit log -p --follow -- path/to/file # File history with patches\n```\n\n**Efficient Reading:**\n- Use `git show` for commit-level understanding\n- Use `git diff` with file paths for focused analysis\n- Avoid `git log -p` without limits (token-heavy)\n\n## Integration with Sanctum\n\n**Before running catchup analysis**, use `sanctum:git-workspace-review` to gather:\n- Repository confirmation (pwd, branch)\n- Status overview (staged vs unstaged)\n- Diff statistics\n- Diff details\n\nThen proceed with catchup-specific insight extraction and follow-up identification.\n\n**Sanctum provides the raw data; catchup extracts insights and concrete next steps.**\n\n## Common Patterns\n\n**Feature Branch Catchup:**\n```bash\nBASE=$(git merge-base main HEAD)\ngit diff --stat main...HEAD\ngit log --oneline main...HEAD\n```\n\n**Release Catchup:**\n```bash\ngit diff --stat v1.0.0...v1.1.0\ngit log --oneline --graph v1.0.0...v1.1.0\n```\n\n**Daily Standup Catchup:**\n```bash\ngit log --since=\"yesterday\" --oneline --all\ngit diff --stat HEAD@{yesterday}...HEAD\n```\n\nFile v1.9.14:modules/log-analysis-patterns.md\n\n---\nname: log-analysis-patterns\ndescription: System log and event stream analysis patterns for catchup\nparent_skill: imbue:catchup\ncategory: analysis-patterns\ntags: [logs, events, monitoring, time-series]\nestimated_tokens: 300\n---\n\n# Log Analysis Patterns\n\n## System Log Catchup\n\nWhen catching up on system behavior via logs:\n\n**Context Establishment:**\n- Identify time window: \"Last check was [timestamp]\"\n- Note log sources (application, system, service)\n- Identify environment (prod, staging, dev)\n- Baseline normal behavior\n\n**Delta Capture:**\n- Count log entries by severity (ERROR, WARN, INFO)\n- Enumerate unique error types\n- Identify anomalies or patterns\n- Note frequency changes (spike, drop, stable)\n\n**Efficient Commands:**\n```bash\n# Count by severity\ngrep -c \"ERROR\" logfile.log\ngrep -c \"WARN\" logfile.log\n\n# Unique error messages\ngrep \"ERROR\" logfile.log | cut -d: -f3 | sort | uniq -c | sort -rn | head -20\n\n# Time-based filtering\nawk '$1 >= \"2025-12-04\" && $1 <= \"2025-12-05\"' logfile.log\n```\n\n## Event Stream Analysis\n\nFor application events, audit logs, or metrics:\n\n**Context:**\n- Event source and schema\n- Baseline event rate\n- Time window of interest\n- Expected vs actual patterns\n\n**Delta:**\n- New event types introduced\n- Event rate changes (throughput)\n- Failed vs successful event ratios\n- Outliers or anomalies\n\n**Insights:**\n- Performance trends (response times, throughput)\n- Error patterns (recurring, transient, progressive)\n- User behavior changes\n- System health indicators\n\n## Time-Window Analysis\n\n**Comparing time windows:**\n```bash\n# Events today vs yesterday\ncomm -13 <(grep \"2025-12-04\" events.log | sort) \\\n <(grep \"2025-12-05\" events.log | sort)\n\n# Hourly breakdown\nawk '{print substr($1,12,2)}' logfile.log | sort | uniq -c\n```\n\n**Pattern Detection:**\n- Periodic patterns (hourly, daily, weekly cycles)\n- Correlation between events\n- Cascading failures\n- Recovery patterns\n\n## Metric-Based Catchup\n\nWhen logs include metrics or measurements:\n\n**Delta:**\n- Min/max/avg changes\n- Percentile shifts (p50, p95, p99)\n- Threshold violations\n- Trend direction (improving, degrading, stable)\n\n**Insights:**\n- Capacity planning needs\n- Performance regression sources\n- Resource utilization trends\n- SLA compliance status\n\n## Token Conservation\n\n- Use aggregation (counts, uniques) over raw logs\n- Sample representative entries, don't reproduce all\n- Reference log files + line numbers for detail\n- Summarize patterns rather than listing every entry\n- Defer deep debugging to specialized tools/skills\n\nFile v1.9.14:skill-card.md\n\n## Description:
\nSummarizes recent work so an agent or collaborator can recover context after a break, handoff, or status check.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[athola](https://clawhub.ai/user/athola)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers, engineers, and project contributors use this skill to get up to speed on recent git changes, meeting notes, sprint updates, document revisions, or logs. It helps capture scope, deltas, themes, follow-ups, blockers, and questions without re-reading every source.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: Unscoped catchup requests can produce incomplete or misleading summaries when the baseline, branch, date range, sprint, or log window is unclear.
\nMitigation: Confirm the scope and baseline before summarizing, then record follow-ups, blockers, and questions explicitly.
\nRisk: Logs and private notes may contain sensitive information.
\nMitigation: Use only inputs approved for the agent session and redact sensitive values before analysis.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/athola/skills/nm-imbue-catchup)
\n- [Imbue plugin homepage](https://github.com/athola/claude-night-market/tree/master/plugins/imbue)
\n\n\n## Skill Output:
\n**Output Type(s):** [Text, Markdown, Shell commands, Guidance]
\n**Output Format:** [Markdown summary with bullet lists, task checkboxes, and optional shell command snippets]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Uses scoped inputs such as a branch, date range, sprint, document revision, or log window; summaries should reference source paths and lines rather than reproduce full inputs.]
\n\n## Skill Version(s):
\n1.9.14 (source: server release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.9.13: 6 files, 7780 bytes\n\nFiles: modules/document-analysis-patterns.md (2358b), modules/git-catchup-patterns.md (3338b), modules/log-analysis-patterns.md (2540b), skill-card.md (2218b), SKILL.md (3757b), _meta.json (136b)\n\nFile v1.9.13:SKILL.md\n\n---\nname: catchup\ndescription: Summarizes recent git changes for context recovery after session breaks\nversion: 1.9.8\ntriggers:\n - summarization\n - context-acquisition\n - insights\n - follow-ups\n - resuming work after a gap or handing off to another session\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/imbue\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.imbue:proof-of-work\"]}}}\nsource: claude-night-market\nsource_plugin: imbue\n---\n\n> **Night Market Skill** — ported from [claude-night-market/imbue](https://github.com/athola/claude-night-market/tree/master/plugins/imbue). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n## Table of Contents\n\n- [Overview](#overview)\n- [When to Use](#when-to-use)\n- [Activation](#activation)\n- [Progressive Loading](#progressive-loading)\n- [4-Step Methodology](#4-step-methodology)\n- [Output Format](#output-format)\n\n# Catchup Analysis Methodology\n\n## Overview\n\nStructured 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.\n\n## When To Use\n- Joining ongoing work or returning after absence\n- Before planning or reviewing handoffs\n- Any \"what happened and what's next\" context\n\n## When NOT To Use\n\n- Doing detailed\n diff analysis - use diff-analysis instead\n- Full code review needed\n - use review-core instead\n\n## Activation\n**Keywords**: catchup, summary, status, progress, context, handoff\n**Cues**: \"get me up to speed\", \"current status\", \"summarize progress\"\n\n## Progressive Loading\n\nLoad modules based on context:\n\n**Git**: Load `modules/git-catchup-patterns.md` for git commands. Consider `sanctum:git-workspace-review` for initial data gathering.\n\n**Documents/Notes**: Load `modules/document-analysis-patterns.md` for meeting notes, sprint tracking, document revisions.\n\n**Logs/Events**: Load `modules/log-analysis-patterns.md` for time-series and metric analysis.\n\n**Always Available**: `imbue:proof-of-work`, TodoWrite workflow, structured output.\n\n## Required TodoWrite Items\n1. `catchup:context-confirmed` - Boundaries established\n2. `catchup:delta-captured` - Changes enumerated\n3. `catchup:insights-extracted` - Themes identified\n4. `catchup:followups-recorded` - Actions captured\n\n## 4-Step Methodology\n\n### Step 1: Confirm Context\nDefine scope (git branch, sprint, meetings), baseline (last state), and current target. See modules for commands.\n\n### Step 2: Capture Delta\nEnumerate changed items with metrics. Prioritize source/config/docs over generated artifacts. See modules for strategies.\n\n### Step 3: Extract Insights\nPer item: **What** (change), **Why** (motivation), **Implications** (tests/risks/deps). Rollup into themes.\n\n### Step 4: Record Follow-ups\nCapture: Tests, Documentation, Reviews, Blockers, Questions. If none, state explicitly.\n\n## Output Format\n```\n## Summary\n[2-3 sentence theme + risk overview]\n\n## Key Changes\n- [Item]: [what/why/implication]\n\n## Follow-ups\n- [ ] [Action with owner]\n\n## Blockers/Questions\n- [Item requiring resolution]\n```\n**Verification:** Run the command with `--help` flag to verify availability.\n\n## Integration\nUse `imbue:diff-analysis` for risk assessment, `imbue:proof-of-work` for reproducibility, `sanctum:git-workspace-review` for git data. Feed to `brainstorming` or `writing-plans` as needed.\n\n## Token Conservation\nReference paths and lines (don't reproduce). Summarize outputs. Defer deep analysis. Use progressive loading.\n\n## Exit Criteria\n- Four TodoWrite items completed\n- Context/delta/insights/follow-ups captured\n- Stakeholders understand state without re-reading sources\n\nFile v1.9.13:_meta.json\n\n{\n \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n \"slug\": \"nm-imbue-catchup\",\n \"version\": \"1.9.13\",\n \"publishedAt\": 1782577115730\n}\n\nFile v1.9.13:modules/document-analysis-patterns.md\n\n---\nname: document-analysis-patterns\ndescription: Document and meeting notes analysis patterns for catchup\nparent_skill: imbue:catchup\ncategory: analysis-patterns\ntags: [documents, meetings, notes, tracking]\nestimated_tokens: 300\n---\n\n# Document Analysis Patterns\n\n## Meeting Notes Analysis\n\nWhen catching up on meeting notes or discussions:\n\n**Context Establishment:**\n- Identify date range: \"Last meeting I attended was [date]\"\n- Note participants involved\n- Identify meeting series or project name\n\n**Delta Capture:**\n- List topics discussed (agenda items)\n- Enumerate decisions made\n- Identify action items assigned\n- Note open questions or blocked items\n\n**Insight Extraction:**\n- What changed since last meeting?\n- What decisions affect ongoing work?\n- What consensus emerged on contentious topics?\n- What new information affects project direction?\n\n## Sprint/Ticket Catchup Patterns\n\nFor Jira, GitHub Issues, or similar tracking systems:\n\n**Context:**\n- Last sprint/milestone reviewed\n- Current sprint/milestone\n- Team velocity or capacity changes\n\n**Delta:**\n- Tickets completed since baseline\n- Tickets in progress\n- New tickets added to backlog\n- Priority shifts or re-ordering\n\n**Insights:**\n- Velocity trends (ahead/behind schedule?)\n- Risk indicators (blocked tickets, dependencies)\n- Scope changes (new requirements, deferred items)\n- Team capacity changes\n\n## Document Revision Tracking\n\nWhen reviewing evolving documents (specs, designs, RFCs):\n\n**Context:**\n- Last version reviewed (version number, date, or commit)\n- Current version\n- Document type and audience\n\n**Delta:**\n- Sections added, modified, or removed\n- Comments or review feedback incorporated\n- Status changes (draft → review → approved)\n\n**Insights:**\n- Requirements changes and rationale\n- Design decisions made or reversed\n- Unresolved discussions or open questions\n- Approval status and blockers\n\n## Generic Document Delta Patterns\n\n**Efficient Enumeration:**\n- Focus on substantive changes (ignore typos, formatting)\n- Identify authors/contributors to understand perspective\n- Note timestamp for context\n- Track references to external decisions or dependencies\n\n**Token Conservation:**\n- Summarize content rather than quoting verbatim\n- Reference section headings + key points\n- List decisions/actions rather than narrative\n- Use bullet points for scanning efficiency\n\nFile v1.9.13:modules/git-catchup-patterns.md\n\n---\nname: git-catchup-patterns\ndescription: Git-specific commands and patterns for catchup analysis\nparent_skill: imbue:catchup\ncategory: technical-patterns\ntags: [git, version-control, delta-capture]\nestimated_tokens: 400\n---\n\n# Git Catchup Patterns\n\n## Git Context Establishment\n\nUse these commands to establish git repository context:\n\n```bash\npwd # Show current directory\ngit status -sb | head -n 1 # Show current branch and status\ngit rev-parse --abbrev-ref --symbolic-full-name @{u} # Show the upstream branch, if one is being tracked\n```\n\nThese help answer:\n- Where am I working?\n- What branch am I on?\n- Is this branch tracking a remote?\n\n## Git Delta Capture\n\nEfficiently capture changes between states:\n\n```bash\ngit diff --stat ${BASE}...HEAD # Show summary statistics\ngit diff --name-only ${BASE}...HEAD # List changed files\ngit log --oneline ${BASE}...HEAD # Show commit history\n```\n\n**Key Patterns:**\n- Use `--stat` for high-level overview (files changed, insertions/deletions)\n- Use `--name-only` for enumeration without content\n- Use `...` three-dot syntax to show changes on current branch since divergence\n\n## Semantic Delta Capture (sem)\n\nWhen sem is available (see `leyline:sem-integration`),\nenhance delta capture with entity-level diffs:\n\n```bash\n# Entity-level change summary across commits\nsem diff --format json ${BASE}...HEAD\n\n# Track a specific entity's evolution\nsem log \n```\n\n> **Note:** sem may not support three-dot (`...`) range\n> syntax directly. If `sem diff` fails with a range,\n> resolve the merge base first:\n> `BASE=$(git merge-base main HEAD)` then pass\n> `sem diff --format json $BASE HEAD`.\n\n**Key advantages over git diff --stat:**\n\n- Shows which functions/classes changed, not just files\n- Distinguishes additions from modifications from renames\n- `sem log` tracks an entity across renames\n\nWhen sem is unavailable, fall back to the git commands\nin the section above.\n\n## Git-Specific Insights Extraction\n\nTargeted inspection commands:\n\n```bash\ngit show --stat # Show specific commit changes\ngit diff ${BASE}...HEAD -- path/to/file # Examine specific file changes\ngit log -p --follow -- path/to/file # File history with patches\n```\n\n**Efficient Reading:**\n- Use `git show` for commit-level understanding\n- Use `git diff` with file paths for focused analysis\n- Avoid `git log -p` without limits (token-heavy)\n\n## Integration with Sanctum\n\n**Before running catchup analysis**, use `sanctum:git-workspace-review` to gather:\n- Repository confirmation (pwd, branch)\n- Status overview (staged vs unstaged)\n- Diff statistics\n- Diff details\n\nThen proceed with catchup-specific insight extraction and follow-up identification.\n\n**Sanctum provides the raw data; catchup extracts insights and concrete next steps.**\n\n## Common Patterns\n\n**Feature Branch Catchup:**\n```bash\nBASE=$(git merge-base main HEAD)\ngit diff --stat main...HEAD\ngit log --oneline main...HEAD\n```\n\n**Release Catchup:**\n```bash\ngit diff --stat v1.0.0...v1.1.0\ngit log --oneline --graph v1.0.0...v1.1.0\n```\n\n**Daily Standup Catchup:**\n```bash\ngit log --since=\"yesterday\" --oneline --all\ngit diff --stat HEAD@{yesterday}...HEAD\n```\n\nFile v1.9.13:modules/log-analysis-patterns.md\n\n---\nname: log-analysis-patterns\ndescription: System log and event stream analysis patterns for catchup\nparent_skill: imbue:catchup\ncategory: analysis-patterns\ntags: [logs, events, monitoring, time-series]\nestimated_tokens: 300\n---\n\n# Log Analysis Patterns\n\n## System Log Catchup\n\nWhen catching up on system behavior via logs:\n\n**Context Establishment:**\n- Identify time window: \"Last check was [timestamp]\"\n- Note log sources (application, system, service)\n- Identify environment (prod, staging, dev)\n- Baseline normal behavior\n\n**Delta Capture:**\n- Count log entries by severity (ERROR, WARN, INFO)\n- Enumerate unique error types\n- Identify anomalies or patterns\n- Note frequency changes (spike, drop, stable)\n\n**Efficient Commands:**\n```bash\n# Count by severity\ngrep -c \"ERROR\" logfile.log\ngrep -c \"WARN\" logfile.log\n\n# Unique error messages\ngrep \"ERROR\" logfile.log | cut -d: -f3 | sort | uniq -c | sort -rn | head -20\n\n# Time-based filtering\nawk '$1 >= \"2025-12-04\" && $1 <= \"2025-12-05\"' logfile.log\n```\n\n## Event Stream Analysis\n\nFor application events, audit logs, or metrics:\n\n**Context:**\n- Event source and schema\n- Baseline event rate\n- Time window of interest\n- Expected vs actual patterns\n\n**Delta:**\n- New event types introduced\n- Event rate changes (throughput)\n- Failed vs successful event ratios\n- Outliers or anomalies\n\n**Insights:**\n- Performance trends (response times, throughput)\n- Error patterns (recurring, transient, progressive)\n- User behavior changes\n- System health indicators\n\n## Time-Window Analysis\n\n**Comparing time windows:**\n```bash\n# Events today vs yesterday\ncomm -13 <(grep \"2025-12-04\" events.log | sort) \\\n <(grep \"2025-12-05\" events.log | sort)\n\n# Hourly breakdown\nawk '{print substr($1,12,2)}' logfile.log | sort | uniq -c\n```\n\n**Pattern Detection:**\n- Periodic patterns (hourly, daily, weekly cycles)\n- Correlation between events\n- Cascading failures\n- Recovery patterns\n\n## Metric-Based Catchup\n\nWhen logs include metrics or measurements:\n\n**Delta:**\n- Min/max/avg changes\n- Percentile shifts (p50, p95, p99)\n- Threshold violations\n- Trend direction (improving, degrading, stable)\n\n**Insights:**\n- Capacity planning needs\n- Performance regression sources\n- Resource utilization trends\n- SLA compliance status\n\n## Token Conservation\n\n- Use aggregation (counts, uniques) over raw logs\n- Sample representative entries, don't reproduce all\n- Reference log files + line numbers for detail\n- Summarize patterns rather than listing every entry\n- Defer deep debugging to specialized tools/skills\n\nFile v1.9.13:skill-card.md\n\n## Description:
\nSummarizes recent git changes for context recovery after session breaks.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[athola](https://clawhub.ai/user/athola)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and team members use this skill to catch up on recent repository, document, meeting, sprint, or log changes after an absence, handoff, or interrupted work session.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: Session catchup can preserve or restate sensitive context from previous work.
\nMitigation: Avoid using the skill with secrets or confidential material, and periodically clean up named sessions that are no longer needed.
\nRisk: Generated summaries may omit, misprioritize, or misinterpret recent changes.
\nMitigation: Review source files, diffs, logs, or documents before relying on the summary for planning, reviews, or handoffs.
\nRisk: Suggested shell commands for git or log analysis may be run in the wrong repository, branch, or time window.
\nMitigation: Confirm the working directory, branch, baseline, and target scope before running commands or acting on their results.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/athola/skills/nm-imbue-catchup)
\n- [Metadata homepage](https://github.com/athola/claude-night-market/tree/master/plugins/imbue)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, shell commands, guidance]
\n**Output Format:** [Markdown with concise summaries, action lists, blockers, and optional shell command examples]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May reference local files, git ranges, logs, documents, and session context; no executable code is bundled.]
\n\n## Skill Version(s):
\n1.9.13 (source: server release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.9.12: 6 files, 7731 bytes\n\nFiles: modules/document-analysis-patterns.md (2358b), modules/git-catchup-patterns.md (3338b), modules/log-analysis-patterns.md (2540b), skill-card.md (2086b), SKILL.md (3757b), _meta.json (136b)\n\nFile v1.9.12:SKILL.md\n\n---\nname: catchup\ndescription: Summarizes recent git changes for context recovery after session breaks\nversion: 1.9.8\ntriggers:\n - summarization\n - context-acquisition\n - insights\n - follow-ups\n - resuming work after a gap or handing off to another session\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/imbue\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.imbue:proof-of-work\"]}}}\nsource: claude-night-market\nsource_plugin: imbue\n---\n\n> **Night Market Skill** — ported from [claude-night-market/imbue](https://github.com/athola/claude-night-market/tree/master/plugins/imbue). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n## Table of Contents\n\n- [Overview](#overview)\n- [When to Use](#when-to-use)\n- [Activation](#activation)\n- [Progressive Loading](#progressive-loading)\n- [4-Step Methodology](#4-step-methodology)\n- [Output Format](#output-format)\n\n# Catchup Analysis Methodology\n\n## Overview\n\nStructured 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.\n\n## When To Use\n- Joining ongoing work or returning after absence\n- Before planning or reviewing handoffs\n- Any \"what happened and what's next\" context\n\n## When NOT To Use\n\n- Doing detailed\n diff analysis - use diff-analysis instead\n- Full code review needed\n - use review-core instead\n\n## Activation\n**Keywords**: catchup, summary, status, progress, context, handoff\n**Cues**: \"get me up to speed\", \"current status\", \"summarize progress\"\n\n## Progressive Loading\n\nLoad modules based on context:\n\n**Git**: Load `modules/git-catchup-patterns.md` for git commands. Consider `sanctum:git-workspace-review` for initial data gathering.\n\n**Documents/Notes**: Load `modules/document-analysis-patterns.md` for meeting notes, sprint tracking, document revisions.\n\n**Logs/Events**: Load `modules/log-analysis-patterns.md` for time-series and metric analysis.\n\n**Always Available**: `imbue:proof-of-work`, TodoWrite workflow, structured output.\n\n## Required TodoWrite Items\n1. `catchup:context-confirmed` - Boundaries established\n2. `catchup:delta-captured` - Changes enumerated\n3. `catchup:insights-extracted` - Themes identified\n4. `catchup:followups-recorded` - Actions captured\n\n## 4-Step Methodology\n\n### Step 1: Confirm Context\nDefine scope (git branch, sprint, meetings), baseline (last state), and current target. See modules for commands.\n\n### Step 2: Capture Delta\nEnumerate changed items with metrics. Prioritize source/config/docs over generated artifacts. See modules for strategies.\n\n### Step 3: Extract Insights\nPer item: **What** (change), **Why** (motivation), **Implications** (tests/risks/deps). Rollup into themes.\n\n### Step 4: Record Follow-ups\nCapture: Tests, Documentation, Reviews, Blockers, Questions. If none, state explicitly.\n\n## Output Format\n```\n## Summary\n[2-3 sentence theme + risk overview]\n\n## Key Changes\n- [Item]: [what/why/implication]\n\n## Follow-ups\n- [ ] [Action with owner]\n\n## Blockers/Questions\n- [Item requiring resolution]\n```\n**Verification:** Run the command with `--help` flag to verify availability.\n\n## Integration\nUse `imbue:diff-analysis` for risk assessment, `imbue:proof-of-work` for reproducibility, `sanctum:git-workspace-review` for git data. Feed to `brainstorming` or `writing-plans` as needed.\n\n## Token Conservation\nReference paths and lines (don't reproduce). Summarize outputs. Defer deep analysis. Use progressive loading.\n\n## Exit Criteria\n- Four TodoWrite items completed\n- Context/delta/insights/follow-ups captured\n- Stakeholders understand state without re-reading sources\n\nFile v1.9.12:_meta.json\n\n{\n \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n \"slug\": \"nm-imbue-catchup\",\n \"version\": \"1.9.12\",\n \"publishedAt\": 1781838760609\n}\n\nFile v1.9.12:modules/document-analysis-patterns.md\n\n---\nname: document-analysis-patterns\ndescription: Document and meeting notes analysis patterns for catchup\nparent_skill: imbue:catchup\ncategory: analysis-patterns\ntags: [documents, meetings, notes, tracking]\nestimated_tokens: 300\n---\n\n# Document Analysis Patterns\n\n## Meeting Notes Analysis\n\nWhen catching up on meeting notes or discussions:\n\n**Context Establishment:**\n- Identify date range: \"Last meeting I attended was [date]\"\n- Note participants involved\n- Identify meeting series or project name\n\n**Delta Capture:**\n- List topics discussed (agenda items)\n- Enumerate decisions made\n- Identify action items assigned\n- Note open questions or blocked items\n\n**Insight Extraction:**\n- What changed since last meeting?\n- What decisions affect ongoing work?\n- What consensus emerged on contentious topics?\n- What new information affects project direction?\n\n## Sprint/Ticket Catchup Patterns\n\nFor Jira, GitHub Issues, or similar tracking systems:\n\n**Context:**\n- Last sprint/milestone reviewed\n- Current sprint/milestone\n- Team velocity or capacity changes\n\n**Delta:**\n- Tickets completed since baseline\n- Tickets in progress\n- New tickets added to backlog\n- Priority shifts or re-ordering\n\n**Insights:**\n- Velocity trends (ahead/behind schedule?)\n- Risk indicators (blocked tickets, dependencies)\n- Scope changes (new requirements, deferred items)\n- Team capacity changes\n\n## Document Revision Tracking\n\nWhen reviewing evolving documents (specs, designs, RFCs):\n\n**Context:**\n- Last version reviewed (version number, date, or commit)\n- Current version\n- Document type and audience\n\n**Delta:**\n- Sections added, modified, or removed\n- Comments or review feedback incorporated\n- Status changes (draft → review → approved)\n\n**Insights:**\n- Requirements changes and rationale\n- Design decisions made or reversed\n- Unresolved discussions or open questions\n- Approval status and blockers\n\n## Generic Document Delta Patterns\n\n**Efficient Enumeration:**\n- Focus on substantive changes (ignore typos, formatting)\n- Identify authors/contributors to understand perspective\n- Note timestamp for context\n- Track references to external decisions or dependencies\n\n**Token Conservation:**\n- Summarize content rather than quoting verbatim\n- Reference section headings + key points\n- List decisions/actions rather than narrative\n- Use bullet points for scanning efficiency\n\nFile v1.9.12:modules/git-catchup-patterns.md\n\n---\nname: git-catchup-patterns\ndescription: Git-specific commands and patterns for catchup analysis\nparent_skill: imbue:catchup\ncategory: technical-patterns\ntags: [git, version-control, delta-capture]\nestimated_tokens: 400\n---\n\n# Git Catchup Patterns\n\n## Git Context Establishment\n\nUse these commands to establish git repository context:\n\n```bash\npwd # Show current directory\ngit status -sb | head -n 1 # Show current branch and status\ngit rev-parse --abbrev-ref --symbolic-full-name @{u} # Show the upstream branch, if one is being tracked\n```\n\nThese help answer:\n- Where am I working?\n- What branch am I on?\n- Is this branch tracking a remote?\n\n## Git Delta Capture\n\nEfficiently capture changes between states:\n\n```bash\ngit diff --stat ${BASE}...HEAD # Show summary statistics\ngit diff --name-only ${BASE}...HEAD # List changed files\ngit log --oneline ${BASE}...HEAD # Show commit history\n```\n\n**Key Patterns:**\n- Use `--stat` for high-level overview (files changed, insertions/deletions)\n- Use `--name-only` for enumeration without content\n- Use `...` three-dot syntax to show changes on current branch since divergence\n\n## Semantic Delta Capture (sem)\n\nWhen sem is available (see `leyline:sem-integration`),\nenhance delta capture with entity-level diffs:\n\n```bash\n# Entity-level change summary across commits\nsem diff --format json ${BASE}...HEAD\n\n# Track a specific entity's evolution\nsem log \n```\n\n> **Note:** sem may not support three-dot (`...`) range\n> syntax directly. If `sem diff` fails with a range,\n> resolve the merge base first:\n> `BASE=$(git merge-base main HEAD)` then pass\n> `sem diff --format json $BASE HEAD`.\n\n**Key advantages over git diff --stat:**\n\n- Shows which functions/classes changed, not just files\n- Distinguishes additions from modifications from renames\n- `sem log` tracks an entity across renames\n\nWhen sem is unavailable, fall back to the git commands\nin the section above.\n\n## Git-Specific Insights Extraction\n\nTargeted inspection commands:\n\n```bash\ngit show --stat # Show specific commit changes\ngit diff ${BASE}...HEAD -- path/to/file # Examine specific file changes\ngit log -p --follow -- path/to/file # File history with patches\n```\n\n**Efficient Reading:**\n- Use `git show` for commit-level understanding\n- Use `git diff` with file paths for focused analysis\n- Avoid `git log -p` without limits (token-heavy)\n\n## Integration with Sanctum\n\n**Before running catchup analysis**, use `sanctum:git-workspace-review` to gather:\n- Repository confirmation (pwd, branch)\n- Status overview (staged vs unstaged)\n- Diff statistics\n- Diff details\n\nThen proceed with catchup-specific insight extraction and follow-up identification.\n\n**Sanctum provides the raw data; catchup extracts insights and concrete next steps.**\n\n## Common Patterns\n\n**Feature Branch Catchup:**\n```bash\nBASE=$(git merge-base main HEAD)\ngit diff --stat main...HEAD\ngit log --oneline main...HEAD\n```\n\n**Release Catchup:**\n```bash\ngit diff --stat v1.0.0...v1.1.0\ngit log --oneline --graph v1.0.0...v1.1.0\n```\n\n**Daily Standup Catchup:**\n```bash\ngit log --since=\"yesterday\" --oneline --all\ngit diff --stat HEAD@{yesterday}...HEAD\n```\n\nFile v1.9.12:modules/log-analysis-patterns.md\n\n---\nname: log-analysis-patterns\ndescription: System log and event stream analysis patterns for catchup\nparent_skill: imbue:catchup\ncategory: analysis-patterns\ntags: [logs, events, monitoring, time-series]\nestimated_tokens: 300\n---\n\n# Log Analysis Patterns\n\n## System Log Catchup\n\nWhen catching up on system behavior via logs:\n\n**Context Establishment:**\n- Identify time window: \"Last check was [timestamp]\"\n- Note log sources (application, system, service)\n- Identify environment (prod, staging, dev)\n- Baseline normal behavior\n\n**Delta Capture:**\n- Count log entries by severity (ERROR, WARN, INFO)\n- Enumerate unique error types\n- Identify anomalies or patterns\n- Note frequency changes (spike, drop, stable)\n\n**Efficient Commands:**\n```bash\n# Count by severity\ngrep -c \"ERROR\" logfile.log\ngrep -c \"WARN\" logfile.log\n\n# Unique error messages\ngrep \"ERROR\" logfile.log | cut -d: -f3 | sort | uniq -c | sort -rn | head -20\n\n# Time-based filtering\nawk '$1 >= \"2025-12-04\" && $1 <= \"2025-12-05\"' logfile.log\n```\n\n## Event Stream Analysis\n\nFor application events, audit logs, or metrics:\n\n**Context:**\n- Event source and schema\n- Baseline event rate\n- Time window of interest\n- Expected vs actual patterns\n\n**Delta:**\n- New event types introduced\n- Event rate changes (throughput)\n- Failed vs successful event ratios\n- Outliers or anomalies\n\n**Insights:**\n- Performance trends (response times, throughput)\n- Error patterns (recurring, transient, progressive)\n- User behavior changes\n- System health indicators\n\n## Time-Window Analysis\n\n**Comparing time windows:**\n```bash\n# Events today vs yesterday\ncomm -13 <(grep \"2025-12-04\" events.log | sort) \\\n <(grep \"2025-12-05\" events.log | sort)\n\n# Hourly breakdown\nawk '{print substr($1,12,2)}' logfile.log | sort | uniq -c\n```\n\n**Pattern Detection:**\n- Periodic patterns (hourly, daily, weekly cycles)\n- Correlation between events\n- Cascading failures\n- Recovery patterns\n\n## Metric-Based Catchup\n\nWhen logs include metrics or measurements:\n\n**Delta:**\n- Min/max/avg changes\n- Percentile shifts (p50, p95, p99)\n- Threshold violations\n- Trend direction (improving, degrading, stable)\n\n**Insights:**\n- Capacity planning needs\n- Performance regression sources\n- Resource utilization trends\n- SLA compliance status\n\n## Token Conservation\n\n- Use aggregation (counts, uniques) over raw logs\n- Sample representative entries, don't reproduce all\n- Reference log files + line numbers for detail\n- Summarize patterns rather than listing every entry\n- Defer deep debugging to specialized tools/skills\n\nFile v1.9.12:skill-card.md\n\n## Description:
\nSummarizes recent git changes for context recovery after session breaks.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[athola](https://clawhub.ai/user/athola)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers, engineers, and project collaborators use this skill to get up to speed after a session break, handoff, or absence by summarizing recent changes, key implications, follow-ups, and blockers across git repositories, notes, tickets, documents, or logs.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill may activate on broad catchup or status requests and inspect repositories, notes, issue trackers, or logs that the user points it at.
\nMitigation: Set explicit scope, baseline, time window, and allowed data sources before analysis begins.
\nRisk: Logs, documents, or notes used for catchup may contain sensitive information.
\nMitigation: Limit analysis to necessary files or systems and summarize patterns instead of reproducing sensitive raw content.
\n\n\n## Reference(s):
\n- [ClawHub release page](https://clawhub.ai/athola/nm-imbue-catchup)
\n- [OpenClaw homepage](https://github.com/athola/claude-night-market/tree/master/plugins/imbue)
\n\n\n## Skill Output:
\n**Output Type(s):** [Text, Markdown, Shell commands, Guidance]
\n**Output Format:** [Markdown summary with headings, bullets, checklists, and optional inline shell commands]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Designed for scoped catchup summaries with concise references to source paths, lines, time windows, and follow-up actions.]
\n\n## Skill Version(s):
\n1.9.12 (source: ClawHub release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.3: 6 files, 7765 bytes\n\nFiles: modules/document-analysis-patterns.md (2358b), modules/git-catchup-patterns.md (3338b), modules/log-analysis-patterns.md (2540b), skill-card.md (2226b), SKILL.md (3757b), _meta.json (135b)\n\nFile v1.0.3:SKILL.md\n\n---\nname: catchup\ndescription: Summarizes recent git changes for context recovery after session breaks\nversion: 1.9.8\ntriggers:\n - summarization\n - context-acquisition\n - insights\n - follow-ups\n - resuming work after a gap or handing off to another session\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/imbue\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.imbue:proof-of-work\"]}}}\nsource: claude-night-market\nsource_plugin: imbue\n---\n\n> **Night Market Skill** — ported from [claude-night-market/imbue](https://github.com/athola/claude-night-market/tree/master/plugins/imbue). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n## Table of Contents\n\n- [Overview](#overview)\n- [When to Use](#when-to-use)\n- [Activation](#activation)\n- [Progressive Loading](#progressive-loading)\n- [4-Step Methodology](#4-step-methodology)\n- [Output Format](#output-format)\n\n# Catchup Analysis Methodology\n\n## Overview\n\nStructured 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.\n\n## When To Use\n- Joining ongoing work or returning after absence\n- Before planning or reviewing handoffs\n- Any \"what happened and what's next\" context\n\n## When NOT To Use\n\n- Doing detailed\n diff analysis - use diff-analysis instead\n- Full code review needed\n - use review-core instead\n\n## Activation\n**Keywords**: catchup, summary, status, progress, context, handoff\n**Cues**: \"get me up to speed\", \"current status\", \"summarize progress\"\n\n## Progressive Loading\n\nLoad modules based on context:\n\n**Git**: Load `modules/git-catchup-patterns.md` for git commands. Consider `sanctum:git-workspace-review` for initial data gathering.\n\n**Documents/Notes**: Load `modules/document-analysis-patterns.md` for meeting notes, sprint tracking, document revisions.\n\n**Logs/Events**: Load `modules/log-analysis-patterns.md` for time-series and metric analysis.\n\n**Always Available**: `imbue:proof-of-work`, TodoWrite workflow, structured output.\n\n## Required TodoWrite Items\n1. `catchup:context-confirmed` - Boundaries established\n2. `catchup:delta-captured` - Changes enumerated\n3. `catchup:insights-extracted` - Themes identified\n4. `catchup:followups-recorded` - Actions captured\n\n## 4-Step Methodology\n\n### Step 1: Confirm Context\nDefine scope (git branch, sprint, meetings), baseline (last state), and current target. See modules for commands.\n\n### Step 2: Capture Delta\nEnumerate changed items with metrics. Prioritize source/config/docs over generated artifacts. See modules for strategies.\n\n### Step 3: Extract Insights\nPer item: **What** (change), **Why** (motivation), **Implications** (tests/risks/deps). Rollup into themes.\n\n### Step 4: Record Follow-ups\nCapture: Tests, Documentation, Reviews, Blockers, Questions. If none, state explicitly.\n\n## Output Format\n```\n## Summary\n[2-3 sentence theme + risk overview]\n\n## Key Changes\n- [Item]: [what/why/implication]\n\n## Follow-ups\n- [ ] [Action with owner]\n\n## Blockers/Questions\n- [Item requiring resolution]\n```\n**Verification:** Run the command with `--help` flag to verify availability.\n\n## Integration\nUse `imbue:diff-analysis` for risk assessment, `imbue:proof-of-work` for reproducibility, `sanctum:git-workspace-review` for git data. Feed to `brainstorming` or `writing-plans` as needed.\n\n## Token Conservation\nReference paths and lines (don't reproduce). Summarize outputs. Defer deep analysis. Use progressive loading.\n\n## Exit Criteria\n- Four TodoWrite items completed\n- Context/delta/insights/follow-ups captured\n- Stakeholders understand state without re-reading sources\n\nFile v1.0.3:_meta.json\n\n{\n \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n \"slug\": \"nm-imbue-catchup\",\n \"version\": \"1.0.3\",\n \"publishedAt\": 1781791670932\n}\n\nFile v1.0.3:modules/document-analysis-patterns.md\n\n---\nname: document-analysis-patterns\ndescription: Document and meeting notes analysis patterns for catchup\nparent_skill: imbue:catchup\ncategory: analysis-patterns\ntags: [documents, meetings, notes, tracking]\nestimated_tokens: 300\n---\n\n# Document Analysis Patterns\n\n## Meeting Notes Analysis\n\nWhen catching up on meeting notes or discussions:\n\n**Context Establishment:**\n- Identify date range: \"Last meeting I attended was [date]\"\n- Note participants involved\n- Identify meeting series or project name\n\n**Delta Capture:**\n- List topics discussed (agenda items)\n- Enumerate decisions made\n- Identify action items assigned\n- Note open questions or blocked items\n\n**Insight Extraction:**\n- What changed since last meeting?\n- What decisions affect ongoing work?\n- What consensus emerged on contentious topics?\n- What new information affects project direction?\n\n## Sprint/Ticket Catchup Patterns\n\nFor Jira, GitHub Issues, or similar tracking systems:\n\n**Context:**\n- Last sprint/milestone reviewed\n- Current sprint/milestone\n- Team velocity or capacity changes\n\n**Delta:**\n- Tickets completed since baseline\n- Tickets in progress\n- New tickets added to backlog\n- Priority shifts or re-ordering\n\n**Insights:**\n- Velocity trends (ahead/behind schedule?)\n- Risk indicators (blocked tickets, dependencies)\n- Scope changes (new requirements, deferred items)\n- Team capacity changes\n\n## Document Revision Tracking\n\nWhen reviewing evolving documents (specs, designs, RFCs):\n\n**Context:**\n- Last version reviewed (version number, date, or commit)\n- Current version\n- Document type and audience\n\n**Delta:**\n- Sections added, modified, or removed\n- Comments or review feedback incorporated\n- Status changes (draft → review → approved)\n\n**Insights:**\n- Requirements changes and rationale\n- Design decisions made or reversed\n- Unresolved discussions or open questions\n- Approval status and blockers\n\n## Generic Document Delta Patterns\n\n**Efficient Enumeration:**\n- Focus on substantive changes (ignore typos, formatting)\n- Identify authors/contributors to understand perspective\n- Note timestamp for context\n- Track references to external decisions or dependencies\n\n**Token Conservation:**\n- Summarize content rather than quoting verbatim\n- Reference section headings + key points\n- List decisions/actions rather than narrative\n- Use bullet points for scanning efficiency\n\nFile v1.0.3:modules/git-catchup-patterns.md\n\n---\nname: git-catchup-patterns\ndescription: Git-specific commands and patterns for catchup analysis\nparent_skill: imbue:catchup\ncategory: technical-patterns\ntags: [git, version-control, delta-capture]\nestimated_tokens: 400\n---\n\n# Git Catchup Patterns\n\n## Git Context Establishment\n\nUse these commands to establish git repository context:\n\n```bash\npwd # Show current directory\ngit status -sb | head -n 1 # Show current branch and status\ngit rev-parse --abbrev-ref --symbolic-full-name @{u} # Show the upstream branch, if one is being tracked\n```\n\nThese help answer:\n- Where am I working?\n- What branch am I on?\n- Is this branch tracking a remote?\n\n## Git Delta Capture\n\nEfficiently capture changes between states:\n\n```bash\ngit diff --stat ${BASE}...HEAD # Show summary statistics\ngit diff --name-only ${BASE}...HEAD # List changed files\ngit log --oneline ${BASE}...HEAD # Show commit history\n```\n\n**Key Patterns:**\n- Use `--stat` for high-level overview (files changed, insertions/deletions)\n- Use `--name-only` for enumeration without content\n- Use `...` three-dot syntax to show changes on current branch since divergence\n\n## Semantic Delta Capture (sem)\n\nWhen sem is available (see `leyline:sem-integration`),\nenhance delta capture with entity-level diffs:\n\n```bash\n# Entity-level change summary across commits\nsem diff --format json ${BASE}...HEAD\n\n# Track a specific entity's evolution\nsem log \n```\n\n> **Note:** sem may not support three-dot (`...`) range\n> syntax directly. If `sem diff` fails with a range,\n> resolve the merge base first:\n> `BASE=$(git merge-base main HEAD)` then pass\n> `sem diff --format json $BASE HEAD`.\n\n**Key advantages over git diff --stat:**\n\n- Shows which functions/classes changed, not just files\n- Distinguishes additions from modifications from renames\n- `sem log` tracks an entity across renames\n\nWhen sem is unavailable, fall back to the git commands\nin the section above.\n\n## Git-Specific Insights Extraction\n\nTargeted inspection commands:\n\n```bash\ngit show --stat # Show specific commit changes\ngit diff ${BASE}...HEAD -- path/to/file # Examine specific file changes\ngit log -p --follow -- path/to/file # File history with patches\n```\n\n**Efficient Reading:**\n- Use `git show` for commit-level understanding\n- Use `git diff` with file paths for focused analysis\n- Avoid `git log -p` without limits (token-heavy)\n\n## Integration with Sanctum\n\n**Before running catchup analysis**, use `sanctum:git-workspace-review` to gather:\n- Repository confirmation (pwd, branch)\n- Status overview (staged vs unstaged)\n- Diff statistics\n- Diff details\n\nThen proceed with catchup-specific insight extraction and follow-up identification.\n\n**Sanctum provides the raw data; catchup extracts insights and concrete next steps.**\n\n## Common Patterns\n\n**Feature Branch Catchup:**\n```bash\nBASE=$(git merge-base main HEAD)\ngit diff --stat main...HEAD\ngit log --oneline main...HEAD\n```\n\n**Release Catchup:**\n```bash\ngit diff --stat v1.0.0...v1.1.0\ngit log --oneline --graph v1.0.0...v1.1.0\n```\n\n**Daily Standup Catchup:**\n```bash\ngit log --since=\"yesterday\" --oneline --all\ngit diff --stat HEAD@{yesterday}...HEAD\n```\n\nFile v1.0.3:modules/log-analysis-patterns.md\n\n---\nname: log-analysis-patterns\ndescription: System log and event stream analysis patterns for catchup\nparent_skill: imbue:catchup\ncategory: analysis-patterns\ntags: [logs, events, monitoring, time-series]\nestimated_tokens: 300\n---\n\n# Log Analysis Patterns\n\n## System Log Catchup\n\nWhen catching up on system behavior via logs:\n\n**Context Establishment:**\n- Identify time window: \"Last check was [timestamp]\"\n- Note log sources (application, system, service)\n- Identify environment (prod, staging, dev)\n- Baseline normal behavior\n\n**Delta Capture:**\n- Count log entries by severity (ERROR, WARN, INFO)\n- Enumerate unique error types\n- Identify anomalies or patterns\n- Note frequency changes (spike, drop, stable)\n\n**Efficient Commands:**\n```bash\n# Count by severity\ngrep -c \"ERROR\" logfile.log\ngrep -c \"WARN\" logfile.log\n\n# Unique error messages\ngrep \"ERROR\" logfile.log | cut -d: -f3 | sort | uniq -c | sort -rn | head -20\n\n# Time-based filtering\nawk '$1 >= \"2025-12-04\" && $1 <= \"2025-12-05\"' logfile.log\n```\n\n## Event Stream Analysis\n\nFor application events, audit logs, or metrics:\n\n**Context:**\n- Event source and schema\n- Baseline event rate\n- Time window of interest\n- Expected vs actual patterns\n\n**Delta:**\n- New event types introduced\n- Event rate changes (throughput)\n- Failed vs successful event ratios\n- Outliers or anomalies\n\n**Insights:**\n- Performance trends (response times, throughput)\n- Error patterns (recurring, transient, progressive)\n- User behavior changes\n- System health indicators\n\n## Time-Window Analysis\n\n**Comparing time windows:**\n```bash\n# Events today vs yesterday\ncomm -13 <(grep \"2025-12-04\" events.log | sort) \\\n <(grep \"2025-12-05\" events.log | sort)\n\n# Hourly breakdown\nawk '{print substr($1,12,2)}' logfile.log | sort | uniq -c\n```\n\n**Pattern Detection:**\n- Periodic patterns (hourly, daily, weekly cycles)\n- Correlation between events\n- Cascading failures\n- Recovery patterns\n\n## Metric-Based Catchup\n\nWhen logs include metrics or measurements:\n\n**Delta:**\n- Min/max/avg changes\n- Percentile shifts (p50, p95, p99)\n- Threshold violations\n- Trend direction (improving, degrading, stable)\n\n**Insights:**\n- Capacity planning needs\n- Performance regression sources\n- Resource utilization trends\n- SLA compliance status\n\n## Token Conservation\n\n- Use aggregation (counts, uniques) over raw logs\n- Sample representative entries, don't reproduce all\n- Reference log files + line numbers for detail\n- Summarize patterns rather than listing every entry\n- Defer deep debugging to specialized tools/skills\n\nFile v1.0.3:skill-card.md\n\n## Description:
\nSummarizes recent git changes for context recovery after session breaks.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[athola](https://clawhub.ai/user/athola)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and project contributors use this skill to quickly understand what changed across git history, meeting notes, sprint trackers, document revisions, or logs after a gap or handoff.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill may be asked to inspect private documents, meeting notes, git history, or logs that contain sensitive information.
\nMitigation: Use it only on intended, scoped inputs and avoid sensitive logs or private documents unless that review is authorized.
\nRisk: Catch-up summaries can omit important context or overstate the implications of recent changes.
\nMitigation: Review the cited source files, commits, notes, or log windows before relying on the summary for planning or handoff decisions.
\nRisk: The artifact includes example shell commands for git and log inspection.
\nMitigation: Review commands and path scopes before execution, especially in repositories or environments containing confidential data.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/athola/nm-imbue-catchup)
\n- [OpenClaw homepage](https://github.com/athola/claude-night-market/tree/master/plugins/imbue)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, shell commands, guidance]
\n**Output Format:** [Markdown summary with key changes, follow-ups, blockers, and optional shell command snippets.]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Produces concise catch-up analysis; no generated files are expected.]
\n\n## Skill Version(s):
\n1.0.3 (source: ClawHub release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.2: 6 files, 7792 bytes\n\nFiles: modules/document-analysis-patterns.md (2358b), modules/git-catchup-patterns.md (3100b), modules/log-analysis-patterns.md (2540b), skill-card.md (2220b), SKILL.md (4093b), _meta.json (135b)\n\nFile v1.0.2:SKILL.md\n\n---\nname: catchup\ndescription: |\n Summarize recent changes from git history for context recovery, handoffs, and sprint review\nversion: 1.9.5\ntriggers:\n - summarization\n - context-acquisition\n - insights\n - follow-ups\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/imbue\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.imbue:proof-of-work\"]}}}\nsource: claude-night-market\nsource_plugin: imbue\n---\n\n> **Night Market Skill** — ported from [claude-night-market/imbue](https://github.com/athola/claude-night-market/tree/master/plugins/imbue). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n## Table of Contents\n\n- [Overview](#overview)\n- [When to Use](#when-to-use)\n- [Activation](#activation)\n- [Progressive Loading](#progressive-loading)\n- [4-Step Methodology](#4-step-methodology)\n- [Output Format](#output-format)\n\n# Catchup Analysis Methodology\n\n## Overview\n\nStructured 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.\n\n## When To Use\n- Joining ongoing work or returning after absence\n- Before planning or reviewing handoffs\n- Any \"what happened and what's next\" context\n\n## When NOT To Use\n\n- Doing detailed\n diff analysis - use diff-analysis instead\n- Full code review needed\n - use review-core instead\n- Doing detailed\n diff analysis - use diff-analysis instead\n- Full code review needed\n - use review-core instead\n\n## Activation\n**Keywords**: catchup, summary, status, progress, context, handoff\n**Cues**: \"get me up to speed\", \"current status\", \"summarize progress\"\n\n## Progressive Loading\n\nLoad modules based on context:\n\n**Git**: Load `modules/git-catchup-patterns.md` for git commands. Consider `sanctum:git-workspace-review` for initial data gathering.\n\n**Documents/Notes**: Load `modules/document-analysis-patterns.md` for meeting notes, sprint tracking, document revisions.\n\n**Logs/Events**: Load `modules/log-analysis-patterns.md` for time-series and metric analysis.\n\n**Always Available**: `imbue:proof-of-work`, TodoWrite workflow, structured output.\n\n## Required TodoWrite Items\n1. `catchup:context-confirmed` - Boundaries established\n2. `catchup:delta-captured` - Changes enumerated\n3. `catchup:insights-extracted` - Themes identified\n4. `catchup:followups-recorded` - Actions captured\n\n## 4-Step Methodology\n\n### Step 1: Confirm Context\nDefine scope (git branch, sprint, meetings), baseline (last state), and current target. See modules for commands.\n\n### Step 2: Capture Delta\nEnumerate changed items with metrics. Prioritize source/config/docs over generated artifacts. See modules for strategies.\n\n### Step 3: Extract Insights\nPer item: **What** (change), **Why** (motivation), **Implications** (tests/risks/deps). Rollup into themes.\n\n### Step 4: Record Follow-ups\nCapture: Tests, Documentation, Reviews, Blockers, Questions. If none, state explicitly.\n\n## Output Format\n```\n## Summary\n[2-3 sentence theme + risk overview]\n\n## Key Changes\n- [Item]: [what/why/implication]\n\n## Follow-ups\n- [ ] [Action with owner]\n\n## Blockers/Questions\n- [Item requiring resolution]\n```\n**Verification:** Run the command with `--help` flag to verify availability.\n\n## Integration\nUse `imbue:diff-analysis` for risk assessment, `imbue:proof-of-work` for reproducibility, `sanctum:git-workspace-review` for git data. Feed to `brainstorming` or `writing-plans` as needed.\n\n## Token Conservation\nReference paths + lines (don't reproduce). Summarize outputs. Defer deep analysis. Use progressive loading.\n\n## Exit Criteria\n- Four TodoWrite items completed\n- Context/delta/insights/follow-ups captured\n- Stakeholders understand state without re-reading sources\n## Troubleshooting\n\n### Common Issues\n\n**Command not found**\nEnsure all dependencies are installed and in PATH\n\n**Permission errors**\nCheck file permissions and run with appropriate privileges\n\n**Unexpected behavior**\nEnable verbose logging with `--verbose` flag\n\nFile v1.0.2:_meta.json\n\n{\n \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n \"slug\": \"nm-imbue-catchup\",\n \"version\": \"1.0.2\",\n \"publishedAt\": 1778293032755\n}\n\nFile v1.0.2:modules/document-analysis-patterns.md\n\n---\nname: document-analysis-patterns\ndescription: Document and meeting notes analysis patterns for catchup\nparent_skill: imbue:catchup\ncategory: analysis-patterns\ntags: [documents, meetings, notes, tracking]\nestimated_tokens: 300\n---\n\n# Document Analysis Patterns\n\n## Meeting Notes Analysis\n\nWhen catching up on meeting notes or discussions:\n\n**Context Establishment:**\n- Identify date range: \"Last meeting I attended was [date]\"\n- Note participants involved\n- Identify meeting series or project name\n\n**Delta Capture:**\n- List topics discussed (agenda items)\n- Enumerate decisions made\n- Identify action items assigned\n- Note open questions or blocked items\n\n**Insight Extraction:**\n- What changed since last meeting?\n- What decisions affect ongoing work?\n- What consensus emerged on contentious topics?\n- What new information affects project direction?\n\n## Sprint/Ticket Catchup Patterns\n\nFor Jira, GitHub Issues, or similar tracking systems:\n\n**Context:**\n- Last sprint/milestone reviewed\n- Current sprint/milestone\n- Team velocity or capacity changes\n\n**Delta:**\n- Tickets completed since baseline\n- Tickets in progress\n- New tickets added to backlog\n- Priority shifts or re-ordering\n\n**Insights:**\n- Velocity trends (ahead/behind schedule?)\n- Risk indicators (blocked tickets, dependencies)\n- Scope changes (new requirements, deferred items)\n- Team capacity changes\n\n## Document Revision Tracking\n\nWhen reviewing evolving documents (specs, designs, RFCs):\n\n**Context:**\n- Last version reviewed (version number, date, or commit)\n- Current version\n- Document type and audience\n\n**Delta:**\n- Sections added, modified, or removed\n- Comments or review feedback incorporated\n- Status changes (draft → review → approved)\n\n**Insights:**\n- Requirements changes and rationale\n- Design decisions made or reversed\n- Unresolved discussions or open questions\n- Approval status and blockers\n\n## Generic Document Delta Patterns\n\n**Efficient Enumeration:**\n- Focus on substantive changes (ignore typos, formatting)\n- Identify authors/contributors to understand perspective\n- Note timestamp for context\n- Track references to external decisions or dependencies\n\n**Token Conservation:**\n- Summarize content rather than quoting verbatim\n- Reference section headings + key points\n- List decisions/actions rather than narrative\n- Use bullet points for scanning efficiency\n\nFile v1.0.2:modules/git-catchup-patterns.md\n\n---\nname: git-catchup-patterns\ndescription: Git-specific commands and patterns for catchup analysis\nparent_skill: imbue:catchup\ncategory: technical-patterns\ntags: [git, version-control, delta-capture]\nestimated_tokens: 400\n---\n\n# Git Catchup Patterns\n\n## Git Context Establishment\n\nUse these commands to establish git repository context:\n\n```bash\npwd # Show current directory\ngit status -sb | head -n 1 # Show current branch and status\ngit rev-parse --abbrev-ref --symbolic-full-name @{u} # Show the upstream branch, if one is being tracked\n```\n\nThese help answer:\n- Where am I working?\n- What branch am I on?\n- Is this branch tracking a remote?\n\n## Git Delta Capture\n\nEfficiently capture changes between states:\n\n```bash\ngit diff --stat ${BASE}...HEAD # Show summary statistics\ngit diff --name-only ${BASE}...HEAD # List changed files\ngit log --oneline ${BASE}...HEAD # Show commit history\n```\n\n**Key Patterns:**\n- Use `--stat` for high-level overview (files changed, insertions/deletions)\n- Use `--name-only` for enumeration without content\n- Use `...` three-dot syntax to show changes on current branch since divergence\n\n## Semantic Delta Capture (sem)\n\nWhen sem is available (see `leyline:sem-integration`),\nenhance delta capture with entity-level diffs:\n\n```bash\n# Entity-level change summary across commits\nsem diff --json ${BASE}...HEAD\n\n# Track a specific entity's evolution\nsem log \n```\n\n**Key advantages over git diff --stat:**\n\n- Shows which functions/classes changed, not just files\n- Distinguishes additions from modifications from renames\n- `sem log` tracks an entity across renames\n\nWhen sem is unavailable, fall back to the git commands\nin the section above.\n\n## Git-Specific Insights Extraction\n\nTargeted inspection commands:\n\n```bash\ngit show --stat # Show specific commit changes\ngit diff ${BASE}...HEAD -- path/to/file # Examine specific file changes\ngit log -p --follow -- path/to/file # File history with patches\n```\n\n**Efficient Reading:**\n- Use `git show` for commit-level understanding\n- Use `git diff` with file paths for focused analysis\n- Avoid `git log -p` without limits (token-heavy)\n\n## Integration with Sanctum\n\n**Before running catchup analysis**, use `sanctum:git-workspace-review` to gather:\n- Repository confirmation (pwd, branch)\n- Status overview (staged vs unstaged)\n- Diff statistics\n- Diff details\n\nThen proceed with catchup-specific insight extraction and follow-up identification.\n\n**Sanctum provides the raw data; catchup extracts insights and actionable items.**\n\n## Common Patterns\n\n**Feature Branch Catchup:**\n```bash\nBASE=$(git merge-base main HEAD)\ngit diff --stat main...HEAD\ngit log --oneline main...HEAD\n```\n\n**Release Catchup:**\n```bash\ngit diff --stat v1.0.0...v1.1.0\ngit log --oneline --graph v1.0.0...v1.1.0\n```\n\n**Daily Standup Catchup:**\n```bash\ngit log --since=\"yesterday\" --oneline --all\ngit diff --stat HEAD@{yesterday}...HEAD\n```\n\nFile v1.0.2:modules/log-analysis-patterns.md\n\n---\nname: log-analysis-patterns\ndescription: System log and event stream analysis patterns for catchup\nparent_skill: imbue:catchup\ncategory: analysis-patterns\ntags: [logs, events, monitoring, time-series]\nestimated_tokens: 300\n---\n\n# Log Analysis Patterns\n\n## System Log Catchup\n\nWhen catching up on system behavior via logs:\n\n**Context Establishment:**\n- Identify time window: \"Last check was [timestamp]\"\n- Note log sources (application, system, service)\n- Identify environment (prod, staging, dev)\n- Baseline normal behavior\n\n**Delta Capture:**\n- Count log entries by severity (ERROR, WARN, INFO)\n- Enumerate unique error types\n- Identify anomalies or patterns\n- Note frequency changes (spike, drop, stable)\n\n**Efficient Commands:**\n```bash\n# Count by severity\ngrep -c \"ERROR\" logfile.log\ngrep -c \"WARN\" logfile.log\n\n# Unique error messages\ngrep \"ERROR\" logfile.log | cut -d: -f3 | sort | uniq -c | sort -rn | head -20\n\n# Time-based filtering\nawk '$1 >= \"2025-12-04\" && $1 <= \"2025-12-05\"' logfile.log\n```\n\n## Event Stream Analysis\n\nFor application events, audit logs, or metrics:\n\n**Context:**\n- Event source and schema\n- Baseline event rate\n- Time window of interest\n- Expected vs actual patterns\n\n**Delta:**\n- New event types introduced\n- Event rate changes (throughput)\n- Failed vs successful event ratios\n- Outliers or anomalies\n\n**Insights:**\n- Performance trends (response times, throughput)\n- Error patterns (recurring, transient, progressive)\n- User behavior changes\n- System health indicators\n\n## Time-Window Analysis\n\n**Comparing time windows:**\n```bash\n# Events today vs yesterday\ncomm -13 <(grep \"2025-12-04\" events.log | sort) \\\n <(grep \"2025-12-05\" events.log | sort)\n\n# Hourly breakdown\nawk '{print substr($1,12,2)}' logfile.log | sort | uniq -c\n```\n\n**Pattern Detection:**\n- Periodic patterns (hourly, daily, weekly cycles)\n- Correlation between events\n- Cascading failures\n- Recovery patterns\n\n## Metric-Based Catchup\n\nWhen logs include metrics or measurements:\n\n**Delta:**\n- Min/max/avg changes\n- Percentile shifts (p50, p95, p99)\n- Threshold violations\n- Trend direction (improving, degrading, stable)\n\n**Insights:**\n- Capacity planning needs\n- Performance regression sources\n- Resource utilization trends\n- SLA compliance status\n\n## Token Conservation\n\n- Use aggregation (counts, uniques) over raw logs\n- Sample representative entries, don't reproduce all\n- Reference log files + line numbers for detail\n- Summarize patterns rather than listing every entry\n- Defer deep debugging to specialized tools/skills\n\nFile v1.0.2:skill-card.md\n\n## Description:
\nSummarize recent changes from git history for context recovery, handoffs, and sprint review.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[athola](https://clawhub.ai/user/athola)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers, engineers, and project contributors use this skill to quickly understand what changed across git history, meeting notes, sprint tracking documents, or logs, then identify implications, follow-ups, blockers, and questions.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: Broad trigger phrases such as summary, status, progress, context, and handoff could activate the skill unintentionally.
\nMitigation: Use explicit phrasing when invoking the skill and confirm the intended scope before analysis begins.
\nRisk: Catchup analysis may read repository, document, meeting-note, or log context that contains sensitive material.
\nMitigation: Avoid invoking the skill in sensitive directories or conversations unless that context is appropriate for summarization.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/athola/nm-imbue-catchup)
\n- [Publisher profile](https://clawhub.ai/user/athola)
\n- [Clawdis homepage](https://github.com/athola/claude-night-market/tree/master/plugins/imbue)
\n\n\n## Skill Output:
\n**Output Type(s):** [Analysis, Markdown, Shell commands, Guidance]
\n**Output Format:** [Markdown summary with bullets, checklists, and inline shell commands when git or log analysis is needed]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Uses progressive loading for git, document, and log analysis patterns; summarizes outputs and references paths or lines instead of reproducing large source content.]
\n\n## Skill Version(s):
\n1.0.2 (source: server release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.1: 5 files, 6594 bytes\n\nFiles: modules/document-analysis-patterns.md (2358b), modules/git-catchup-patterns.md (3100b), modules/log-analysis-patterns.md (2540b), SKILL.md (4093b), _meta.json (135b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: catchup\ndescription: |\n Summarize recent changes from git history for context recovery, handoffs, and sprint review\nversion: 1.9.4\ntriggers:\n - summarization\n - context-acquisition\n - insights\n - follow-ups\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/imbue\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.imbue:proof-of-work\"]}}}\nsource: claude-night-market\nsource_plugin: imbue\n---\n\n> **Night Market Skill** — ported from [claude-night-market/imbue](https://github.com/athola/claude-night-market/tree/master/plugins/imbue). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n## Table of Contents\n\n- [Overview](#overview)\n- [When to Use](#when-to-use)\n- [Activation](#activation)\n- [Progressive Loading](#progressive-loading)\n- [4-Step Methodology](#4-step-methodology)\n- [Output Format](#output-format)\n\n# Catchup Analysis Methodology\n\n## Overview\n\nStructured 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.\n\n## When To Use\n- Joining ongoing work or returning after absence\n- Before planning or reviewing handoffs\n- Any \"what happened and what's next\" context\n\n## When NOT To Use\n\n- Doing detailed\n diff analysis - use diff-analysis instead\n- Full code review needed\n - use review-core instead\n- Doing detailed\n diff analysis - use diff-analysis instead\n- Full code review needed\n - use review-core instead\n\n## Activation\n**Keywords**: catchup, summary, status, progress, context, handoff\n**Cues**: \"get me up to speed\", \"current status\", \"summarize progress\"\n\n## Progressive Loading\n\nLoad modules based on context:\n\n**Git**: Load `modules/git-catchup-patterns.md` for git commands. Consider `sanctum:git-workspace-review` for initial data gathering.\n\n**Documents/Notes**: Load `modules/document-analysis-patterns.md` for meeting notes, sprint tracking, document revisions.\n\n**Logs/Events**: Load `modules/log-analysis-patterns.md` for time-series and metric analysis.\n\n**Always Available**: `imbue:proof-of-work`, TodoWrite workflow, structured output.\n\n## Required TodoWrite Items\n1. `catchup:context-confirmed` - Boundaries established\n2. `catchup:delta-captured` - Changes enumerated\n3. `catchup:insights-extracted` - Themes identified\n4. `catchup:followups-recorded` - Actions captured\n\n## 4-Step Methodology\n\n### Step 1: Confirm Context\nDefine scope (git branch, sprint, meetings), baseline (last state), and current target. See modules for commands.\n\n### Step 2: Capture Delta\nEnumerate changed items with metrics. Prioritize source/config/docs over generated artifacts. See modules for strategies.\n\n### Step 3: Extract Insights\nPer item: **What** (change), **Why** (motivation), **Implications** (tests/risks/deps). Rollup into themes.\n\n### Step 4: Record Follow-ups\nCapture: Tests, Documentation, Reviews, Blockers, Questions. If none, state explicitly.\n\n## Output Format\n```\n## Summary\n[2-3 sentence theme + risk overview]\n\n## Key Changes\n- [Item]: [what/why/implication]\n\n## Follow-ups\n- [ ] [Action with owner]\n\n## Blockers/Questions\n- [Item requiring resolution]\n```\n**Verification:** Run the command with `--help` flag to verify availability.\n\n## Integration\nUse `imbue:diff-analysis` for risk assessment, `imbue:proof-of-work` for reproducibility, `sanctum:git-workspace-review` for git data. Feed to `brainstorming` or `writing-plans` as needed.\n\n## Token Conservation\nReference paths + lines (don't reproduce). Summarize outputs. Defer deep analysis. Use progressive loading.\n\n## Exit Criteria\n- Four TodoWrite items completed\n- Context/delta/insights/follow-ups captured\n- Stakeholders understand state without re-reading sources\n## Troubleshooting\n\n### Common Issues\n\n**Command not found**\nEnsure all dependencies are installed and in PATH\n\n**Permission errors**\nCheck file permissions and run with appropriate privileges\n\n**Unexpected behavior**\nEnable verbose logging with `--verbose` flag\n\nFile v1.0.1:_meta.json\n\n{\n \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n \"slug\": \"nm-imbue-catchup\",\n \"version\": \"1.0.1\",\n \"publishedAt\": 1778077071495\n}\n\nFile v1.0.1:modules/document-analysis-patterns.md\n\n---\nname: document-analysis-patterns\ndescription: Document and meeting notes analysis patterns for catchup\nparent_skill: imbue:catchup\ncategory: analysis-patterns\ntags: [documents, meetings, notes, tracking]\nestimated_tokens: 300\n---\n\n# Document Analysis Patterns\n\n## Meeting Notes Analysis\n\nWhen catching up on meeting notes or discussions:\n\n**Context Establishment:**\n- Identify date range: \"Last meeting I attended was [date]\"\n- Note participants involved\n- Identify meeting series or project name\n\n**Delta Capture:**\n- List topics discussed (agenda items)\n- Enumerate decisions made\n- Identify action items assigned\n- Note open questions or blocked items\n\n**Insight Extraction:**\n- What changed since last meeting?\n- What decisions affect ongoing work?\n- What consensus emerged on contentious topics?\n- What new information affects project direction?\n\n## Sprint/Ticket Catchup Patterns\n\nFor Jira, GitHub Issues, or similar tracking systems:\n\n**Context:**\n- Last sprint/milestone reviewed\n- Current sprint/milestone\n- Team velocity or capacity changes\n\n**Delta:**\n- Tickets completed since baseline\n- Tickets in progress\n- New tickets added to backlog\n- Priority shifts or re-ordering\n\n**Insights:**\n- Velocity trends (ahead/behind schedule?)\n- Risk indicators (blocked tickets, dependencies)\n- Scope changes (new requirements, deferred items)\n- Team capacity changes\n\n## Document Revision Tracking\n\nWhen reviewing evolving documents (specs, designs, RFCs):\n\n**Context:**\n- Last version reviewed (version number, date, or commit)\n- Current version\n- Document type and audience\n\n**Delta:**\n- Sections added, modified, or removed\n- Comments or review feedback incorporated\n- Status changes (draft → review → approved)\n\n**Insights:**\n- Requirements changes and rationale\n- Design decisions made or reversed\n- Unresolved discussions or open questions\n- Approval status and blockers\n\n## Generic Document Delta Patterns\n\n**Efficient Enumeration:**\n- Focus on substantive changes (ignore typos, formatting)\n- Identify authors/contributors to understand perspective\n- Note timestamp for context\n- Track references to external decisions or dependencies\n\n**Token Conservation:**\n- Summarize content rather than quoting verbatim\n- Reference section headings + key points\n- List decisions/actions rather than narrative\n- Use bullet points for scanning efficiency\n\nFile v1.0.1:modules/git-catchup-patterns.md\n\n---\nname: git-catchup-patterns\ndescription: Git-specific commands and patterns for catchup analysis\nparent_skill: imbue:catchup\ncategory: technical-patterns\ntags: [git, version-control, delta-capture]\nestimated_tokens: 400\n---\n\n# Git Catchup Patterns\n\n## Git Context Establishment\n\nUse these commands to establish git repository context:\n\n```bash\npwd # Show current directory\ngit status -sb | head -n 1 # Show current branch and status\ngit rev-parse --abbrev-ref --symbolic-full-name @{u} # Show the upstream branch, if one is being tracked\n```\n\nThese help answer:\n- Where am I working?\n- What branch am I on?\n- Is this branch tracking a remote?\n\n## Git Delta Capture\n\nEfficiently capture changes between states:\n\n```bash\ngit diff --stat ${BASE}...HEAD # Show summary statistics\ngit diff --name-only ${BASE}...HEAD # List changed files\ngit log --oneline ${BASE}...HEAD # Show commit history\n```\n\n**Key Patterns:**\n- Use `--stat` for high-level overview (files changed, insertions/deletions)\n- Use `--name-only` for enumeration without content\n- Use `...` three-dot syntax to show changes on current branch since divergence\n\n## Semantic Delta Capture (sem)\n\nWhen sem is available (see `leyline:sem-integration`),\nenhance delta capture with entity-level diffs:\n\n```bash\n# Entity-level change summary across commits\nsem diff --json ${BASE}...HEAD\n\n# Track a specific entity's evolution\nsem log \n```\n\n**Key advantages over git diff --stat:**\n\n- Shows which functions/classes changed, not just files\n- Distinguishes additions from modifications from renames\n- `sem log` tracks an entity across renames\n\nWhen sem is unavailable, fall back to the git commands\nin the section above.\n\n## Git-Specific Insights Extraction\n\nTargeted inspection commands:\n\n```bash\ngit show --stat # Show specific commit changes\ngit diff ${BASE}...HEAD -- path/to/file # Examine specific file changes\ngit log -p --follow -- path/to/file # File history with patches\n```\n\n**Efficient Reading:**\n- Use `git show` for commit-level understanding\n- Use `git diff` with file paths for focused analysis\n- Avoid `git log -p` without limits (token-heavy)\n\n## Integration with Sanctum\n\n**Before running catchup analysis**, use `sanctum:git-workspace-review` to gather:\n- Repository confirmation (pwd, branch)\n- Status overview (staged vs unstaged)\n- Diff statistics\n- Diff details\n\nThen proceed with catchup-specific insight extraction and follow-up identification.\n\n**Sanctum provides the raw data; catchup extracts insights and actionable items.**\n\n## Common Patterns\n\n**Feature Branch Catchup:**\n```bash\nBASE=$(git merge-base main HEAD)\ngit diff --stat main...HEAD\ngit log --oneline main...HEAD\n```\n\n**Release Catchup:**\n```bash\ngit diff --stat v1.0.0...v1.1.0\ngit log --oneline --graph v1.0.0...v1.1.0\n```\n\n**Daily Standup Catchup:**\n```bash\ngit log --since=\"yesterday\" --oneline --all\ngit diff --stat HEAD@{yesterday}...HEAD\n```\n\nFile v1.0.1:modules/log-analysis-patterns.md\n\n---\nname: log-analysis-patterns\ndescription: System log and event stream analysis patterns for catchup\nparent_skill: imbue:catchup\ncategory: analysis-patterns\ntags: [logs, events, monitoring, time-series]\nestimated_tokens: 300\n---\n\n# Log Analysis Patterns\n\n## System Log Catchup\n\nWhen catching up on system behavior via logs:\n\n**Context Establishment:**\n- Identify time window: \"Last check was [timestamp]\"\n- Note log sources (application, system, service)\n- Identify environment (prod, staging, dev)\n- Baseline normal behavior\n\n**Delta Capture:**\n- Count log entries by severity (ERROR, WARN, INFO)\n- Enumerate unique error types\n- Identify anomalies or patterns\n- Note frequency changes (spike, drop, stable)\n\n**Efficient Commands:**\n```bash\n# Count by severity\ngrep -c \"ERROR\" logfile.log\ngrep -c \"WARN\" logfile.log\n\n# Unique error messages\ngrep \"ERROR\" logfile.log | cut -d: -f3 | sort | uniq -c | sort -rn | head -20\n\n# Time-based filtering\nawk '$1 >= \"2025-12-04\" && $1 <= \"2025-12-05\"' logfile.log\n```\n\n## Event Stream Analysis\n\nFor application events, audit logs, or metrics:\n\n**Context:**\n- Event source and schema\n- Baseline event rate\n- Time window of interest\n- Expected vs actual patterns\n\n**Delta:**\n- New event types introduced\n- Event rate changes (throughput)\n- Failed vs successful event ratios\n- Outliers or anomalies\n\n**Insights:**\n- Performance trends (response times, throughput)\n- Error patterns (recurring, transient, progressive)\n- User behavior changes\n- System health indicators\n\n## Time-Window Analysis\n\n**Comparing time windows:**\n```bash\n# Events today vs yesterday\ncomm -13 <(grep \"2025-12-04\" events.log | sort) \\\n <(grep \"2025-12-05\" events.log | sort)\n\n# Hourly breakdown\nawk '{print substr($1,12,2)}' logfile.log | sort | uniq -c\n```\n\n**Pattern Detection:**\n- Periodic patterns (hourly, daily, weekly cycles)\n- Correlation between events\n- Cascading failures\n- Recovery patterns\n\n## Metric-Based Catchup\n\nWhen logs include metrics or measurements:\n\n**Delta:**\n- Min/max/avg changes\n- Percentile shifts (p50, p95, p99)\n- Threshold violations\n- Trend direction (improving, degrading, stable)\n\n**Insights:**\n- Capacity planning needs\n- Performance regression sources\n- Resource utilization trends\n- SLA compliance status\n\n## Token Conservation\n\n- Use aggregation (counts, uniques) over raw logs\n- Sample representative entries, don't reproduce all\n- Reference log files + line numbers for detail\n- Summarize patterns rather than listing every entry\n- Defer deep debugging to specialized tools/skills\n\nArchive v1.0.0: 5 files, 6592 bytes\n\nFiles: modules/document-analysis-patterns.md (2358b), modules/git-catchup-patterns.md (3100b), modules/log-analysis-patterns.md (2540b), SKILL.md (4093b), _meta.json (135b)\n\nFile v1.0.0:SKILL.md\n\n---\nname: catchup\ndescription: |\n Summarize recent changes from git history for context recovery, handoffs, and sprint review\nversion: 1.8.2\ntriggers:\n - summarization\n - context-acquisition\n - insights\n - follow-ups\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/imbue\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.imbue:proof-of-work\"]}}}\nsource: claude-night-market\nsource_plugin: imbue\n---\n\n> **Night Market Skill** — ported from [claude-night-market/imbue](https://github.com/athola/claude-night-market/tree/master/plugins/imbue). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n## Table of Contents\n\n- [Overview](#overview)\n- [When to Use](#when-to-use)\n- [Activation](#activation)\n- [Progressive Loading](#progressive-loading)\n- [4-Step Methodology](#4-step-methodology)\n- [Output Format](#output-format)\n\n# Catchup Analysis Methodology\n\n## Overview\n\nStructured 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.\n\n## When To Use\n- Joining ongoing work or returning after absence\n- Before planning or reviewing handoffs\n- Any \"what happened and what's next\" context\n\n## When NOT To Use\n\n- Doing detailed\n diff analysis - use diff-analysis instead\n- Full code review needed\n - use review-core instead\n- Doing detailed\n diff analysis - use diff-analysis instead\n- Full code review needed\n - use review-core instead\n\n## Activation\n**Keywords**: catchup, summary, status, progress, context, handoff\n**Cues**: \"get me up to speed\", \"current status\", \"summarize progress\"\n\n## Progressive Loading\n\nLoad modules based on context:\n\n**Git**: Load `modules/git-catchup-patterns.md` for git commands. Consider `sanctum:git-workspace-review` for initial data gathering.\n\n**Documents/Notes**: Load `modules/document-analysis-patterns.md` for meeting notes, sprint tracking, document revisions.\n\n**Logs/Events**: Load `modules/log-analysis-patterns.md` for time-series and metric analysis.\n\n**Always Available**: `imbue:proof-of-work`, TodoWrite workflow, structured output.\n\n## Required TodoWrite Items\n1. `catchup:context-confirmed` - Boundaries established\n2. `catchup:delta-captured` - Changes enumerated\n3. `catchup:insights-extracted` - Themes identified\n4. `catchup:followups-recorded` - Actions captured\n\n## 4-Step Methodology\n\n### Step 1: Confirm Context\nDefine scope (git branch, sprint, meetings), baseline (last state), and current target. See modules for commands.\n\n### Step 2: Capture Delta\nEnumerate changed items with metrics. Prioritize source/config/docs over generated artifacts. See modules for strategies.\n\n### Step 3: Extract Insights\nPer item: **What** (change), **Why** (motivation), **Implications** (tests/risks/deps). Rollup into themes.\n\n### Step 4: Record Follow-ups\nCapture: Tests, Documentation, Reviews, Blockers, Questions. If none, state explicitly.\n\n## Output Format\n```\n## Summary\n[2-3 sentence theme + risk overview]\n\n## Key Changes\n- [Item]: [what/why/implication]\n\n## Follow-ups\n- [ ] [Action with owner]\n\n## Blockers/Questions\n- [Item requiring resolution]\n```\n**Verification:** Run the command with `--help` flag to verify availability.\n\n## Integration\nUse `imbue:diff-analysis` for risk assessment, `imbue:proof-of-work` for reproducibility, `sanctum:git-workspace-review` for git data. Feed to `brainstorming` or `writing-plans` as needed.\n\n## Token Conservation\nReference paths + lines (don't reproduce). Summarize outputs. Defer deep analysis. Use progressive loading.\n\n## Exit Criteria\n- Four TodoWrite items completed\n- Context/delta/insights/follow-ups captured\n- Stakeholders understand state without re-reading sources\n## Troubleshooting\n\n### Common Issues\n\n**Command not found**\nEnsure all dependencies are installed and in PATH\n\n**Permission errors**\nCheck file permissions and run with appropriate privileges\n\n**Unexpected behavior**\nEnable verbose logging with `--verbose` flag\n\nFile v1.0.0:_meta.json\n\n{\n \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n \"slug\": \"nm-imbue-catchup\",\n \"version\": \"1.0.0\",\n \"publishedAt\": 1775991707635\n}\n\nFile v1.0.0:modules/document-analysis-patterns.md\n\n---\nname: document-analysis-patterns\ndescription: Document and meeting notes analysis patterns for catchup\nparent_skill: imbue:catchup\ncategory: analysis-patterns\ntags: [documents, meetings, notes, tracking]\nestimated_tokens: 300\n---\n\n# Document Analysis Patterns\n\n## Meeting Notes Analysis\n\nWhen catching up on meeting notes or discussions:\n\n**Context Establishment:**\n- Identify date range: \"Last meeting I attended was [date]\"\n- Note participants involved\n- Identify meeting series or project name\n\n**Delta Capture:**\n- List topics discussed (agenda items)\n- Enumerate decisions made\n- Identify action items assigned\n- Note open questions or blocked items\n\n**Insight Extraction:**\n- What changed since last meeting?\n- What decisions affect ongoing work?\n- What consensus emerged on contentious topics?\n- What new information affects project direction?\n\n## Sprint/Ticket Catchup Patterns\n\nFor Jira, GitHub Issues, or similar tracking systems:\n\n**Context:**\n- Last sprint/milestone reviewed\n- Current sprint/milestone\n- Team velocity or capacity changes\n\n**Delta:**\n- Tickets completed since baseline\n- Tickets in progress\n- New tickets added to backlog\n- Priority shifts or re-ordering\n\n**Insights:**\n- Velocity trends (ahead/behind schedule?)\n- Risk indicators (blocked tickets, dependencies)\n- Scope changes (new requirements, deferred items)\n- Team capacity changes\n\n## Document Revision Tracking\n\nWhen reviewing evolving documents (specs, designs, RFCs):\n\n**Context:**\n- Last version reviewed (version number, date, or commit)\n- Current version\n- Document type and audience\n\n**Delta:**\n- Sections added, modified, or removed\n- Comments or review feedback incorporated\n- Status changes (draft → review → approved)\n\n**Insights:**\n- Requirements changes and rationale\n- Design decisions made or reversed\n- Unresolved discussions or open questions\n- Approval status and blockers\n\n## Generic Document Delta Patterns\n\n**Efficient Enumeration:**\n- Focus on substantive changes (ignore typos, formatting)\n- Identify authors/contributors to understand perspective\n- Note timestamp for context\n- Track references to external decisions or dependencies\n\n**Token Conservation:**\n- Summarize content rather than quoting verbatim\n- Reference section headings + key points\n- List decisions/actions rather than narrative\n- Use bullet points for scanning efficiency\n\nFile v1.0.0:modules/git-catchup-patterns.md\n\n---\nname: git-catchup-patterns\ndescription: Git-specific commands and patterns for catchup analysis\nparent_skill: imbue:catchup\ncategory: technical-patterns\ntags: [git, version-control, delta-capture]\nestimated_tokens: 400\n---\n\n# Git Catchup Patterns\n\n## Git Context Establishment\n\nUse these commands to establish git repository context:\n\n```bash\npwd # Show current directory\ngit status -sb | head -n 1 # Show current branch and status\ngit rev-parse --abbrev-ref --symbolic-full-name @{u} # Show the upstream branch, if one is being tracked\n```\n\nThese help answer:\n- Where am I working?\n- What branch am I on?\n- Is this branch tracking a remote?\n\n## Git Delta Capture\n\nEfficiently capture changes between states:\n\n```bash\ngit diff --stat ${BASE}...HEAD # Show summary statistics\ngit diff --name-only ${BASE}...HEAD # List changed files\ngit log --oneline ${BASE}...HEAD # Show commit history\n```\n\n**Key Patterns:**\n- Use `--stat` for high-level overview (files changed, insertions/deletions)\n- Use `--name-only` for enumeration without content\n- Use `...` three-dot syntax to show changes on current branch since divergence\n\n## Semantic Delta Capture (sem)\n\nWhen sem is available (see `leyline:sem-integration`),\nenhance delta capture with entity-level diffs:\n\n```bash\n# Entity-level change summary across commits\nsem diff --json ${BASE}...HEAD\n\n# Track a specific entity's evolution\nsem log \n```\n\n**Key advantages over git diff --stat:**\n\n- Shows which functions/classes changed, not just files\n- Distinguishes additions from modifications from renames\n- `sem log` tracks an entity across renames\n\nWhen sem is unavailable, fall back to the git commands\nin the section above.\n\n## Git-Specific Insights Extraction\n\nTargeted inspection commands:\n\n```bash\ngit show --stat # Show specific commit changes\ngit diff ${BASE}...HEAD -- path/to/file # Examine specific file changes\ngit log -p --follow -- path/to/file # File history with patches\n```\n\n**Efficient Reading:**\n- Use `git show` for commit-level understanding\n- Use `git diff` with file paths for focused analysis\n- Avoid `git log -p` without limits (token-heavy)\n\n## Integration with Sanctum\n\n**Before running catchup analysis**, use `sanctum:git-workspace-review` to gather:\n- Repository confirmation (pwd, branch)\n- Status overview (staged vs unstaged)\n- Diff statistics\n- Diff details\n\nThen proceed with catchup-specific insight extraction and follow-up identification.\n\n**Sanctum provides the raw data; catchup extracts insights and actionable items.**\n\n## Common Patterns\n\n**Feature Branch Catchup:**\n```bash\nBASE=$(git merge-base main HEAD)\ngit diff --stat main...HEAD\ngit log --oneline main...HEAD\n```\n\n**Release Catchup:**\n```bash\ngit diff --stat v1.0.0...v1.1.0\ngit log --oneline --graph v1.0.0...v1.1.0\n```\n\n**Daily Standup Catchup:**\n```bash\ngit log --since=\"yesterday\" --oneline --all\ngit diff --stat HEAD@{yesterday}...HEAD\n```\n\nFile v1.0.0:modules/log-analysis-patterns.md\n\n---\nname: log-analysis-patterns\ndescription: System log and event stream analysis patterns for catchup\nparent_skill: imbue:catchup\ncategory: analysis-patterns\ntags: [logs, events, monitoring, time-series]\nestimated_tokens: 300\n---\n\n# Log Analysis Patterns\n\n## System Log Catchup\n\nWhen catching up on system behavior via logs:\n\n**Context Establishment:**\n- Identify time window: \"Last check was [timestamp]\"\n- Note log sources (application, system, service)\n- Identify environment (prod, staging, dev)\n- Baseline normal behavior\n\n**Delta Capture:**\n- Count log entries by severity (ERROR, WARN, INFO)\n- Enumerate unique error types\n- Identify anomalies or patterns\n- Note frequency changes (spike, drop, stable)\n\n**Efficient Commands:**\n```bash\n# Count by severity\ngrep -c \"ERROR\" logfile.log\ngrep -c \"WARN\" logfile.log\n\n# Unique error messages\ngrep \"ERROR\" logfile.log | cut -d: -f3 | sort | uniq -c | sort -rn | head -20\n\n# Time-based filtering\nawk '$1 >= \"2025-12-04\" && $1 <= \"2025-12-05\"' logfile.log\n```\n\n## Event Stream Analysis\n\nFor application events, audit logs, or metrics:\n\n**Context:**\n- Event source and schema\n- Baseline event rate\n- Time window of interest\n- Expected vs actual patterns\n\n**Delta:**\n- New event types introduced\n- Event rate changes (throughput)\n- Failed vs successful event ratios\n- Outliers or anomalies\n\n**Insights:**\n- Performance trends (response times, throughput)\n- Error patterns (recurring, transient, progressive)\n- User behavior changes\n- System health indicators\n\n## Time-Window Analysis\n\n**Comparing time windows:**\n```bash\n# Events today vs yesterday\ncomm -13 <(grep \"2025-12-04\" events.log | sort) \\\n <(grep \"2025-12-05\" events.log | sort)\n\n# Hourly breakdown\nawk '{print substr($1,12,2)}' logfile.log | sort | uniq -c\n```\n\n**Pattern Detection:**\n- Periodic patterns (hourly, daily, weekly cycles)\n- Correlation between events\n- Cascading failures\n- Recovery patterns\n\n## Metric-Based Catchup\n\nWhen logs include metrics or measurements:\n\n**Delta:**\n- Min/max/avg changes\n- Percentile shifts (p50, p95, p99)\n- Threshold violations\n- Trend direction (improving, degrading, stable)\n\n**Insights:**\n- Capacity planning needs\n- Performance regression sources\n- Resource utilization trends\n- SLA compliance status\n\n## Token Conservation\n\n- Use aggregation (counts, uniques) over raw logs\n- Sample representative entries, don't reproduce all\n- Reference log files + line numbers for detail\n- Summarize patterns rather than listing every entry\n- Defer deep debugging to specialized tools/skills","readmeExcerpt":"Skill: catchup Owner: athola Summary: Summarizes recent git changes for context recovery after session breaks Tags: latest:1.9.19 Version history: v1.9.19 | 2026-08-26T13:12:11.370Z | user Release v1.9.19 v1.9.17 | 2026-07-30T05:33:56.974Z | user Release v1.9.17 v1.9.16 | 2026-07-14T19:50:40.418Z | user Release v1.9.16 v1.9.14 | 2026-06-30T17:59:48.795Z | user Release v1.9.14 v1.9.13 | 2026-06-27T16:18:35.730Z | user","codeSnippets":[],"executableExamples":[{"language":"text","snippet":"## Summary\n[2-3 sentence theme + risk overview]\n\n## Key Changes\n- [Item]: [what/why/implication]\n\n## Follow-ups\n- [ ] [Action with owner]\n\n## Blockers/Questions\n- [Item requiring resolution]"},{"language":"bash","snippet":"pwd # Show current directory\ngit status -sb | head -n 1 # Show current branch and status\ngit rev-parse --abbrev-ref --symbolic-full-name @{u} # Show the upstream branch, if one is being tracked"},{"language":"bash","snippet":"git diff --stat ${BASE}...HEAD # Show summary statistics\ngit diff --name-only ${BASE}...HEAD # List changed files\ngit log --oneline ${BASE}...HEAD # Show commit history"},{"language":"bash","snippet":"# Entity-level change summary across commits\nsem diff --format json ${BASE}...HEAD\n\n# Track a specific entity's evolution\nsem log "},{"language":"bash","snippet":"git show --stat # Show specific commit changes\ngit diff ${BASE}...HEAD -- path/to/file # Examine specific file changes\ngit log -p --follow -- path/to/file # File history with patches"},{"language":"bash","snippet":"BASE=$(git merge-base main HEAD)\ngit diff --stat main...HEAD\ngit log --oneline main...HEAD"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: catchup\ndescription: Summarizes recent git changes for context recovery after session breaks\nversion: 1.9.8\ntriggers:\n - summarization\n - context-acquisition\n - insights\n - follow-ups\n - resuming work after a gap or handing off to another session\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/imbue\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.imbue:proof-of-work\"]}}}\nsource: claude-night-market\nsource_plugin: imbue\n---\n\n> **Night Market Skill** — ported from [claude-night-market/imbue](https://github.com/athola/claude-night-market/tree/master/plugins/imbue). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n## Table of Contents\n\n- [Overview](#overview)\n- [When to Use](#when-to-use)\n- [Activation](#activation)\n- [Progressive Loading](#progressive-loading)\n- [4-Step Methodology](#4-step-methodology)\n- [Output Format](#output-format)\n\n# Catchup Analysis Methodology\n\n## Overview\n\nStructured 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.\n\n## When To Use\n- Joining ongoing work or returning after absence\n- Before planning or reviewing handoffs\n- Any \"what happened and what's next\" context\n\n## When NOT To Use\n\n- Doing detailed\n diff analysis - use diff-analysis instead\n- Full code review needed\n - use review-core instead\n\n## Activation\n**Keywords**: catchup, summary, status, progress, context, handoff\n**Cues**: \"get me up to speed\", \"current status\", \"summarize progress\"\n\n## Progressive Loading\n\nLoad modules based on context:\n\n**Git**: Load `modules/git-catchup-patterns.md` for git commands. Consider `sanctum:git-workspace-review` for initial data gathering.\n\n**Documents/Notes**: Load `modules/document-analysis-patterns.md` for meeting notes, sprint tracking, document revisions.\n\n**Logs/Events**: Load `modules/log-analysis-patterns.md` for time-series and metric analysis.\n\n**Always Available**: `imbue:proof-of-work`, TodoWrite workflow, structured output.\n\n## Required TodoWrite Items\n1. `catchup:context-confirmed` - Boundaries established\n2. `catchup:delta-captured` - Changes enumerated\n3. `catchup:insights-extracted` - Themes identified\n4. `catchup:followups-recorded` - Actions captured\n\n## 4-Step Methodology\n\n### Step 1: Confirm Context\nDefine scope (git branch, sprint, meetings), baseline (last state), and current target. See modules for commands.\n\n### Step 2: Capture Delta\nEnumerate changed items with metrics. Prioritize source/config/docs over generated artifacts. See modules for strategies.\n\n### Step 3: Extract Insights\nPer item: **What** (change), **Why** (motivation), **Implications** (tests/risks/deps). Rollup into themes.\n\n### Step 4: Record Follow-ups\nCapture: Tests, Documentation, Reviews, Blockers, Questions. If none, state explicitly.\n\n## Output Format\n```\n## Summary"},{"path":"_meta.json","content":"{\n \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n \"slug\": \"nm-imbue-catchup\",\n \"version\": \"1.9.19\",\n \"publishedAt\": 1787749931370\n}"},{"path":"modules/document-analysis-patterns.md","content":"---\nname: document-analysis-patterns\ndescription: Document and meeting notes analysis patterns for catchup\nparent_skill: imbue:catchup\ncategory: analysis-patterns\ntags: [documents, meetings, notes, tracking]\nestimated_tokens: 300\n---\n\n# Document Analysis Patterns\n\n## Meeting Notes Analysis\n\nWhen catching up on meeting notes or discussions:\n\n**Context Establishment:**\n- Identify date range: \"Last meeting I attended was [date]\"\n- Note participants involved\n- Identify meeting series or project name\n\n**Delta Capture:**\n- List topics discussed (agenda items)\n- Enumerate decisions made\n- Identify action items assigned\n- Note open questions or blocked items\n\n**Insight Extraction:**\n- What changed since last meeting?\n- What decisions affect ongoing work?\n- What consensus emerged on contentious topics?\n- What new information affects project direction?\n\n## Sprint/Ticket Catchup Patterns\n\nFor Jira, GitHub Issues, or similar tracking systems:\n\n**Context:**\n- Last sprint/milestone reviewed\n- Current sprint/milestone\n- Team velocity or capacity changes\n\n**Delta:**\n- Tickets completed since baseline\n- Tickets in progress\n- New tickets added to backlog\n- Priority shifts or re-ordering\n\n**Insights:**\n- Velocity trends (ahead/behind schedule?)\n- Risk indicators (blocked tickets, dependencies)\n- Scope changes (new requirements, deferred items)\n- Team capacity changes\n\n## Document Revision Tracking\n\nWhen reviewing evolving documents (specs, designs, RFCs):\n\n**Context:**\n- Last version reviewed (version number, date, or commit)\n- Current version\n- Document type and audience\n\n**Delta:**\n- Sections added, modified, or removed\n- Comments or review feedback incorporated\n- Status changes (draft → review → approved)\n\n**Insights:**\n- Requirements changes and rationale\n- Design decisions made or reversed\n- Unresolved discussions or open questions\n- Approval status and blockers\n\n## Generic Document Delta Patterns\n\n**Efficient Enumeration:**\n- Focus on substantive changes (ignore typos, formatting)\n- Identify authors/contributors to understand perspective\n- Note timestamp for context\n- Track references to external decisions or dependencies\n\n**Token Conservation:**\n- Summarize content rather than quoting verbatim\n- Reference section headings + key points\n- List decisions/actions rather than narrative\n- Use bullet points for scanning efficiency"},{"path":"modules/git-catchup-patterns.md","content":"---\nname: git-catchup-patterns\ndescription: Git-specific commands and patterns for catchup analysis\nparent_skill: imbue:catchup\ncategory: technical-patterns\ntags: [git, version-control, delta-capture]\nestimated_tokens: 400\n---\n\n# Git Catchup Patterns\n\n## Git Context Establishment\n\nUse these commands to establish git repository context:\n\n```bash\npwd # Show current directory\ngit status -sb | head -n 1 # Show current branch and status\ngit rev-parse --abbrev-ref --symbolic-full-name @{u} # Show the upstream branch, if one is being tracked\n```\n\nThese help answer:\n- Where am I working?\n- What branch am I on?\n- Is this branch tracking a remote?\n\n## Git Delta Capture\n\nEfficiently capture changes between states:\n\n```bash\ngit diff --stat ${BASE}...HEAD # Show summary statistics\ngit diff --name-only ${BASE}...HEAD # List changed files\ngit log --oneline ${BASE}...HEAD # Show commit history\n```\n\n**Key Patterns:**\n- Use `--stat` for high-level overview (files changed, insertions/deletions)\n- Use `--name-only` for enumeration without content\n- Use `...` three-dot syntax to show changes on current branch since divergence\n\n## Semantic Delta Capture (sem)\n\nWhen sem is available (see `leyline:sem-integration`),\nenhance delta capture with entity-level diffs:\n\n```bash\n# Entity-level change summary across commits\nsem diff --format json ${BASE}...HEAD\n\n# Track a specific entity's evolution\nsem log \n```\n\n> **Note:** sem may not support three-dot (`...`) range\n> syntax directly. If `sem diff` fails with a range,\n> resolve the merge base first:\n> `BASE=$(git merge-base main HEAD)` then pass\n> `sem diff --format json $BASE HEAD`.\n\n**Key advantages over git diff --stat:**\n\n- Shows which functions/classes changed, not just files\n- Distinguishes additions from modifications from renames\n- `sem log` tracks an entity across renames\n\nWhen sem is unavailable, fall back to the git commands\nin the section above.\n\n## Git-Specific Insights Extraction\n\nTargeted inspection commands:\n\n```bash\ngit show --stat # Show specific commit changes\ngit diff ${BASE}...HEAD -- path/to/file # Examine specific file changes\ngit log -p --follow -- path/to/file # File history with patches\n```\n\n**Efficient Reading:**\n- Use `git show` for commit-level understanding\n- Use `git diff` with file paths for focused analysis\n- Avoid `git log -p` without limits (token-heavy)\n\n## Integration with Sanctum\n\n**Before running catchup analysis**, use `sanctum:git-workspace-review` to gather:\n- Repository confirmation (pwd, branch)\n- Status overview (staged vs unstaged)\n- Diff statistics\n- Diff details\n\nThen proceed with catchup-specific insight extraction and follow-up identification.\n\n**Sanctum provides the raw data; catchup extracts insights and concrete next steps.**\n\n## Common Patterns\n\n**Feature Branch Catchup:"},{"path":"modules/log-analysis-patterns.md","content":"---\nname: log-analysis-patterns\ndescription: System log and event stream analysis patterns for catchup\nparent_skill: imbue:catchup\ncategory: analysis-patterns\ntags: [logs, events, monitoring, time-series]\nestimated_tokens: 300\n---\n\n# Log Analysis Patterns\n\n## System Log Catchup\n\nWhen catching up on system behavior via logs:\n\n**Context Establishment:**\n- Identify time window: \"Last check was [timestamp]\"\n- Note log sources (application, system, service)\n- Identify environment (prod, staging, dev)\n- Baseline normal behavior\n\n**Delta Capture:**\n- Count log entries by severity (ERROR, WARN, INFO)\n- Enumerate unique error types\n- Identify anomalies or patterns\n- Note frequency changes (spike, drop, stable)\n\n**Efficient Commands:**\n```bash\n# Count by severity\ngrep -c \"ERROR\" logfile.log\ngrep -c \"WARN\" logfile.log\n\n# Unique error messages\ngrep \"ERROR\" logfile.log | cut -d: -f3 | sort | uniq -c | sort -rn | head -20\n\n# Time-based filtering\nawk '$1 >= \"2025-12-04\" && $1 <= \"2025-12-05\"' logfile.log\n```\n\n## Event Stream Analysis\n\nFor application events, audit logs, or metrics:\n\n**Context:**\n- Event source and schema\n- Baseline event rate\n- Time window of interest\n- Expected vs actual patterns\n\n**Delta:**\n- New event types introduced\n- Event rate changes (throughput)\n- Failed vs successful event ratios\n- Outliers or anomalies\n\n**Insights:**\n- Performance trends (response times, throughput)\n- Error patterns (recurring, transient, progressive)\n- User behavior changes\n- System health indicators\n\n## Time-Window Analysis\n\n**Comparing time windows:**\n```bash\n# Events today vs yesterday\ncomm -13 <(grep \"2025-12-04\" events.log | sort) \\\n <(grep \"2025-12-05\" events.log | sort)\n\n# Hourly breakdown\nawk '{print substr($1,12,2)}' logfile.log | sort | uniq -c\n```\n\n**Pattern Detection:**\n- Periodic patterns (hourly, daily, weekly cycles)\n- Correlation between events\n- Cascading failures\n- Recovery patterns\n\n## Metric-Based Catchup\n\nWhen logs include metrics or measurements:\n\n**Delta:**\n- Min/max/avg changes\n- Percentile shifts (p50, p95, p99)\n- Threshold violations\n- Trend direction (improving, degrading, stable)\n\n**Insights:**\n- Capacity planning needs\n- Performance regression sources\n- Resource utilization trends\n- SLA compliance status\n\n## Token Conservation\n\n- Use aggregation (counts, uniques) over raw logs\n- Sample representative entries, don't reproduce all\n- Reference log files + line numbers for detail\n- Summarize patterns rather than listing every entry\n- Defer deep debugging to specialized tools/skills"}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"Summarizes recent git changes for context recovery after session breaks Skill: catchup Owner: athola Summary: Summarizes recent git changes for context recovery after session breaks Tags: latest:1.9.19 Version history: v1.9.19 | 2026-08-26T13:12:11.370Z | user Release v1.9.19 v1.9.17 | 2026-07-30T05:33:56.974Z | user Release v1.9.17 v1.9.16 | 2026-07-14T19:50:40.418Z | user Release v1.9.16 v1.9.14 | 2026-06-30T17:59:48.795Z | user Release v1.9.14 v1.9.13 | 2026-06-27T16:18:35.730Z | user","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":1035,"uniquenessScore":59,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-10T05:43:22.487Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-10T05:43:22.487Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-10T06:44:20.885Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}