repokit

Configure a GitHub repository through the gh CLI, in three explicit modes:

• about. Infer a one-line About description and a focused set of topics from the repo's own contents (README, manifest, code), show them against whatever is already set, and apply what you approve.
• labels. Provision the workflow labels: the lifecycle and priority sets issuekit uses to track work and rank it, and the automation label that asks a repo's AI review tooling to look at a PR. Create what's missing, reconcile what drifted.
• setup. Bring an already-created repo up to convention in one span: apply the house repo settings (merge-commit-only, delete-branch-on-merge), scaffold the baseline files (LICENSE by an asked question, README, .gitignore, AGENTS.md), then run about and labels on top. It configures; gh repo create stays with the user.

Three jobs, one skill, because all three answer "make this repo's GitHub configuration right": the outward-facing blurb people read, the label vocabulary the issue workflow runs on, and the settings-and-files baseline a new repo starts from.

When this fires

The user wants to configure a repo on GitHub. Route to a mode from what they ask:

• about. "Set the repo description", "add topics", "write an About blurb", "tag this repo", "update the repo's About".
• labels. "Provision the workflow labels", "set up this repo's labels", "add the issuekit labels", "add priority labels", "add an ai-review label", "the blocked label is missing".
• setup. "Set up this new repo", "configure this repo", "make this repo match my conventions", or a vague "set up this repo" / "configure repo metadata" — setup is the umbrella, and it subsumes the old "offer about then labels" answer.

If no mode is clear, ask first. Present the three modes and let the user pick before touching anything.