resume

Name: resume
Availability: InStock
Author: computerconnection

Aggregate handoffs, git history, and project state into a structured resume brief.

Updated Mar 31, 2026

Search Tags:#onboarding #resume #handoffs #project-context #git-history #state-recovery

Ready to run

npx skills add https://github.com/ComputerConnection/zach-pack --skill resume-computerconnection

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: resume
Source: https://github.com/ComputerConnection/zach-pack/tree/main/skills/resume
Command: npx skills add https://github.com/ComputerConnection/zach-pack --skill resume-computerconnection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reconstructs project context so you can pick up exactly where you left off by aggregating handoffs, git history, and project state, reducing ramp-up time and miscommunication.

Core Features & Use Cases

Reconstructs project context from repository history, handoffs, and current state
Identifies original intent, decisions, blockers, and next steps to unblock work
Use Case: Start a session on an existing project and continue seamlessly without re-explaining prior work

Quick Start

Run the resume skill with a project path to reconstruct the latest context and continue work.

Frequently Asked Questions about resume

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

FAQPage Schema

How do I reconstruct project context from git history and handoffs to resume work?▼

To reconstruct project context, aggregate repository handoffs, git history, and current state to extract original intent, decisions, blockers, and next steps into a structured brief. This allows you to resume work without re-explaining prior sessions.

What is the best way to pick up an existing project without re-explaining prior work to stakeholders?▼

The best way to pick up an existing project is by aggregating handoffs and git history to align stakeholders. Reconstructing context identifies original intent, current progress, and next steps to unblock work and reduce ramp-up time.

Can I recover project state and identify blockers across different repositories and teams?▼

Yes, you can recover project state across teams and repositories by reconstructing context from existing handoffs and git history. This process handles missing context and aligns stakeholders by extracting decisions and current blockers.

How do I generate a structured resume brief for a session starting on an existing codebase?▼

Generate a structured resume brief by running context reconstruction with your project path. This aggregates repository history and current state to output original intent, decisions, blockers, and next steps for your existing codebase.

Does project context reconstruction work for sessions with missing handoff documentation?▼

Yes, context reconstruction works with missing handoff documentation by relying on git history and current project state. It handles missing context to align stakeholders and extract necessary decisions, blockers, and next steps.

When should I avoid using automated context reconstruction for project state recovery?▼

You should avoid automated context reconstruction when repository history is sparse or handoffs lack technical detail. If git history and current state do not reflect actual decisions, the generated resume brief will lack accurate intent and blockers.