Agent Skills
Instruction packs for your AI agent — browse standalone skills, tool add-ons and skills that need setup first.
✦ Standalone skills2,358
Listed for general use, with no separate prerequisite named.
🧰 Tool add-ons426
Listed as skills bundled with a specific tool, with no separate prerequisite named.
🔌 Needs setup first88
Each relies on something you set up separately — such as an app, a command-line tool or an account — and its page names what that is.
google-labs-code · Version Control · Official
16 standalone skillscommit-message-storyteller
✓★ 36,202by github
Analyzes git diffs or staged changes and generates narrative commit messages that explain WHY a change was made, not just what changed — following Conventional Commits format. Use when asked to "write a commit message", "generate a commit", "describe my changes", "what should I commit this as", "commit this", "summarize my diff", or "help me commit". Works with git diff output, staged files, or plain descriptions of changes.
conventional-commit
✓★ 36,202by github
Prompt and workflow for generating conventional commit messages using a structured XML format. Guides users to create standardized, descriptive commit messages in line with the Conventional Commits specification, including instructions, examples, and validation.
create-github-issue-feature-from-specification
✓★ 36,202by github
Create GitHub Issue for feature request from specification file using feature_request.yml template.
create-github-issues-feature-from-implementation-plan
✓★ 36,202by github
Create GitHub Issues from implementation plan phases using feature_request.yml or chore_request.yml templates.
create-github-issues-for-unmet-specification-requirements
✓★ 36,202by github
Create GitHub Issues for unimplemented requirements from specification files using feature_request.yml template.
git-commit
✓★ 36,202by github
Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping
git-flow-branch-creator
✓★ 36,202by github
Intelligent Git Flow branch creator that analyzes git status/diff and creates appropriate branches following the nvie Git Flow branching model.
github-issues
✓★ 36,202by github
Create, update, and manage GitHub issues using MCP tools. Use this skill when users want to create bug reports, feature requests, or task issues, update existing issues, add labels/assignees/milestones, manage repository labels, set issue fields (dates, priority, custom fields), set issue types, manage issue workflows, link issues, add dependencies, or track blocked-by/blocking relationships. Triggers on requests like "create an issue", "file a bug", "request a feature", "update issue X", "set the priority", "set the start date", "create a label", "rename a label", "list repo labels", "link issues", "add dependency", "blocked by", "blocking", or any GitHub issue management task.
github-release
✓★ 36,202by github
Guides IA through releasing a new version of a GitHub library end-to-end. Handles SemVer versioning and Keep a Changelog formatting automatically.
issue-fields-migration
✓★ 36,202by github
Bulk-migrate metadata to GitHub issue fields from two sources: repo labels (e.g. priority labels to a Priority field) and Project V2 fields. Use when users say "migrate my labels to issue fields", "migrate project fields to issue fields", "convert labels to issue fields", "copy project field values to issue fields", or ask about adopting issue fields. Issue fields are org-level typed metadata (single select, text, number, date) that replace label-based workarounds with structured, searchable, cross-repo fields.
make-repo-contribution
✓★ 36,202by github
All changes to code must follow the guidance documented in the repository. Before any issue is filed, branch is made, commits generated, or pull request (or PR) created, a search must be done to ensure the right steps are followed. Whenever asked to create an issue, commit messages, to push code, or create a PR, use this skill so everything is done correctly.
pr-dashboard
✓★ 36,202by github
Open a GitHub PR dashboard in the browser. Use when the user asks to see their pull requests, open the PR dashboard, show PRs for a date range, or check PR status. Trigger phrases include "show my PRs", "open PR dashboard", "pull request dashboard".
repo-story-time
✓★ 36,202by github
Generate a comprehensive repository summary and narrative story from commit history
gh-address-comments
✓★ 23,283by openai
Help address review/issue comments on the open GitHub PR for the current branch using gh CLI; verify gh auth first and prompt the user to authenticate if not logged in.
non-interactive-git-rebase
✓★ 11,189by facebook
Use when needing to reorder, split, drop, or amend git commits that are not the top commit, without interactive editor access. Covers programmatic rebase via GIT_SEQUENCE_EDITOR, commit splitting with automated hunk selection, and metadata changes (author, message, dates) on any commit in a range.
pr-reference
✓★ 1,245by microsoft
Generates PR reference XML with commit history and unified diffs between branches, with extension and path filtering. Use when creating pull request descriptions, preparing code reviews, analyzing branch changes, discovering work items from diffs, or generating structured diff summaries.