メニュー
Git + GitHub umbrella. Hard rule - never use gh api graphql without double-confirming, REST is default. Owns the full PR lifecycle (branch, commit, open, monitor CI, auto-fix, merge) and routes to ward-passthrough and git-workflow siblings.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Kai's "start a sidequest" command - file a Forgejo issue from a described piece of work, then dispatch it through ward into its own session.
Tier and prune an issue backlog - P0-P4 tier definitions (P4 is the icebox/lowest tier), a target distribution as ranges, percentile-cut assignment that lands within the bands, pruning, and a second orthogonal automation-mode axis (headless/interactive/consult). Triggers - prioritize, prioritization, triage the backlog, P0/P1/P2/P3/P4, backlog ratio, icebox, burn down the backlog, tier the issues, automation mode, eligibility to dispatch.
gpg-ssm is a GPG wrapper that pulls signing material from AWS SSM at sign time instead of caching on disk. Use when wiring up a fresh machine for signed commits, bootstrapping the shared signing key, rotating a key, or debugging signing failures. Triggers - gpg-ssm, gpg signing, signed commits.
git workflow, forgejo, default tracker, commit, push, PR, gh, fj, issue, todo, gish.
Kai's technical preferences - Go CLI defaults (urfave/cli), Charm TUI stack, dead-repo check, doc conventions, default license. Triggers - cli, tui, library, dependency, recommend tool.
The five-tier information model for agent-facing CLI commands - description, body, intro, help, outro - plus push-short/pull-long. Use when documenting a CLI agents invoke, not humans.
| name | coding-git |
| description | Git + GitHub umbrella. Hard rule - never use gh api graphql without double-confirming, REST is default. Owns the full PR lifecycle (branch, commit, open, monitor CI, auto-fix, merge) and routes to ward-passthrough and git-workflow siblings. |
| seed | {"kind":"always"} |
Umbrella skill for any work that touches git or GitHub. Owns the broad keyword surface, carries the hard rules that apply to every GitHub touch, holds the full pull-request lifecycle inline, and routes to the focused siblings for ward passthrough and the coilysiren/* commit rules.
git, github, gh, gh cli, gh api, octokit, graphql, repo, repository, pull request, PR, issue, fork, branch, commit, push, workflow, action, release, tag, label.
Never reach for the GitHub GraphQL API (gh api graphql, octokit.graphql, raw POSTs to /graphql, etc.) without double-confirming with Kai first. State that the proposed approach uses GraphQL, name a REST alternative if one exists, and wait for an explicit go-ahead before running or writing the call.
Applies to one-off commands, scripts, workflows, skills, and any code Kai will run.
Why: GraphQL rate limits have burned three days of Kai's time. The recovery is slow and annoying, and the burn is silent until limits hit.
How to apply: default to REST (gh api /repos/..., search endpoints, list endpoints) and accept the extra round-trips. REST rate limits are far more forgiving and the failure mode is per-call, not per-account.
Each step shows the gh way first, then the git + curl fallback for machines without gh. Detect which to use once up front (gh auth status succeeds -> gh, else extract owner/repo from the remote and use a token for REST calls).
gh (audit-log binding, scope routing) - ward-ops-gh-meta (in ward).coilysiren/* repos (commit-to-main default, every-commit-closes-an-issue rule, readonly exceptions) - kai-git-workflow.owner/repo#N refs and issue URLs.coding-github, before the PR-workflow merge and rename to coding-git).