last-session

Summarize recent git commits, branch context, and file status for resumed development.

4|1|Updated Jan 8, 2024
One-click install
npx skills add https://github.com/OpenSourcePharmaFoundation/ospf-ayurveda-kg --skill last-session
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: last-session
Source: https://github.com/OpenSourcePharmaFoundation/ospf-ayurveda-kg/tree/main/.claude/skills/last-session
Command: npx skills add https://github.com/OpenSourcePharmaFoundation/ospf-ayurveda-kg --skill last-session

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly understand what changed and what work was in progress before your last session, so you can pick up efficiently without re-reading everything from scratch.

Core Features & Use Cases

  • Recent commit review: Summarizes the last 10–15 commits to infer what was being built or fixed.
  • Workspace state inspection: Identifies the current branch and surfaces modified/untracked files via git status and diffs.
  • Documentation cross-check: Scans for relevant project notes such as TODO items and CLAUDE.md updates to capture planned next actions.
  • Use Case: When you return to a repo after a break and want a concrete checklist of what to continue, what to verify, and which files were last touched.

Quick Start

Run the last-session Skill to get a concise summary of your current branch, recent changes, modified files, and the most likely next steps.

Frequently Asked Questions about last-session

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

FAQPage Schema
How do I resume work on a git repository after a break?

To resume work on a git repository, you review recent commits, inspect the current branch context, and check modified files to generate a task-oriented summary. This provides actionable continuity including changed files and next steps for project resumption.

What is the best way to review recent project activity before resuming development?

Reviewing recent project activity involves summarizing the last 10 to 15 git commits to infer what was being built or fixed. It also requires inspecting workspace state via git status and diffs to surface modified files for a concrete continuity checklist.

Can I get a summary of changed files and workspace status from git commits?

Yes, you can get a summary of changed files and workspace status by inspecting recent git commits, current branch context, and repository file status. This process identifies modified files to produce an actionable task-oriented summary for project resumption.

Does reviewing git diffs and branch context capture planned next actions?

Reviewing git diffs and branch context captures planned next actions by cross-checking relevant project notes such as TODO items and CLAUDE.md updates. This documentation scan identifies what to continue and which files were last touched during development.

Do I need Bash git commands to inspect repository file status for project resumption?

Yes, you need Bash git commands to inspect repository file status for project resumption. The process requires running Bash git commands and file status inspection to summarize recent commits, current branch context, and modified files for actionable continuity.