git-resume

Analyze git commit history and diffs to summarize recent work and pending tasks.

1|1|Updated Jul 7, 2026

Search Tags:#automation #git #workflow #development #context #productivity

Ready to run

npx skills add https://github.com/hicucu/my-poor-ai --skill git-resume

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-resume
Source: https://github.com/hicucu/my-poor-ai/tree/main/skills/git-resume
Command: npx skills add https://github.com/hicucu/my-poor-ai --skill git-resume

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the loss of mental context when returning to a project by automatically analyzing recent commit history, diffs, and unfinished tasks to reconstruct your previous workflow.

Core Features & Use Cases

Context Reconstruction: Analyzes commit messages and code changes to summarize what you were working on.
Task Tracking: Identifies unfinished work, including TODOs, FIXMEs, and uncommitted changes.
Use Case: If you stopped working on a feature last week, use this skill to get a summary of your progress, the files you were editing, and a recommended next step to resume development immediately.

Quick Start

Use the git-resume skill to analyze your work from yesterday and suggest the next steps for your current session.

Frequently Asked Questions about git-resume

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

FAQPage Schema

How do I restore coding context from git history after a break?▼

To restore coding context from git history, analyze recent commit messages and code diffs to summarize previous work and identify pending tasks. This approach reconstructs your development workflow by reviewing uncommitted changes and recent code modifications.

Can I track unfinished tasks and TODOs in my local git repository?▼

Yes, you can track unfinished tasks in your local git repository by analyzing uncommitted changes and scanning diffs for TODOs and FIXMEs. This process identifies pending work and helps reconstruct what features were actively being developed.

Does git context reconstruction work without remote repository access?▼

Git context reconstruction works entirely on local repositories using git CLI access. It performs log analysis and status checks on your current working directory, requiring no remote repository connectivity to summarize recent work and identify unfinished code.

What is the best way to resume development on a feature from last week?▼

The best way to resume development is to analyze recent git commit history and diffs to generate a summary of your progress. This identifies the files you were editing, unfinished tasks, and recommends logical next steps to continue coding immediately.

How do I get a summary of recent uncommitted changes in git?▼

To get a summary of recent uncommitted changes in git, run a status check and diff analysis on your current working directory. This identifies modified files, pending TODOs, and unfinished code to help you quickly understand your current project state.

What are the limitations of using git logs for workflow context reconstruction?▼

Git logs for workflow context reconstruction are limited by commit message quality and require local git CLI access. It relies on analyzing existing diffs and uncommitted changes, so poorly documented commits or missing local history reduce context accuracy.