handlename
@handlename
Public Skills
setup-tagpr
by handlename
Set up tagpr for automated release management in a repository. tagpr automatically creates and updates pull requests for unreleased items, tags them when merged, and creates GitHub Releases. Use this skill when users want to (1) introduce tagpr to their repository, (2) set up automated releases with tagpr, (3) configure tagpr with goreleaser for Go projects, (4) enable immutable releases with tagpr, or (5) set up release workflow for TypeScript/Node.js projects.
go1.27-changes
by handlename
Reference for what changed in Go 1.27 — use when writing or reviewing Go code in a go 1.27+ module so you do not fall back on pre-1.27 training-data assumptions. Covers new language features (generic methods), new and changed standard-library APIs (encoding/json/v2, uuid, crypto/mldsa, strings.CutLast, …), and dangerous behavior changes (time channels now unbuffered, net UnixConn returning raw io.EOF, go tool trace -http binding localhost-only). Triggers include "go 1.27", "golang 1.27", "go1.27", "1.27 の変更点", "Go 1.27 で開発", "is this valid in go 1.27".
multirepo
by handlename
Investigate or edit multiple local git repositories in parallel. Fires when a message contains a multirepo: <repo1>, <repo2>, ... declaration. The main session acts as an orchestrator: it assigns one dedicated sub-agent (multirepo-worker) per repo, handles dispatch and result aggregation only, and never touches code itself. Worktrees are created for edits only; commits and PRs are left to other skills.
github-resource-access
by handlename
Use when accessing GitHub resources such as issues, PRs, repositories, or secrets. Enforces "use the gh CLI; reads are free, writes require explicit instruction".
maint-glossary
by handlename
Use when creating or maintaining a glossary of domain terms from a requirements document, spec, or codebase. Triggers include "create a glossary", "define terms", "extract domain vocabulary", or "update the glossary" after the source document or domain evolves.
mermaid-to-svg
by handlename
Turn a mermaid diagram into a hand-drawn free-layout SVG image file and return its path. Pure and offline — it draws an SVG following GitHub Primer-ish style rules but does NOT render via mermaid-cli, upload anything, or embed the result. Designed to be called from other skills (e.g. plan-to-issue, create-pr) through a subagent whose only return value is the SVG file path on success or a failure reason on failure, then paired with github-attachment-upload to publish it. Use when a mermaid diagram should be presented as a freely laid out image. Triggers include "mermaidを自由レイアウトのSVGにして", "hand-draw this mermaid as an SVG", "generate a free-layout SVG for this mermaid".
create-pr
by handlename
Create a Pull Request from the current branch to a base branch, using GitHub CLI to generate a suitable title and description from the commit history.
draw-mermaid
by handlename
Draw a mermaid diagram from a natural-language intent and return a syntax-validated mermaid source, verifying it with mermaid.parse() against a vendored, version-pinned mermaid.js driven by playwright-cli. Designed to be called from other skills (e.g. plan-to-issue, create-pr) through a subagent whose only return value is the validated mermaid on success or a failure reason on failure. Use whenever a mermaid diagram must be produced with a guarantee that it parses without syntax errors. Triggers include "mermaidで図を描いて構文チェックまでして", "draw a mermaid diagram and make sure it has no syntax errors", "syntax-checked mermaid".
github-attachment-upload
by handlename
Upload an arbitrary local file to GitHub user-attachments by driving a real browser with playwright-cli against an issue editor, then return the attachment URL. File-type agnostic — works for SVG, PNG, screenshots, or any file GitHub's editor accepts; it does not create an issue or comment. Designed to be called from other skills (e.g. plan-to-issue, create-pr) through a subagent whose only return value is the URL on success or a failure reason on failure. Use when a local file must become a GitHub user-attachments URL. Triggers include "このファイルをGitHubのuser-attachmentsに上げてURLをちょうだい", "upload this file to GitHub user-attachments", "get me an attachment URL for this image".
plan-to-issue
by handlename
Use when an implementation plan or design has been finalized in the session and the user wants to record it on GitHub. Either creates a tracking issue (overview + PR-granularity checklist with TASK- IDs) plus a self-contained detailed comment, or — when a related issue already exists (e.g. the plan revises a plan previously posted there) — posts the plan as a self-contained comment on that existing issue, superseding the previous plan comment. Triggers include "issue化して", "計画をissueにして", "turn this plan into an issue", "create a tracking issue for this", "既存のissueにコメントとして投稿して", "計画を issue #N に投稿して".
commit-it
by handlename
Commit changes following the Conventional Commits specification, verifying test passage first. Supports both git and Jujutsu (jj) repositories.
persona-mimic-trainer
by handlename
Train and iteratively refine a custom sub-agent that mimics a specific person's decision-making criteria, cognitive biases, and communication style for mock wall-hitting (pre-communication verification).