Nm Imbue Catchup

Summarize recent changes from git history for context recovery, handoffs, and sprint review

Security Scan

This instruction-only skill is coherent with its stated purpose (summarizing git/document/log deltas); it runs repository/log inspection commands and references other helper plugins, and it does not request secrets or install code, though one opaque config key should be reviewed.

Purpose & Capability

The name/description (git catchup/context recovery) match the SKILL.md and module contents. The instructions focus on git, documents, and logs and reference complementary plugins (sanctum, leyline, imbue modules) to gather data — these integrations are plausible for the stated purpose.

Instruction Scope

Runtime instructions and modules explicitly describe running git, grep, awk and related commands to enumerate changes, logs, and meeting notes. They do not instruct reading unrelated system secrets, contacting external endpoints, or exfiltrating data. Note: the skill expects to inspect the user's repository and log files when invoked, which is appropriate for a catchup tool.

Install Mechanism

No install spec and no code files — instruction-only. This is the lowest-risk installation model (nothing written to disk by the skill).

Credentials

The skill requests no environment variables or credentials. It does declare a required config path 'night-market.imbue:proof-of-work' (metadata.requires/config). That config key is not explained in the SKILL.md; it may be benign (e.g., reproducibility/proof metadata) but is opaque — the user should verify what that config contains and that it is not a secret before enabling the skill.

Persistence & Privilege

always is false and the skill is user-invocable. It does not request persistent system-wide modifications or elevated privileges in the instructions. Autonomous invocation is allowed (platform default) but not combined with any other concerning factors.

Assessment

This skill is instruction-only and appears to do what it says: run git/log/document inspection commands to summarize recent changes. Before installing, confirm what the 'night-market.imbue:proof-of-work' config key contains (ensure it is not a secret or external credential). Also be aware that using the skill will run repository and log inspection commands in your workspace — only invoke it in repositories and environments you intend the agent to read. If you rely on other plugins it references (sanctum, leyline, sem), check their permissions and configs separately.

Night Market Skill — ported from claude-night-market/imbue. For the full experience with agents, hooks, and commands, install the Claude Code plugin.

Table of Contents

• Overview
• When to Use
• Activation
• Progressive Loading
• 4-Step Methodology
• Output Format

Catchup Analysis Methodology

Overview

Structured method for quickly understanding recent changes in git repositories, meeting notes, sprint progress, document revisions, or system logs. Answers "what changed and what matters?" efficiently.

When To Use

• Joining ongoing work or returning after absence
• Before planning or reviewing handoffs
• Any "what happened and what's next" context

When NOT To Use

• Doing detailed diff analysis - use diff-analysis instead
• Full code review needed
  • use review-core instead
• Doing detailed diff analysis - use diff-analysis instead
• Full code review needed
  • use review-core instead

Activation

Keywords: catchup, summary, status, progress, context, handoff Cues: "get me up to speed", "current status", "summarize progress"

Progressive Loading

Load modules based on context:

Git: Load modules/git-catchup-patterns.md for git commands. Consider sanctum:git-workspace-review for initial data gathering.

Documents/Notes: Load modules/document-analysis-patterns.md for meeting notes, sprint tracking, document revisions.

Logs/Events: Load modules/log-analysis-patterns.md for time-series and metric analysis.

Always Available: imbue:proof-of-work, TodoWrite workflow, structured output.

Required TodoWrite Items

1. catchup:context-confirmed - Boundaries established
2. catchup:delta-captured - Changes enumerated
3. catchup:insights-extracted - Themes identified
4. catchup:followups-recorded - Actions captured

4-Step Methodology

Step 1: Confirm Context

Define scope (git branch, sprint, meetings), baseline (last state), and current target. See modules for commands.

Step 2: Capture Delta

Enumerate changed items with metrics. Prioritize source/config/docs over generated artifacts. See modules for strategies.

Step 3: Extract Insights

Per item: What (change), Why (motivation), Implications (tests/risks/deps). Rollup into themes.

Step 4: Record Follow-ups

Capture: Tests, Documentation, Reviews, Blockers, Questions. If none, state explicitly.

Output Format

## Summary
[2-3 sentence theme + risk overview]

## Key Changes
- [Item]: [what/why/implication]

## Follow-ups
- [ ] [Action with owner]

## Blockers/Questions
- [Item requiring resolution]

Verification: Run the command with --help flag to verify availability.

Integration

Use 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.

Token Conservation

Reference paths + lines (don't reproduce). Summarize outputs. Defer deep analysis. Use progressive loading.

Exit Criteria

• Four TodoWrite items completed
• Context/delta/insights/follow-ups captured
• Stakeholders understand state without re-reading sources

Troubleshooting

Common Issues

Command not found Ensure all dependencies are installed and in PATH

Permission errors Check file permissions and run with appropriate privileges

Unexpected behavior Enable verbose logging with --verbose flag