Loading the repository README…
Showing 24 of 24 collected skills.
Use for substantive explanations, comparisons, proposals, and multi-part answers in conversational chat; or when writing or substantially revising reader-facing prose outside the current conversation, including documentation, design documents, incident…
Use when receiving or addressing code review feedback about changes you made, including pasted reviewer comments, inline PR comments, requested changes, review summaries, questions, nits, or direct user critique that may require replies or revisions.
Use when creating, editing, validating, rendering, or debugging local CLI and TUI demo GIFs with asciinema+agg, Betamax, or VHS, including recorder selection, scripted terminal recordings, `.tape` files, captions, keyboard overlays, waits, pacing, and…
Use when creating, updating, or testing agent-facing guidance, including skills, AGENTS.md, CLAUDE.md, and references linked from them; deciding when guidance should be reached or applied; repairing unclear triggers, pointers, or observed misbehavior;…
Use when writing or editing prose other than ordinary conversational chat, including formatting-only edits, or when the user requests source-style prose in chat.
Use when performing Git repository operations involving commits, amendments, fixups, branch creation or movement, stacked branches, pushes, pull request creation, metadata updates, merges, review submission, publishing, or recovery from raw Git usage.…
Use when deciding what test evidence a code change needs, or when writing, changing, deleting, or reviewing tests or their supporting infrastructure. Do not use merely to explain an existing test result or compiler error when no code, test, or validation…
Use when writing, changing, reviewing, testing, debugging, or explaining Go code; working with Go modules, tool dependencies, or dependency source; or choosing Go language and standard-library APIs. Do not use when Go is only incidental context and no…
Use when designing, changing, or evaluating code ownership, boundaries, contracts, representations, dependency lifetimes, domain adapters, public API shapes, or where policy and state live, including while adding code or refactoring. Do not use for a local…
Use when drafting, revising, reviewing, or evaluating a commit message, pull request title or description, or source text intended to become or supply a commit message or pull request metadata. Do not use for ordinary change explanations, changelogs, release…
Use when the user requests a subagent quorum, independent design proposals, panel-based synthesis, or a multi-agent tie-break between defined alternatives. Do not use for ordinary delegation, parallel fact gathering, implementation splitting, or a choice that…
Use when the user wants help understanding a code change and deciding where to focus their own review of a pull request, commit, or diff.
Use when writing, changing, organizing, or reviewing non-generated code; evaluating how readily a maintainer can understand and safely change it; or deciding source order, naming, control flow, locality, physical organization, or whether a boundary reduces…
Use when the user explicitly requests a Pikchr diagram, Pikchr source, a `.pikchr` file, or SVG rendered with Pikchr. Do not use for a general diagram request that does not select Pikchr as the format.
Use when writing, reviewing, revising, or deciding whether to add or remove code comments or in-code documentation; when introducing or changing domain concepts, non-obvious contracts, invariants, or representation boundaries; or when code's local model is…
Create, revise, review, or decide whether to create Architecture Decision Records (ADRs) and decision logs. Use when a significant technical decision needs durable rationale for future maintainers or agents, or when an existing ADR must inform a current…
Use when designing or changing a command-line interface, including commands, flags, output streams, structured output, exit status, or the boundary between command adapters and application behavior. Do not use merely to invoke an existing command.
Use when drafting, revising, evaluating, reviewing, or applying a commit message; or when committing work, amending commits, creating fixup commits, creating branches as part of committing work, stacking work, inserting prerequisite work below the current…
Use when planning, creating, revising, or reviewing an explanatory 2D diagram's viewer task, visual argument, visual vocabulary, spatial layout, or semantic correctness, including when another diagram skill requires it. Pair it with medium-specific guidance…
Use when the agent is responsible for performing a code review of a diff, commit, pull request, or code change and producing findings about behavior, design, readability, documentation, or reviewability. Do not use when responding to feedback on the agent's…
Use when a diagram must be readable as plain text, including when the user requests text characters or the destination is a plain-text artifact such as Markdown, a commit message, or terminal output. Plain-text diagrams can also be used in chat when they suit…
Use when creating pull requests, updating pull request branches, pushing or publishing work for review, applying pull request metadata, or submitting stacked branches. Do not use for drafting or reviewing pull request metadata without a pull request…
Use when acquiring, using, inspecting, or returning temporary pooled Git worktrees with the `treehouse` CLI for isolated task work, delegated subagent work, or cleanup of leased treehouse worktree paths.
Use when deciding whether a repository change needs a changelog entry, creating or updating Changie unreleased entries, choosing the correct changelog kind, or writing user-facing changelog body text in repositories that use `.changie.yaml`.
Copy this prompt into the AI assistant you're using.
Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/abhinav/home.The repository README could not be loaded. You can still explore its Skills below.