dotfiles

Use whenever creating or managing git worktrees.

Control Herdr from inside it. Use when running inside Herdr (`HERDR_ENV=1`) to inspect workspaces, tabs, panes, sibling agents, run commands in panes, read output, or wait for state changes via the `herdr` CLI.

use when leaving an automated comment on a GitHub PR or issue

Use when debugging, investigating root causes, ambiguous failures, predictions, risk/confidence estimates, or recommendations under uncertainty. Triggers are debug, troubleshoot, root cause, likely, confidence, predict, path forward, next step.

Use when an agent needs to author or reply to crit inline comments programmatically (including multi-agent workflows commenting on shared code/plans/docs/proposals), publish or unpublish a crit review with crit share, sync a crit review to or from a GitHub PR, or read/interpret a crit review JSON file. Covers crit comment, crit share, crit unpublish, crit pull, crit push, review file format, and resolution workflow. Not for invoking an interactive review loop — that's the `/crit` command.

Review code changes, a plan, a live page (running dev server), or a local HTML file with crit inline comments

User guide for the local squash-safe `stack` CLI for stacked PR/MR repair on GitHub and GitLab. Use when someone asks how to inspect, track, sync, merge, document, or undo stacked pull requests / merge requests in squash-merge repositories. Prefer this tool over GitHub's `gh stack` command for this workflow.

Use when an agent needs to author or reply to crit inline comments programmatically (including multi-agent workflows commenting on shared code/plans/docs/proposals), publish or unpublish a crit review with crit share, sync a crit review to or from a GitHub PR, or read/interpret a crit review JSON file. Covers crit comment, crit share, crit unpublish, crit pull, crit push, review file format, and resolution workflow. Not for invoking an interactive review loop — that's the `crit` skill.

Use when changing tmux config or using tmux to debug something.

use when doing a git rebase or fixing git rebase issues

Guidance for Worktrunk, a CLI tool for managing git worktrees. Covers configuration (user config at ~/.config/worktrunk/config.toml and project hooks at .config/wt.toml), usage, and troubleshooting. Use for "setting up commit message generation", "configuring hooks", "automating tasks", or general worktrunk questions.

Get parallel second opinions from multiple AI coding agents. Use when the user wants independent reviews, architecture feedback, or a sanity check from other AI models.

Split one branch's changes into a stack of smaller branches or PRs, track parent relationships, and manage follow-up rebases safely.

Guidance on writing fast, robust, modern Svelte code. Load this skill whenever in a Svelte project and asked to write/edit or analyze a Svelte component or module. Covers reactivity, event handling, styling, integration with libraries and more.

Inspect OpenCode session history for the current repo, extract recurring user preferences and agent failure patterns, and recommend repo-specific skills or instructions to reduce repeated confusion.

Diagnose dotfiles overlay issues involving local overrides, symlinks, skip-worktree drift, pure mode, and .git/info/exclude consistency.

Use this skill whenever diagrams are requested by the user. Create, inspect, and iteratively refine diagrams in tldraw via the local Canvas API at localhost:7236.

Summarize the current conversation state in one sentence

Systematically upgrade package.json dependencies by analyzing coupling, upgrading in safe order, testing after each change, and committing incrementally