Draft single-line commit-message options for the currently staged changes (best first), have the user pick one via AskUserQuestion, then run `git commit -m "<selection>"`. TRIGGER when the user asks for "options"/"choices" for a commit, for "numbered"/"one-liner" commit messages for staged changes, or otherwise asks Claude to draft and commit staged changes in one shot. ALSO TRIGGER when the user accepts a `[c]ommit` follow-up that Claude offered (replies `c`, `cm`, `commit`, or 🚢 mapped to such an option); the accepted offer counts as a request for options, never auto-pick a subject and `git commit -m` directly. SKIP when nothing is staged, when the user is asking only for drafts without committing, or when the user wants a multi-line body (this skill is subject-only).
Compose a short, descriptive session title for the `/rename` built-in and copy a ready-to-paste `/rename <title>` to the clipboard with `pbcopy`. The title is a brief plain-language description (not a slug), and a relevant PR is appended when one exists. TRIGGER when the user's whole message is exactly `ren`, when they invoke `/ren` or `/rename-session`, ask for a "name"/"title" for the session, ask to "name the session", or want a `/rename` line drafted for the current work. SKIP when the user wants to rename to a fixed prune marker like `del` (that is the literal `/rename del`, no drafting needed), or is asking about the `/rename` built-in itself rather than a name for this session.
Ferry a worktree's working-tree changes into the root (main checkout) so they can be sourced or run live at the installed path (dotfile edits the rest of the system reads from `~/.dot-star`, which symlinks to root). Worktree stays on disk so `/commit` and `wtd` still happen there after `/untry`. TRIGGER when cwd is inside `*/worktrees/*` and the user invokes `/try`, says "try this in root", "test these live", "move it to root for testing", or otherwise signals they want to exercise worktree edits at the root path. SKIP when cwd is the root checkout itself, when the worktree has no working-tree changes (`git status --porcelain` empty), or when a `/try` is already active for this worktree (a `try:wt-source:<name>` entry exists in `git stash list`).
Promote a saved memory from soft (text Claude must remember to apply) to hard (a hook, `settings.json` entry, `CLAUDE_*.md` line, shell alias, or skill that fires automatically). Propose 2-3 candidate target shapes that fit the memory, pick one via `AskUserQuestion`, then write the change. TRIGGER when the user's whole message is exactly `codify` or `/codify` (optionally followed by a memory slug); ALSO offer it as a single follow-up sentence immediately after you save a new memory file, but only if the memory expresses a behavioral rule (feedback/project type with a clear "do X" or "when Y, do Z"). SKIP for pure user/reference facts with nothing to enforce, for fluid rules the user is still trying out, or when the target shape would duplicate existing config.
Land a worktree's commits back into the default branch in the main checkout and remove the worktree. TRIGGER when cwd is inside `*/worktrees/*` and the user signals work is done (e.g. "ship it", "land it", "merge it back", "clean up the worktree", "wrap this up"). SKIP when not in a worktree, when there are uncommitted changes the user has not addressed, or when the user is mid-task.
Promote a worktree's commits onto the default branch in the main checkout, leaving the worktree and branch in place to keep working. TRIGGER when cwd is inside `*/worktrees/*` and the user signals they want their commits on the default branch without wrapping up (e.g. "promote", "promote to master", "push these up but keep the worktree"), or accepts a `[p]romote` follow-up. SKIP when not in a worktree, when there are uncommitted changes the user has not addressed, or when the user wants to tear the worktree down (that is `worktree-done`).
Reverse a `/try`: capture root's now-possibly-tweaked tested state and put it back into the worktree, restoring root's pre-`/try` edits if any were saved aside. After `/untry` the worktree holds the (possibly tweaked) tested state and root looks the way it did before `/try`, so `/commit` and `wtd` happen in the worktree as usual. TRIGGER when cwd is inside `*/worktrees/*` and the user invokes `/untry`, says "put it back", "move it back to the worktree", "done testing", or otherwise signals they want to undo a `/try`. SKIP when no `/try` is active for this worktree (no `try:wt-source:<name>` entry in `git stash list`), or when the worktree has unrelated uncommitted edits that would conflict with the tested state coming back.