Fear of abandonment

Skill jagp/claude-session-guardrails/fear-of-abandonment/skills/fear-of-abandonment

Scan the current git repo for stranded agent work — worktrees, branches not merged into the integration branch (develop/main), and worktrees holding uncommitted changes. Use when you suspect work happened in a worktree or background session but never got merged, or to audit before deleting worktrees.From its SKILL.md

Install

npx -y skills add jagp/claude-session-guardrails --skill fear-of-abandonment

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.2 KB, 216 tokens by cl100k_base, as published. Nobody here has run it

fear-of-abandonment

A read-only audit that surfaces work which may have been left behind — the "I thought this shipped but it isn't live" case.

What to do

Run the scanner:
```
sh "${CLAUDE_PLUGIN_ROOT}/bin/scan.sh"
```
Present the output to the user, calling out findings in this priority order:
- Branches not merged into the integration branch — committed, durable, but never integrated. This is the most likely home of "lost" work.
- Worktrees with uncommitted changes — fragile work that is invisible in SourceTree's main working-copy view.
- Existing worktrees — candidates for cleanup once their branch is confirmed merged.
If nothing is stranded, say so plainly.

Hard rule

This skill is read-only. Do not merge, delete, prune, or modify anything. Report what you find and stop. Any remediation is a separate, explicit decision for the user.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most pr commit review skills give in 216 tokens

Counted across 888 of the 1,342 authors here whose files we hold, read 2026-08-07

Use conventional commits formatin 127 of 888, across 115 files
Keep subject line under 72 charactersin 62 of 888, across 48 files
Delete branches after mergein 51 of 888, across 38 files
Use imperative mood in subject linein 51 of 888, across 42 files
Use imperative mood in commit messagesin 44 of 888
Verify directory is ignored before creating worktreein 43 of 888, across 12 files
Generate a conventional commit messagein 43 of 888
Add unignored worktree directories to gitignorein 42 of 888, across 10 files
Make atomic commitsin 39 of 888, across 27 files
Run tests before committingin 36 of 888, across 25 files
Verify clean test baselinein 35 of 888, across 9 files
Split unrelated changes into separate commitsin 35 of 888, across 30 files

Said here and by no other author read

present the output to the user
call out unmerged branches first
list existing worktrees as cleanup candidates
state plainly if nothing is stranded

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.