agentsclimarketplace

Bye

Skill lklimek/claudius/skills/bye

Plugin with opinionated set of Claude Code agents nad skills

Install
npx -y skills add lklimek/claudius --skill bye

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

  • 1 stars1 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.

What its author says it does

Copied from the file, not written here

This skill should be used when the user says "bye", "wrap up", "tear down", "we're done", or otherwise ends the session. It shuts down spawned teammates and agents, removes their worktrees, and reconciles uncommitted or unpushed session work.

SKILL.md

1.4 KB, as published. Nobody here has run it

bye

  1. Shut down every teammate/background agent spawned this session (per grand-admiral shutdown discipline — never TaskStop a named teammate).
  2. For each worktree created this session: check git status/git log vs its base. Fully merged and clean → git worktree remove + delete its branch. Anything uncommitted or unmerged → do NOT delete; handle per step 3.
  3. Sweep every repo/worktree touched or created this session (main cwd(s) plus anything from step 2) for uncommitted changes or unpushed commits. For each:
    • Correct action obvious (e.g. finish a trivial commit, merge an already-reviewed branch) → do it.
    • Otherwise → escalate to the user: what's dangling, where, your recommendation. Never guess on anything destructive or ambiguous.
  4. In the main session checkout(s), once step 3 is clean (no uncommitted/unpushed work left unresolved): git fetch then git pull --no-rebase to bring the checked-out branch up to date with origin. Skip a checkout still holding escalated work — don't pull over it.
  5. Report a final summary: what was torn down, what was fixed, what's escalated.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.