claude-code-plugins

Restore claude/codex agents from a tmux-reboot snapshot after tmux-resurrect reopens their windows.

Snapshot running tmux claude/codex agents immediately before a reboot so their sessions can be restored afterward.

Commit changes, run git-test precommit checks, and fix failures. Use when asked to fix build, test, lint, typecheck, or precommit failures.

Running precommit checks and build validation. ALWAYS use after ANY code changes.

This skill should be used after completing any task, before returning control to the user. Always run this skill — it handles the case where there's nothing to do.

Coordination guidelines for leading a team of task-executing agents

Workflow guidelines for team members executing tasks

Work with markdown-based task lists in .llm/todo.md files. Use when managing tasks, working with todo lists, extracting incomplete tasks, marking tasks complete, or implementing tasks from a task list.

Work through all incomplete tasks in .llm/todo.md with one subagent and commit per task, continuing past blocked tasks.

Find and implement the next incomplete task from .llm/todo.md.

Import a plan markdown file into .llm/todo.md as self-contained implementation tasks.

Convert a planning discussion into self-contained tasks in .llm/todo.md.

Find TODO comments in the codebase and add them to .llm/todo.md as tasks.

Run tests across all commits and loop on failures until all pass. Use when asked to run or fix test-all for a branch.

Test every commit in the current branch, fix failures, create fixup commits, and repeat until all commits pass.

Configure git-test for the current repository. Use when git test is missing or the user asks to set up branch testing.

Remove git worktrees safely without force.

Split local changes into multiple logical commits. Use when the user asks to commit changes in chunks.

Commit local changes with careful staging and single-line messages. Use for all git commit operations.

Resolve git merge or rebase conflicts and continue the operation.

Rebase all local branches onto the configured upstream branch.

Rebase local commits on the configured upstream using the plugin rebase script.

Rewrite in-scope commit messages to single-line git-workflow messages with git history reword.

Split the current branch into multiple branches with one commit each.

Commit message format and git workflow rules. ALWAYS use this skill for every git commit — no exceptions — and whenever rewording an existing commit message.

Create a git worktree in a peer directory using the plugin worktree script.

Debug and fix failing GitHub Actions checks for the current commit. Use when asked to fix CI, GHA, or GitHub Actions failures.

Add a self-contained task to .llm/todo.md. Use when the user asks to add one task or append work to the markdown task list.

Guidelines for working with LLM context stored in the .llm/ directory.

Coordinates other skills and agents. ALWAYS use this skill on startup.

Start or restart a project dev server on a specific or discovered port, wait until it is ready, and monitor it for automatic recovery. Use when the user asks to start, restart, keep alive, watch, or monitor a development server.

Keep code comments concise and durable, or clean redundant comments without changing code behavior. Use when adding, editing, reviewing, or removing comments; after code changes; before committing; or when asked to clean comments in a diff or across the repository.

Write test assertions as complete, strict deep-equality checks, and hold existing tests to the same standard. Use when writing new tests, adding assertions, reviewing test quality, strengthening weak tests, or replacing fragmented assertions in a file, directory, diff, or repository.

Run on /wip or for a whole-repository cleanup spanning multiple worktrees and branches. Trigger when the request combines operations such as removing stale worktrees, rebasing all branches, retesting, and pushing, including "clean up my worktrees and branches", "rebase all my branches and get them tested and pushed", or "settle my WIP". The workflow gates destructive and outward-facing actions, never uses --force, and handles worktree, rebase, and test edge cases. Defer to single-operation git skills when the user targets one specific branch or worktree. Wraps git:clean-worktrees and build:test-all.

Diagnose Liquibase change-log lock failures in Maven tests and remove only stale H2 database files from build output directories before rerunning the affected tests. Use when failures contain "Could not acquire change log lock", "Currently locked by", or `liquibase.exception.LockException`.

Dry-run configured OpenRewrite recipes, count and rank violations, and optionally run one selected recipe without committing. Use when asked to analyze OpenRewrite recipes, report rule violations, inspect a rewrite dry run, or compare which recipes would change the most files.

Apply every configured OpenRewrite recipe with violations on a dedicated branch, creating one commit per named leaf recipe and verifying the cumulative result. Use when asked to fix all OpenRewrite violations, create an OpenRewrite cleanup branch, or commit recipe changes separately.

MUST be loaded before creating, editing, or reviewing any SKILL.md, agent markdown, or command markdown file. Contains formatting rules that prevent common mistakes like numbered steps, which cause git churn, and privacy rules requiring generic placeholders instead of real personal data in examples. Also use when the user asks about instruction formatting best practices, header structure, or how to avoid unnecessary diffs.

Produce a single self-contained HTML report that explains a command-line investigation — the commands actually run, their real output, and just enough reasoning to teach it. Use when the user asks for a walkthrough, tutorial, write-up, teaching artifact, or "show me how you did that" of a shell debugging or exploration session.

Create a GitHub pull request the user's preferred way. Use whenever opening, creating, or raising a PR with gh.