actions-goGitHub Actions CI for Go: workflows that build, test, lint or release Go code with actions/setup-go, including go.mod/go.work version files, version matrices, module and build caching, multi-module repositories, test artifacts, and runners without github.com access. Use when writing or reviewing a G
actionsGitHub 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 with this skill.
address-commentsUse when asked to address pull request review comments; it evaluates each comment, makes targeted fixes with test coverage, reports a disposition per comment, and commits only when authorized.
changieChangelog fragments with Changie. Use when writing a changelog entry, adding a change fragment under `.changes/`, recording what shipped, or checking that fragments follow the project's `.changie.yaml` (kinds, length cap) and Keep a Changelog voice. Covers non-interactive `changie new`, shell-safe b
configure-repoUse when asked 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, an
conventional-commitsProvides 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
debug-deliveryDevOps specialist for CI/CD pipelines, deployment debugging, and GitOps workflows focused on making deployments boring and reliable. Use this skill to triage pipeline failures, harden security, and implement monitoring.
document-releasePost-ship documentation check: compare the branch diff with every project doc (README, architecture, contributing, agent instructions, changelog, TODOs, VERSION), fix factual drift, and report a health summary per file. Use after shipping a feature or when docs may be stale. Commits, pushes or PR ed
huskyHusky v9 Git hooks: set up or fix `.husky/` hooks, the `prepare` script, lint-staged or commitlint hooks, CI and production installs, and hooks that fail or do not run. Use when the repository has `.husky/` or the user mentions Husky. A `package.json` alone does not mean Husky; for `lefthook.yml` or
lefthookLefthook Git hooks: write or fix `lefthook.yml` jobs (globs, staged files, parallel or piped runs, re-staging fixes), install hooks locally and in CI, and migrate from Husky. Use when the repository has `lefthook.yml` or the user asks for lefthook or which hook manager to choose. For an existing `.h
pre-commitpre-commit framework (`.pre-commit-config.yaml`): add or update hooks, pin and refresh hook revisions, install it with the project's own tooling (pixi, uv, pipx or pip) and run it in CI. Use when the repository has `.pre-commit-config.yaml`, including Node or Go projects, or the user asks for pre-co
send-prCommit the pending changes, push a feature branch and open a GitHub pull request with a conventional-commit title, a structured body and requested reviewers. Use when the user asks to "ship", or to commit, push and raise a PR. repo: https://github.com/nq-rdl/agent-extensions