wrap-up

Consolidate git activity, notes, and tasks into a daily summary.

3|Updated Dec 3, 2025
One-click install
npx skills add https://github.com/braselog/researchAssistant --skill wrap-up-braselog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wrap-up
Source: https://github.com/braselog/researchAssistant/tree/main/.ra/skills/wrap-up
Command: npx skills add https://github.com/braselog/researchAssistant --skill wrap-up-braselog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-of-day wrap-up consolidates today’s git activity, contextual notes, and tasks into a concise daily summary, helping you maintain continuity and clear planning.

Core Features & Use Cases

  • Automated daily summary: Generate a structured entry that captures what happened, decisions, and next steps.
  • Notes integration: Pull in today’s /note entries and activity notes to seed the log.
  • Planning & handoff: Prepend a filled summary to .research/logs/activity.md for easy reference and tomorrow’s planning.

Quick Start

Use the wrap-up command at the end of a work session to generate and save today's summary. Then review and refine the draft before finalizing.

Frequently Asked Questions about wrap-up

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

FAQPage Schema
How do I generate a daily summary of my git activity and notes?

You can generate a daily summary by running an automated end-of-day wrap-up that consolidates today's git activity, notes from activity.md, and tasks from tasks.md into a single structured entry. This process reads local repository state to gather commits and integrate contextual notes.

What is the best way to automate end-of-day work session logging?

The best way to automate end-of-day logging is to use a wrap-up command that reads your git activity and local markdown notes, then prepends a filled summary to .research/logs/activity.md. This captures decisions and next steps while seeding planning for tomorrow.

Does the daily summary tool require specific file formats for notes and tasks?

Yes, the daily summary tool requires notes and tasks to be stored in specific markdown files. It reads today's entries from activity.md and pulls tasks from tasks.md to integrate them into the final structured log.

Can I use local git commands to track project activity for daily logs?

Yes, you can use local git commands to track project activity for daily logs. The wrap-up process uses standard git commands and filesystem access to gather repository activity and consolidate it into a concise daily summary entry.

How do I plan for tomorrow's tasks using today's git activity and notes?

You plan for tomorrow by generating a structured daily entry that captures today's git activity, decisions, and next steps. This filled summary is prepended to your daily log to provide easy reference and seed your upcoming work planning.

What are the limitations of using filesystem access for daily git activity logs?

A limitation of using filesystem access for daily logs is that the wrap-up process depends on local repository state and specific markdown files. It cannot gather activity from remote repositories or integrate notes stored outside the expected directory structure.