session-restart

Recovers project context by analyzing git history, CI/CD status, and build queues.

1|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/Brandondaymdr/Claude-Skills --skill session-restart
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-restart
Source: https://github.com/Brandondaymdr/Claude-Skills/tree/main/session-restart
Command: npx skills add https://github.com/Brandondaymdr/Claude-Skills --skill session-restart

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, git, node, jq, bc, and includes references (resource) components.

What problem does it solve?

This skill eliminates the cognitive overhead of returning to a project by automatically synthesizing your last session's progress, current git state, and project health into a concise briefing.

Core Features & Use Cases

  • Context Recovery: Automatically identifies your last working state, pending tasks, and uncommitted changes.
  • Health Monitoring: Performs automated checks on CI status, test suites, and build pipelines to ensure you start from a stable foundation.
  • Fleet Integration: Synchronizes build queues for autonomous agent projects to prevent drift between sessions.

Quick Start

Trigger the session-restart skill when you return to a project to get a full briefing on your current progress and recommended next steps.

Frequently Asked Questions about session-restart

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

FAQPage Schema
How do I recover project context after stepping away from a git repository?

Recover project context by analyzing git history, CI/CD status, and local development artifacts. This process synthesizes your last working session, pending tasks, and uncommitted changes into a concise briefing to restore momentum.

What is the best way to verify project health before resuming development?

Verifying project health involves performing automated checks on CI status, test suites, and build pipelines. This ensures you start from a stable foundation and can identify pending work or regressions.

Do I need the GitHub CLI to sync build queues for autonomous agent projects?

Yes, the GitHub CLI and git are required to analyze branch divergence and CI/CD status. An optional Node.js runtime is additionally required for fleet queue synchronization to prevent drift between sessions.

Can I use this workflow to identify branch divergence and pending work across different software projects?

Yes, this workflow operates across diverse software projects to identify branch divergence and pending work. It evaluates local development artifacts and detects regressions regardless of the project type.

Why does context recovery fail if local development artifacts are missing?

Context recovery fails because it relies on local development artifacts to identify your last working state. Missing artifacts prevent the system from synthesizing uncommitted changes and recommending next steps accurately.