amp-close_skill

This skill helps you gracefully close Amp sessions by gathering context, reflecting insights, deciding immediate vs future actions, and generating
  • Python

0

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill spm1001/trousse --skill amp-close

  • SKILL.md15.6 KB

Overview

This skill performs Amp's mandatory end-of-session ritual. It runs a four-phase GODAR loop (Gather, Orient, Decide, Act) to capture context, surface risks and drift, create cross-harness handoffs, and persist a searchable extraction so work never silently drops. Invoke it when a session is ending or the user signals closure.

How this skill works

The skill gathers thread and repo context (thread ID, git/bon status, files touched), then orients via a three-beat reflection: agent observations, a six-question Oracle review for substantive sessions, and user reflection. After the user approves, it decides Now vs Next actions, executes immediate tasks, writes a Claude-discoverable handoff file, and writes/indexes a garde extraction JSON. It also offers optional git commits and pushes when appropriate.

When to use it

  • User says phrases like “wrap up”, “let's finish”, “close out”, or “end of session”
  • Session finished work or several meaningful changes were made
  • Context window is near capacity and you must persist state
  • Before invoking cross-harness handoff when work might continue elsewhere
  • When you need searchable memory for future sessions

Best practices

  • Always run the Orient beats before deciding — agent observations, Oracle (if substantive), then user reflection
  • Gate Oracle to substantive sessions (multiple files/architectural decisions); otherwise self-reflect to save calls
  • Surface every incomplete item into Now or Next — nothing silent or implicit
  • Write the handoff file in Claude’s expected directory and format so next sessions can discover it
  • Attempt garde extraction and scan; if garde-manger is missing, warn and still produce handoff and triage

Example use cases

  • Finishing a refactor that touched multiple files — capture drift, risks, and queue tests as Next
  • After a feature implementation, create a handoff for future Claude sessions and index an extraction for searchable memory
  • Near-end session with full context window — run the ritual to persist learnings before context is lost
  • Small quick fix: perform a brief self-reflection, mark Done, and skip Oracle to avoid unnecessary calls
  • Transition work from Amp to Claude or another toolchain by writing the mandated handoff.md so the next agent can resume

FAQ

Invoke Oracle for substantive sessions: multiple file changes, architecture choices, or non-trivial risks. For tiny edits or trivial work, answer the six questions yourself to conserve calls.

What if garde-manger isn’t installed?

Skip the extraction/index steps, warn the user, and still write the handoff and Now/Next triage. Handoff + triage preserve continuity even without searchable indexing.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational