Skip to content
Back to skills

Astro Handoff

ASecurity

Honest pause/stop/handoff for ASTROLABE sessions — verifies hygiene (target/ absent, no stray worktrees/branches/locks), records exactly what is done (verified vs unverified), what is not, the next concrete step, and any uncommitted local state on the active GitHub issue, then swaps status labels. Use before any pause, stop, or turn end with unfinished issue work, when context compaction is imminent, or when abandoning a claim. GitHub issues are the only handoff medium — never local SITREP/tm...

  • 4 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 22, 2026
ai-agentsgogit

Security analysis

A100/100

Scanned September 22, 2026

npx -y skills add ChrisRoyse/Astrolabe --skill astro-handoff --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Astro Handoff?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Astro Handoff
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/chrisroyse-astro-handoff/badge)](https://www.skillsdirectory.com/skills/chrisroyse-astro-handoff)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: astro-handoff
description: Honest pause/stop/handoff for ASTROLABE sessions — verifies hygiene (target/ absent, no stray worktrees/branches/locks), records exactly what is done (verified vs unverified), what is not, the next concrete step, and any uncommitted local state on the active GitHub issue, then swaps status labels. Use before any pause, stop, or turn end with unfinished issue work, when context compaction is imminent, or when abandoning a claim. GitHub issues are the only handoff medium — never local SITREP/tmp files.
---

# Session handoff

A handoff exists so a zero-context successor can continue without re-deriving anything. It lives on the active issue — nowhere else.

## 1. Hygiene before writing

- Classify `.tmp/astrolabe-launcher.lock` through `scripts\launcher-lock-status.ps1`. Exact ownership is `(pid, owner_process_start_utc_ticks)`, never numeric PID alone. Only `absent` permits a new claim; `held` is read-only, and stale/PID-reused, unreadable, transition, or unevaluable state requires tracker-bound recovery.
- Never delete `target/` manually. Normal cleanup belongs to the exact live launcher owner while it retains the protocol lease. If `target/` remains after that owner exits, preserve it, record the authoritative classifier/attribution state, complete any required tracker-bound reclaim, and clean only under a fresh exact launcher lease.
- `git status --short` — know every uncommitted/untracked path. Remove stray temp files this session created; keep repo-controlled outputs out of the index.
- List stray worktrees/branches this session created (`git worktree list`, `git branch --list 'sweep/*'`) — remove finished ones or name them in the handoff.

## 2. The handoff comment (on the active issue)

State exactly, without optimism:
- **Done** — only items with verification evidence in this thread; anything unverified goes to Not done with a note.
- **Not done** — remaining scope, including partially-written code.
- **Next concrete step** — the single command/edit a successor runs first.
- **Uncommitted state** — paste `git status --short` (or "clean"); name any stash/branch/worktree holding work and any staged-but-ungated server edits.
- **Blockers/conflicts** — lock holders, red gates with issue links.

Embed the telemetry block (kind `handoff`, required keys `done[]`, `not_done[]`, `next`, `uncommitted`) per `${CLAUDE_PROJECT_DIR}/.claude/skills/astro-telemetry/references/spec.md`.

## 3. Labels

- Another agent can resume → swap `status:in-progress` → `status:ready`.
- Genuinely blocked → `status:blocked`, naming the blocker (issue link) in the comment.
- Never leave `status:in-progress` silently on a stopped effort.

## 4. Commit discipline

Committable verified work is committed and pushed (`Refs #N`) before the handoff. Unverified code is named in the handoff instead of being committed as if done — or committed to a clearly-named side branch, stated in the comment.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.