recap

Compile end-of-day work recaps from Claude Code, git, GitHub, and Monday.com into Obsidian markdown notes.

4|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/Ni-Bu/skills --skill recap-ni-bu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: recap
Source: https://github.com/Ni-Bu/skills/tree/main/recap
Command: npx skills add https://github.com/Ni-Bu/skills --skill recap-ni-bu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a full day of scattered Claude Code activity into a clear, ready-to-file recap so you can remember what happened, what changed, and what still needs attention.

Core Features & Use Cases

  • Daily synthesis: Pulls together Claude Code session transcripts, git history, pull request activity, and optional Monday.com updates into one coherent note.
  • Actionable reporting: Separates completed work, in-progress items, follow-ups, and review feedback so nothing important gets lost.
  • Obsidian output: Writes the recap into a dated markdown note in your vault for easy search, linking, and long-term tracking.

Quick Start

Ask the recap skill to generate a recap for a chosen date and save it to your Obsidian vault.

Frequently Asked Questions about recap

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a daily recap of Claude Code sessions and git history?

To generate a daily recap, the skill parses Claude Code session transcripts, git history, and pull request activity for a target date, compiling them into a structured markdown note with frontmatter and linked references.

Can I save Claude Code activity summaries directly to an Obsidian vault?

Yes, you can save Claude Code activity summaries directly to an Obsidian vault. The skill generates a dated markdown note with linked references, enabling easy search and long-term tracking within your vault.

Does the daily recap support Monday.com updates and GitHub pull requests?

Yes, the daily recap supports Monday.com updates and GitHub pull requests. It cross-references activity from Claude Code sessions, git history, pull requests, and optional Monday.com updates into one coherent note.

What is the best way to track completed work and follow-ups from Claude Code transcripts?

The best way to track completed work and follow-ups is by compiling them into an actionable daily recap. The skill separates completed work, in-progress items, follow-ups, and review feedback so nothing important gets lost.

Do I need to specify a target date when creating a daily work summary?

Yes, you need to specify a target date when creating a daily work summary. The skill requires date resolution to accurately compile the daily summary across code changes, pull requests, and attention items for that specific date.