dotfiles

Use when starting feature work that needs isolation from current workspace, before executing implementation plans, or when reviewing an existing branch (e.g. a PR) without switching away from the current branch. It creates isolated git worktrees under `.worktrees/`.

Use this skill when working on terminal UI rendering, interactive CLI prompts, ANSI color output, terminal screenshots, Bubble Tea/Lip Gloss/Huh/Glamour, curses-style apps, or CLI tests that depend on TTY behavior.

Use this skill when you're working with golang code.

Use whenever asked to create GitHub Pull Request.

Use when writing, rewriting, or updating a pull request description. Use this skill's explicit PR template unless the user provides a different template for the current task, keep the result concise and human-readable, explain why the change exists, and ask the user for motivation before updating the PR when the user has not explicitly provided it.

Use this skill whenever writing, editing, reviewing, or deciding whether to add code comments, docstrings, inline comments, or internal function documentation in any programming language. Use it even when the task only mentions "comments", "docs in code", "docstrings", "document this function", or "explain this helper".

Use this skill whenever you need to write or rewrite technical documentation: README sections, runbooks, design notes, API docs, onboarding docs, troubleshooting guides, or other prose documentation outside source code. Use it when the documentation must be both technically correct and easy to read, especially if the draft is becoming vague, academic, or hard to scan.

Use when receiving feedback or after a code review, before implementing suggestions, especially if feedback seems unclear or technically questionable.

Test-driven development with red-green-refactor loop. Use when user wants to: - build features or fix bugs using TDD - mentions "red-green-refactor" - wants integration tests - or asks for test-first development

Master Bash Automated Testing System (Bats) for production shell and CLI testing. Use this skill whenever writing or reviewing Bats tests, shell command tests, CLI integration tests, fixture-heavy tests, Docker-backed Bats suites, or unit/e2e test split patterns for shell utilities.

Use this skill when you're working with shell scripts (bash, sh). Covers script structure, formatting (shfmt), linting (shellcheck), argument parsing, help messages, embedded awk/jq/yq transformations, error handling, and security.

Use this skill when writing or formatting Markdown files. For instance, when writing or modyfing a SKILL.md file, or documenting README.md.

Comprehensive PR review using specialized agents. Use when asked to review a pull request, check code quality before merging, or run any subset of review aspects (code, tests, errors, types, docs, simplify).

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "add/install/remove an X skill", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

Execute git commit with interactive confirmation. Use when user asks to commit changes, create a git commit, or mentions "/commit".

Post PR review findings as a GitHub pending review via the API. Use after completing a PR review when the user wants to publish findings to GitHub. Reads the most recent review from $XDG_DATA_HOME/agents/pr-review/.

Audit PR review threads to ensure all reviewer comments are properly addressed. Use this skill when the user wants to verify PR comments are handled, audit review threads, check if suggestions were applied, resolve/unresolve threads based on code changes, or ensure nothing was missed before merging. Also trigger when the user says things like "check the PR comments", "are all comments addressed", "audit the review", "resolve handled comments", or "close out review threads".

Re-review a PR after fixes have been pushed. Use for a second pass, follow-up review, re-check after addressing comments, or any time you want to look again at a PR that was previously reviewed. Checks which reported issues have been addressed, runs a fresh unbiased review, and filters out noise from already-tracked or already-resolved GitHub threads. Trigger on: "re-review", "second pass", "review again", "check if issues were fixed", "follow-up review", "look again after fixes".

Clone and analyze Git repositories to find specific information. Use this skill whenever the user wants to investigate a GitHub/GitLab/Git repository, analyze code from a remote repo, find specific information in a codebase by URL, clone and examine a project, or understand how something works in an external repository. Handles both public and private repos (using user's git credentials), manages a standardized clone location, and delegates analysis to a subagent.

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Use this skill when writing or modifying Go tests, benchmarks, or test helpers. Covers test style, modern testing APIs, and common mistakes.

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs. Requires running verification commands and confirming output before making any success claims. Evidence before assertions, always.

Use this skill when addressing GitHub PR comments.

Use this skill when writing or editing Go doc comments. Covers doc comment style, doc links ([pkg.Name] syntax), headings, lists, code blocks, and common formatting mistakes.

Extract clean markdown content from web pages, removing clutter and navigation to save tokens. Use instead of WebFetch when the user provides a URL to read or analyze, for online documentation, articles, blog posts, or any standard web page.

Use this skill when you're working with CSS.