delete-last-handover

Clear Last Handover

---

Instructions

First, use the Glob tool to list .claude/handovers/*.md. Sort results by filename descending (newest first, since filenames are timestamps).

Using the Glob results, determine which branch applies:

Branch A — No Files

If the listing shows an error (e.g., "No such file or directory"), is empty, or contains no .md files:

No handover files found — nothing to delete.

Stop here.

Branch B — Files Exist

If there are one or more .md files:

1. The first .md file is the most recent (sorted newest-first). This is the deletion target.
2. State the pre-deletion confirmation:

   Target: {filename} Remaining after deletion: {count - 1} handover file(s)

3. Ask the user for confirmation using AskUserQuestion:

   Delete {filename}? This cannot be undone. Actions: ["Yes, delete it", "Cancel"]

4. If cancelled, stop: > Cancelled — no files were deleted.
5. Delete it using the Bash tool:

   rm .claude/handovers/{filename}
   

6. Memory cleanup: Read the auto-memory file (MEMORY.md in your memory directory). Remove only lines that contain the <!-- handover-sourced --> marker from MEMORY.md using the Edit tool. Leave all other entries untouched. Count removed lines as {N}. After cleanup, inform the user:

   Also removed {N} handover-sourced references from MEMORY.md. If no matching entries were found, skip this message.

---

Output Template

After deletion, output:

Deleted: {filename} Remaining: {count} handover file(s)

---

Anti-Patterns

• Don't delete without stating the target filename first — the user needs to see what will be removed.
• Don't skip verification after deletion — always re-list to confirm the file is gone.
• Don't proceed if the directory doesn't exist — report "nothing to delete" and stop.

---

Verification

Re-list .claude/handovers/ after deletion to confirm the file is gone and the remaining count is correct.

---

Test Plan

Trigger: /delete-last-handover (and /quiver:delete-last-handover should also work)

Setup:

• A .claude/handovers/ directory exists in the project root with one or more .md files (timestamp-named).

Expected behavior:

1. Skill lists handover files via Glob, identifies the newest as the deletion target, and states Target: <filename> plus the remaining count.
2. Skill calls AskUserQuestion with ["Yes, delete it", "Cancel"].
3. On confirm, the target file is removed and the skill re-lists the directory to verify.
4. The skill scans MEMORY.md for lines tagged <!-- handover-sourced --> and removes them via Edit, reporting how many were removed.
5. On cancel, no files are deleted and the skill exits with Cancelled — no files were deleted.

Verification checklist:

• Slash menu shows /delete-last-handover.
• Skill stops gracefully when .claude/handovers/ is empty or missing (No handover files found — nothing to delete.).
• Confirmation prompt is presented before any rm runs.
• MEMORY.md lines without the <!-- handover-sourced --> marker remain untouched.
• Final output reports the deleted filename and remaining count.

Known gotchas:

• The Glob result sort is lexicographic; this is correct because handover filenames use the YYYY-MM-DD_HH-MM-SS.md timestamp format. If filenames ever drift from that format, sort order breaks.