wrap

Commit WIP changes and generate structured handoff summaries for session transitions.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/YarikChekin/ralph-cc --skill wrap-yarikchekin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wrap
Source: https://github.com/YarikChekin/ralph-cc/tree/main/skills/wrap
Command: npx skills add https://github.com/YarikChekin/ralph-cc --skill wrap-yarikchekin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents loss of context at session end by automatically committing in-progress work (WIP) and generating a clear handoff summary for the next agent.

Core Features & Use Cases

  • Auto-commit WIP changes when wrapping a session to preserve progress.
  • Generate a structured handoff summary capturing completed work, remaining tasks, and next steps.
  • Works within Ralph workflows to maintain continuity across sessions and handoffs.

Quick Start

Run /wrap at the end of a session to commit in-progress work and prepare the next agent with a concise handoff.

Frequently Asked Questions about wrap

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

FAQPage Schema
How do I automate session handoffs and preserve WIP context?▼

Automating session handoffs requires committing WIP changes and summarizing context for the next agent. This process prevents context loss by generating a structured handoff summary capturing completed work, remaining tasks, and next steps.

What is a WIP commit and when do I need it in a development sprint?▼

A WIP commit is a deterministic commit of in-progress work made during a development sprint. You need it at the end of a session to preserve progress and prevent loss of context before transitioning to a new agent.

How do I create a handoff summary for the next agent?▼

Creating a handoff summary involves logging progress through a defined sequence of checks. It captures completed work, remaining tasks, and next steps to prepare the next agent with concise context continuity.

Can I use automated WIP logging within testing workflows?▼

Yes, WIP logging is applicable to testing workflows. It maintains continuity across sessions by automatically committing in-progress work and preparing a concise handoff summary for the next agent.

What's the best way to log progress at the end of a development session?▼

The best way to log progress at session end is to run a wrap command. It executes a defined sequence of checks to commit WIP changes and generate a structured handoff summary for the next agent.

Do I need a specific workflow environment to execute deterministic commits for handoffs?▼

No specific external dependencies are required to execute deterministic commits for handoffs. The process works within Ralph workflows to maintain continuity across sessions through defined log entries.