How do I install the Close Story skill?

Run npx skillmds@latest add astropham1808/close-story in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Close Story safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Close Story?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Close Story free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Close Story?

astropham1808 (@astropham1808) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Close Story by astropham1808 — Agent Skill

Name: Close Story
Author: astropham1808

Close Story

Safely clean up a story worktree and branch after its pull request has been reviewed and merged. Use this skill whenever the user asks to close, clean up, or tear down a finished story (AL-xxx, HB-xxx, or any PREFIX-nnn ID), says "PR merged rồi", "dọn worktree", "clean up the branch", "remove the worktree", "xong task này rồi", or asks whether a story is safe to delete. Handles codex/ID, worktree-ID, claude/ID, and explicit custom branch or worktree names. Never use before the human merge gate.

astropham1808 Updated Sep 17, 2026

File contents

Close Story Worktree

Clean up a merged story in a strict order. Keep this skill limited to GitHub merge verification and local Git cleanup.

Required inputs

Resolve these before changing state:

story ID;
repository root;
exact head branch;
exact worktree path;
PR URL or number;
base branch.

Read the applicable CLAUDE.md (and AGENTS.md when the project keeps one for Codex). Preserve unrelated worktrees and branches. Accept branch forms such as codex/AL-151, worktree-AL-161, or claude/AL-216; never rewrite one naming convention into another.

Sequence

Inspect git status --short --branch and git worktree list --porcelain.
Use gh pr view or the GitHub connector to confirm the exact PR has mergedAt set and targets the expected base branch.
If the PR is open, draft, closed without merge, or ambiguous, stop. Return the PR URL and leave the worktree and branch unchanged.
Require the story worktree to be clean. Never reset, clean, stash, or force removal to make it appear clean.
Run scripts/cleanup-merged-story.sh without --apply to preview the exact targets and safety checks.
Run the same command with --apply only when the user has placed cleanup in scope. The script fetches the PR base, verifies the branch tip is an ancestor of the updated base, removes the exact worktree without force, then uses git branch -d.
Confirm the path no longer appears in git worktree list --porcelain and the local branch no longer exists.
Report the merged PR, removed worktree, deleted local branch, and any intentionally retained remote branch.

Safety rules

Never merge the PR. The human reviews and merges.
Never run cleanup based only on a story ID guess.
Never use git worktree remove --force, git branch -D, git reset, git clean, or a recursive filesystem deletion.
Never remove the primary worktree, repository root, or a dirty worktree.
Keep source-tracker completion in a separate workflow.
If a squash merge makes the branch tip not ancestral to the base, stop before removal. Ask the user whether to retain the branch or authorize a separate recoverability plan.
Do not delete the remote branch unless the user explicitly requests it.

Cleanup command

Run from the primary worktree. Requires gh and an authenticated gh auth status.

Preview:

"${CLAUDE_SKILL_DIR}/scripts/cleanup-merged-story.sh" AL-151 codex/AL-151

Apply with an explicit worktree when useful:

"${CLAUDE_SKILL_DIR}/scripts/cleanup-merged-story.sh" AL-151 codex/AL-151 \
  --worktree /absolute/path/to/worktree --apply

The script verifies merge state and targets in both modes.

Pairs with start-story-multi-agent, which opens the story worktree this skill closes. That flow ends at the human PR gate; this one starts after the merge.

---name: close-storydescription: Safely clean up a story worktree and branch after its pull request has been reviewed and merged. Use this skill whenever the user asks to close, clean up, or tear down a finished story (AL-xxx, HB-xxx, or any PREFIX-nnn ID), says "PR merged rồi", "dọn worktree", "clean up the branch", "remove the worktree", "xong task này rồi", or asks whether a story is safe to delete. Handles codex/ID, worktree-ID, claude/ID, and explicit custom branch or worktree names. Never use before the human merge gate.---# Close Story WorktreeClean up a merged story in a strict order. Keep this skill limited to GitHubmerge verification and local Git cleanup.## Required inputsResolve these before changing state:- story ID;- repository root;- exact head branch;- exact worktree path;- PR URL or number;- base branch.Read the applicable `CLAUDE.md` (and `AGENTS.md` when the project keeps one forCodex). Preserve unrelated worktrees and branches. Accept branch forms such as`codex/AL-151`, `worktree-AL-161`, or `claude/AL-216`; never rewrite one namingconvention into another.## Sequence1. Inspect `git status --short --branch` and `git worktree list --porcelain`.2. Use `gh pr view` or the GitHub connector to confirm the exact PR has `mergedAt` set and targets the expected base branch.3. If the PR is open, draft, closed without merge, or ambiguous, stop. Return the PR URL and leave the worktree and branch unchanged.4. Require the story worktree to be clean. Never reset, clean, stash, or force removal to make it appear clean.5. Run `scripts/cleanup-merged-story.sh` without `--apply` to preview the exact targets and safety checks.6. Run the same command with `--apply` only when the user has placed cleanup in scope. The script fetches the PR base, verifies the branch tip is an ancestor of the updated base, removes the exact worktree without force, then uses `git branch -d`.7. Confirm the path no longer appears in `git worktree list --porcelain` and the local branch no longer exists.8. Report the merged PR, removed worktree, deleted local branch, and any intentionally retained remote branch.## Safety rules- Never merge the PR. The human reviews and merges.- Never run cleanup based only on a story ID guess.- Never use `git worktree remove --force`, `git branch -D`, `git reset`, `git clean`, or a recursive filesystem deletion.- Never remove the primary worktree, repository root, or a dirty worktree.- Keep source-tracker completion in a separate workflow.- If a squash merge makes the branch tip not ancestral to the base, stop before removal. Ask the user whether to retain the branch or authorize a separate recoverability plan.- Do not delete the remote branch unless the user explicitly requests it.## Cleanup commandRun from the primary worktree. Requires `gh` and an authenticated`gh auth status`.Preview:~~~bash"${CLAUDE_SKILL_DIR}/scripts/cleanup-merged-story.sh" AL-151 codex/AL-151~~~Apply with an explicit worktree when useful:~~~bash"${CLAUDE_SKILL_DIR}/scripts/cleanup-merged-story.sh" AL-151 codex/AL-151 \ --worktree /absolute/path/to/worktree --apply~~~The script verifies merge state and targets in both modes.## RelatedPairs with `start-story-multi-agent`, which opens the story worktree this skillcloses. That flow ends at the human PR gate; this one starts after the merge.

Frequently asked questions