wrap

Generate a session narrative, edit identity state if needed, commit and push changes following the wrap protocol.

2|Updated Jul 5, 2018
One-click install
npx skills add https://github.com/tnez/dotfiles --skill wrap-tnez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wrap
Source: https://github.com/tnez/dotfiles/tree/main/claude/dot-claude/skills/wrap
Command: npx skills add https://github.com/tnez/dotfiles --skill wrap-tnez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill standardizes the end-of-session ritual by generating a session narrative, applying a targeted bridge edit if needed, and performing the necessary commit and push of identity data to ensure the next session starts oriented.

Core Features & Use Cases

  • Write a structured session narrative to summarize what happened during the interactive session.
  • Perform a targeted bridge edit when required to align state with the identity repo.
  • Commit and push identity changes so subsequent sessions begin from a consistent baseline.
  • Follow the canonical wrap protocol documented in the identity repository to ensure consistency across machines.

Quick Start

Read the wrap protocol at ~/Code/dottie-weaver/identity/processes/wrap.md and execute its steps to finalize the session.

Frequently Asked Questions about wrap

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

FAQPage Schema
How do I automate my git commit and push workflow to finalize a development session?

Automating a git commit and push for your session wrap involves generating a narrative of changes, applying targeted bridge edits, and pushing identity data to ensure consistent baselines across machines.

What is a session narrative and how does it help with end-of-session git commits?

A session narrative is a structured summary of what happened during an interactive session. It standardizes your git commit process by documenting changes before pushing identity state to a repository.

How do I maintain consistent identity state across multiple machines and sessions?

Maintaining consistent identity state across machines requires committing and pushing session changes to a shared repository. Following a canonical wrap protocol ensures subsequent sessions start from a consistent baseline.

Can I apply targeted edits to my repository state before pushing a session wrap?

Yes, you can apply targeted bridge edits to align state with your identity repo before committing. This ensures the pushed changes reflect both your session narrative and necessary state corrections.

What's the best way to standardize an end-of-session wrap protocol for git repositories?

Standardizing an end-of-session wrap protocol involves documenting canonical steps for narrative generation, bridge edits, and commit/push operations. This ensures consistent execution across different machines and sessions.