CommunitySchreiben & Editierengithub.com

labsiqbal/wrap-session

Hermes skill for owner-approved session wrap receipts

Was ist wrap-session?

wrap-session is a Claude Code agent skill that hermes skill for owner-approved session wrap receipts.

Funktioniert mit~Claude Code~Codex CLI~Cursor
npx skills add labsiqbal/wrap-session

Installed? Explore more Schreiben & Editieren skills: steipete/notion, affaan-m/seo, affaan-m/brand-voice · View all 6 →

In Ihrer bevorzugten KI fragen

Öffnet einen neuen Chat, in dem dieser Agent-Skill bereits geladen ist.

Dokumentation

Wrap Session

Close current session cleanly. Chat is draft. Disk is truth.

/wrap-session means: inspect session residue, propose durable actions, wait for owner approval, execute only approved actions, then write receipt.

Use

Use before leaving session with code, decisions, documents, operational changes, or unfinished work another session must resume.

Skip chitchat with nothing durable.

Receipt

One receipt per session:

~/.local/state/session-wrap/<session_id>.md

Use harness session ID when available. Otherwise generate local-YYYYMMDD-HHMMSS-<cwdslug>.

Receipt front matter must contain:

  • session_id
  • harness: active harness name, or other
  • source: active session surface, or other
  • cwd: absolute path
  • project: nearest Git root name, nearest directory name, or (root)
  • wrapped_at: ISO-8601 timestamp
  • next: one first action

Body headings: Done, Decisions, Written, Git, Deferred, Next.

A receipt means clean close. Unfinished work is deferred, never an open receipt. Re-wrap same session ID overwrites old receipt.

Procedure

1. Inspect

Collect session ID, source, absolute current directory, project label, and—when inside a Git worktree—git status --short --branch.

Completion: every receipt field has a truthful value.

2. Draft Wrap Plan

Do not write yet. Show:

WRAP PLAN
project: ...
cwd: ...

Done:
- outcome + evidence path, commit, or URL

Decisions to persist:
1. decision → proposed path, or skip

Deferred work:
- item → proposed backlog, ticket, or document home

Git:
- clean, or dirty and intentional
- proposed commit message, if needed
- push: no by default

Memory:
- stable fact, or none

Next session starts with:
- one action

Point to existing artifacts. Do not copy whole chat into a document. Put every unfinished item in a real home or explicitly mark it skipped.

3. Owner gate

Ask owner to approve or edit:

  1. Decisions, Deferred, and Memory writes
  2. Git action: leave, commit, or commit+push
  3. Plan edits

Accept all, selected numbers, free-text edits, or cancel.

On cancel: write nothing and report cancellation.

4. Execute approved actions

Run only approved writes and Git actions. Verify each external effect before claiming success. Report failures as failures.

5. Write receipt

Create parent directory when missing. Write:

---
session_id: <id>
harness: <harness>
source: <session surface|other>
cwd: <absolute path>
project: <project>
wrapped_at: <ISO-8601>
next: <one action>
---

# Wrap Session · <project>

## Done
- ...

## Decisions
- ...

## Written
- path — what, or (none)

## Git
- ...

## Deferred
- item → home, or (none)

## Next
- ...

Completion: receipt file exists at expected path.

6. Confirm

Reply with receipt path, files or Git changes made, deferred work and its home, and Next line. Stop.

Optional status report

Run companion detector when available:

bin/wrap-status.sh
bin/wrap-status.sh init

It reads Hermes state.db plus receipts. init is explicit and creates only receipt directory plus rollout baseline. Without Hermes state database, it reports receipts and exits successfully.

Verwandte Skills

steipete/notion

Notion CLI/API for pages, Markdown content, data sources, files, comments, search, Workers, and raw API calls.

community

affaan-m/seo

Audit, plan, and implement SEO improvements across technical SEO, on-page optimization, structured data, Core Web Vitals, and content strategy. Use when the user wants better search visibility, SEO remediation, schema markup, sitemap/robots work, or keyword mapping.

community

affaan-m/brand-voice

Build a source-derived writing style profile from real posts, essays, launch notes, docs, or site copy, then reuse that profile across content, outreach, and social workflows. Use when the user wants voice consistency without generic AI writing tropes.

community

affaan-m/crosspost

Multi-platform content distribution across X, LinkedIn, Threads, and Bluesky. Adapts content per platform using content-engine patterns. Never posts identical content cross-platform. Use when the user wants to distribute content across social platforms.

community

affaan-m/x-api

X/Twitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.

community

affaan-m/content-engine

Create platform-native content systems for X, LinkedIn, TikTok, YouTube, newsletters, and repurposed multi-platform campaigns. Use when the user wants social posts, threads, scripts, content calendars, or one source asset adapted cleanly across platforms.

community