gh

Delegate to this agent to address pull request review comments; it evaluates each comment, makes targeted fixes, ensures test coverage, and commits changes with descriptive messages.

GitHub Actions specialist focused on secure CI/CD workflows, action pinning to full commit SHAs, OIDC authentication, least-privilege permissions, and supply-chain security. Delegate workflow authoring and security hardening to this agent.

Delegate to this agent to bootstrap, configure, or audit a GitHub repository's engineering conventions — git hooks, changelog, conventional commits, CI/CD workflows, PR/release flow, and repo-level settings (branch protection, CODEOWNERS, security). It surveys the repo, reports config gaps with severity, and applies fixes by delegating to the gh plugin's skills.

DevOps specialist for CI/CD pipelines, deployment debugging, and GitOps workflows focused on making deployments boring and reliable. Use this agent to triage pipeline failures, harden security, and implement monitoring.

GitHub Actions CI/CD for Go projects. Use when writing or reviewing GitHub Actions workflows that build, test, lint, or release Go code — including actions/setup-go configuration, Go version matrix, dependency caching, go.mod/go.work version files, artifact uploads, and monorepo cache strategies. Also trigger when the user asks about CI for Go, GitHub Actions Go templates, or how to test Go on multiple versions in CI.

Changelog entry creation with Changie. Use when writing a changelog entry, adding a new change fragment, recording what shipped, or following the Keep a Changelog format. Covers non-interactive usage, entry quality rules, issue linking, and fragment file naming.

Provides guidance on writing commit messages using the Conventional Commits specification. Trigger this skill when writing commit messages, generating changelogs, or when the user asks about commit message formatting, conventional commits, semantic versioning based on commits, or needs to categorize a change (e.g., feat vs fix vs chore).

Post-ship documentation update. Use after shipping a feature or at session end to ensure README, ARCHITECTURE, CONTRIBUTING, CLAUDE.md, CHANGELOG, TODOS, and VERSION are accurate and up to date. Trigger phrases: "update the docs to match what shipped", "docs are stale after my changes", "README is outdated", "CHANGELOG needs polish", "review project docs before finishing", "check all docs are consistent".

Manage Git hooks with husky v9. Use when the user asks about git hooks setup, pre-commit hooks, commit-msg hooks, husky configuration, the prepare script, or CI integration for git hooks. Trigger on mentions of 'husky', '.husky/', 'prepare script', or git hook lifecycle management.