Encodes GitHub issue authoring conventions including present-progressive titles and problem-space bodies that communicate inside-out as why, how, and what, with completion criteria read off the documented problem. Must be loaded before composing any issue title or body, or revising an existing issue, whether drafting…
Encodes PR authoring conventions including imperative titles with repository-capability verbs, motivation-focused descriptions, hidden context surfacing, and prose flow guidelines. Must be loaded before composing any pull request title or description, whether drafting interactively or creating programmatically with gh…
Writes commit messages following Go team conventions for both Go packages and supporting files (docs, configs, CI, tooling) in Go-centric codebases (go.mod present or known from context).
Plans a fine-grained sequence of atomic, incremental commits for a non-trivial changeset before any code is written or any commit message is drafted. Language-agnostic; defers commit-message authoring to a separate skill.
Sets the maintainer's standard for committed Go tests (test.go): what earns a commit, how a suite is shaped, named, and commented, and how to review one. Carries the golden hierarchy of contract authority, go-doc-first design and review, annotated Go-team snippets to imitate, and one reference file per scenario.
5 7d agoA68 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: