continue-work

Reads MEMORY.md and git state to summarize pending work.

Updated Oct 1, 2024
One-click install
npx skills add https://github.com/einargudnig/dotfiles --skill continue-work
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: continue-work
Source: https://github.com/einargudnig/dotfiles/tree/main/claude/skills/continue-work
Command: npx skills add https://github.com/einargudnig/dotfiles --skill continue-work

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fast context recovery for interrupted sessions by assembling local state, memory hints, and recent Git activity to help you pick up where you left off.

Core Features & Use Cases

  • Local context gathering: Determine current worktree or folder name.
  • Memory filtering: Read MEMORY.md and filter pending items for the current worktree.
  • Git state visibility: Show branch, recent commits, and uncommitted changes.
  • Active plan awareness: Locate the most recent plan file and reference it for suggested steps.

Quick Start

Tell me to continue or resume, and I will summarize your current work state and pending items.

Frequently Asked Questions about continue-work

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

FAQPage Schema
How do I resume work on an interrupted coding session?

To resume work, you can trigger context recovery by asking to continue. The system reads your MEMORY.md file, checks your git branch and status, and references recent plan files to summarize pending work.

What is the best way to recover context after stepping away from a git project?

Recovering context is done by gathering local git state and memory hints. It shows your current branch, recent commits, and uncommitted changes so you can pick up exactly where you left off.

How does filtering pending work by local worktree help me continue coding?

Filtering pending work by worktree ensures you only see relevant tasks. It reads MEMORY.md and isolates items specific to your current folder, preventing cross-project context bleed when you resume.

Can I use this to find my most recent plan file and suggested next steps?

Yes, you can locate your most recent plan file for suggested next steps. The system automatically searches your local project directory to reference the active plan and guide your immediate actions.

Do I need a MEMORY.md file to gather local context and surface pending work?

You do not strictly need a MEMORY.md file to gather local context, but having one significantly improves recovery. It filters pending items for the current worktree, while git state provides baseline session visibility.