session-wrap

Gather git context and project metadata into structured Obsidian session notes.

23|3|Updated May 17, 2024
One-click install
npx skills add https://github.com/johnend/dots --skill session-wrap-johnend
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-wrap
Source: https://github.com/johnend/dots/tree/main/common/.ai/skills/session-wrap
Command: npx skills add https://github.com/johnend/dots --skill session-wrap-johnend

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of a comprehensive end-of-session note by collecting context from the current project and synthesizing it into a structured Obsidian document.

Core Features & Use Cases

  • Phase-based data collection: gathers branch, recent commits, diffs, status, and current directory to capture the work context.
  • Context extraction and classification: identifies Jira ticket references, repo identity, and workspace scope to tailor the destination and metadata.
  • Synthesis and handoff: compiles the notes into a structured document and hands it off to chronicle-docs for formatting and storage in Obsidian.

Quick Start

Run the session-wrap skill to generate a rich Obsidian note from your current workspace.

Frequently Asked Questions about session-wrap

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

FAQPage Schema
How do I auto-generate Obsidian notes from git history at the end of a coding session?

To auto-generate Obsidian notes from git context, the tool collects your branch, recent commits, diffs, and status, then compiles them into a structured chronicle document handed off to chronicle-docs for storage.

What is the best way to create a structured session chronicle in Obsidian for my development work?

Creating a structured session chronicle involves a two-phase collection process that extracts project metadata, identifies Jira ticket references and repo identity, then formats the workspace context into a rich Obsidian note.

Can I use this to track Jira ticket references across different project workspaces?

Yes, you can track Jira ticket references because the context extraction phase identifies ticket references, repo identity, and workspace scope to tailor the destination and metadata of your Obsidian notes.

Does the session note generation work with general personal projects or only specific workspaces?

Session note generation works with both general personal projects and specific workspaces, including environments under ~/Developer/fanduel/, by gathering current directory context and project metadata.

Do I need chronicle-docs to format and store the extracted git context in Obsidian?

Yes, you need chronicle-docs because the process compiles collected git context and project metadata, then performs a handoff to chronicle-docs for final formatting and storage in Obsidian.