session-loop

Automate session wrap, rehydration, and drift detection for multi-session projects.

1|Updated Nov 18, 2023
One-click install
npx skills add https://github.com/akshayrao14/git-practices --skill session-loop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-loop
Source: https://github.com/akshayrao14/git-practices/tree/main/skills/session-loop
Command: npx skills add https://github.com/akshayrao14/git-practices --skill session-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Claude Code, Codex, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill addresses the challenge of losing context and decisions between sessions in multi-day projects, ensuring a smooth transition and preserving crucial information.

Core Features & Use Cases

  • Session Wrap: Safely end a session and log necessary information.
  • Session Catchup: Resume work with context preservation and drift detection.
  • Session Checkpoint: Lightweight savepoints during a session.
  • Session Drift: Verify the world's state against ledger claims.
  • Session Decide: Log ADR-style decisions in the project ledger.
  • Session Open Loops: Scan and prioritize unresolved threads.
  • Use Case: Ideal for engineering, research, writing, and project management scenarios where context is critical across multiple sessions.

Quick Start

To end your session, run /session-wrap. To start your session, run /session-catchup.

Frequently Asked Questions about session-loop

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

FAQPage Schema
How do I preserve context and decisions across multi-day coding sessions?

To preserve context across multi-day coding sessions, use session wrap and catchup commands to log project state and rehydrate context. This Skill automates context preservation by verifying project state against ledger entries, ensuring continuity.

How do I resume a multi-day project without losing previous session context?

You resume a multi-day project by running a session catchup command that rehydrates context and detects drift. It verifies the current project state against logged ledger entries to ensure consistency before continuing.

Does session-loop work with Claude Code and Codex for project coordination?

Yes, session-loop requires integration with either Claude Code or Codex to function. It leverages these dependencies to automate session wrap, rehydration, and drift detection for multi-session project coordination.

What is session drift detection and how does it verify project state?

Session drift detection verifies the actual world state against claims recorded in the project ledger. It identifies discrepancies between the expected project condition and the real environment state after a session transition.

How do I log architecture decisions during a multi-session workflow?

You log architecture decisions during a multi-session workflow using the session decide command. It records ADR-style decisions directly into the project ledger to maintain a consistent historical record across sessions.

What are the limitations of using a ledger-based approach for session management?

A ledger-based approach for session management relies on accurate state logging and requires Claude Code or Codex. It may not detect environmental changes occurring outside the logged workflow without explicit drift verification.