sleep

Store end-of-session context in GitHub Issues via the GitHub CLI.

8|1|Updated Aug 5, 2025
One-click install
npx skills add https://github.com/ArtyMcLabin/ClaudeCode-global-config --skill sleep
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sleep
Source: https://github.com/ArtyMcLabin/ClaudeCode-global-config/tree/main/skills/sleep
Command: npx skills add https://github.com/ArtyMcLabin/ClaudeCode-global-config --skill sleep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-of-session context preservation by capturing relevant topics, decisions, and next steps and storing them in GitHub Issues within the PA repository so that future sessions can resume without re-explaining context.

Core Features & Use Cases

  • Create or update a GitHub Issue representing the current session topic.
  • Append new context, findings, decisions, and next steps to the issue body across multiple interactions.
  • Identify session context automatically and organize issues to support quick resumption of work.
  • Use Case: Conclude a debugging session by archiving the topic alongside the fixes and next steps; later, reopen or reference the issue to continue.

Quick Start

Save the current session context to PA's GitHub Issues. If an open issue matches the topic, append the new context; otherwise create a new issue with sections for Goal, Context, Findings, Decisions, Open Questions, and Next Steps. Commands typically use the GitHub CLI (gh) to create or update issues, for example: gh issue list --repo <GITHUB_USER>/PersonalAssistant-ClaudeCode --state open --search "<topic keywords>" gh issue create --repo <GITHUB_USER>/PersonalAssistant-ClaudeCode --title "<Descriptive title>" --body "<formatted body>"

Frequently Asked Questions about sleep

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

FAQPage Schema
How do I preserve session context across multiple GitHub CLI interactions?

To preserve session context, this Skill captures relevant topics, decisions, and next steps, storing them in GitHub Issues within the PersonalAssistant-ClaudeCode repository so future sessions can resume work without re-explaining context.

What is the best way to save debugging session findings to GitHub Issues for later resumption?

Saving debugging session findings to GitHub Issues involves creating or updating an issue in the PA repository, appending new context, fixes, and next steps to the issue body across multiple interactions for quick resumption.

Do I need the GitHub CLI to store end-of-session context in repository issues?

Yes, you need the GitHub CLI (gh) and access to the PersonalAssistant-ClaudeCode repository to create or update issues that store your end-of-session context for continuity across sessions.

How does context preservation work when an open issue already matches my session topic?

Context preservation works by searching for open issues matching topic keywords; if a match exists, new context, findings, and decisions are appended to the issue body, otherwise a new issue is created with structured sections.

Can I organize GitHub Issues for planning and wrap-up tasks to support quick resumption of work?

Yes, you can organize GitHub Issues for planning and wrap-up tasks by structuring issue bodies with sections for Goal, Context, Findings, Decisions, Open Questions, and Next Steps to support quick work resumption.