Git & VCS
Git operations, commit helpers, branch management
adynato-github
by adynato
GitHub workflow conventions for Adynato projects. Covers creating PRs with gh CLI, writing thorough descriptions, and using stacked PRs for large deliverables. Use when creating pull requests, managing branches, or breaking down large features.
ask-commit-assistance
by NavanithanS
Code review, staging, and Conventional Commit message generation.
git-best-practices
by aksuharun
Git best practices for commit messages and branch workflow. Use when: - Writing, reviewing, or advising on a git commit message - Advising on branching strategy, merging, or rebasing - Setting up or explaining a team Git workflow - Preparing or reviewing a pull request - Resolving or advising how to avoid merge conflicts - Any task involving git history, linear history, or PR hygiene
git-workflow
by qubernetic-org
"Enforce a strict Gitflow-based workflow with conventional commits, semantic versioning, and issue-driven branching. Use when the user asks to commit, create a branch, open a PR, tag a release, or perform any git operation. Also applies when mentions 'commit', 'branch', 'merge', 'release', 'hotfix', 'gitflow', 'conventional commit', 'semantic versioning', or 'semver'."
swarm-protocol
by co8
"Multi-agent development orchestration for complex projects. Use this skill when orchestrating parallel development workstreams, coordinating multiple agent tasks, managing project documentation structure, or executing /swarm-protocol commands. Triggers on: (1) /swarm-protocol <project-name> to initialize new projects with full planning, (2) /swarm-protocol (no args) to continue existing or start new project, (3) requests involving parallel agent coordination, milestone commits, or multi-phase development workflows."
skill-from-github
by SebastiaanWouters
Create skills by learning from high-quality GitHub projects
denvig-upgrade-npm-dependencies
by marcqualie
Use the denvig cli to upgrade your npm dependencies in the current project.
platform-setup
by Semprini
Use this skill when the user mentions VS Code, Claude Code, Copilot, or any IDE; asks about setup, installation, or configuration; asks "how do I use the agents"; asks "getting started with [platform]"; or needs help with platform-specific workflows, troubleshooting, or effective prompt patterns.
finish-branch
by iamladi
Post-merge cleanup workflow. Detects PR merge, switches to main, pulls latest, runs tests, and removes worktree if exists. Use after PR is merged to clean up.
diffx
by jaydenfyi
Operate the diffx Git-diff CLI for worktree diffs, local/remote ref ranges, GitHub PR diffs, GitLab MR diffs, commit/compare URL diffs, and git-diff-compatible pass-through. Use when an agent must decide what to diff, map intent to diffx input syntax, choose output mode (diff/patch/stat/etc.), apply include/exclude filters, or resolve common flag/pager conflicts.
readme-creator
by aksuharun
Creates high-quality, standardized README.md files for software projects suitable for open-source repositories. Use when asked to create or update a README.
docs-ingestor
by smestern
Ingest documentation for any Python library — crawls PyPI, ReadTheDocs, and GitHub to produce a structured API reference (classes, functions, pitfalls, recipes). Use when the agent needs to learn an unfamiliar library for scientific analysis. Requires sciagent[wizard].
memorytree-workflow
by beyondchenlin
Detect, initialize, and maintain a reusable MemoryTree project-memory workspace for any code repository. On activation, immediately detect and report the repo's MemoryTree state.
nvr-workspace
by cadrianmae
This skill should be used when the user asks to "show workspace", "what's my environment", "workspace context", "where am I working", "show current project context", or wants to understand their current development environment including directory, git info, and neovim instance.
pr-responder
by linuxlewis
Review and respond to GitHub PR comments. Use when analyzing PR feedback, determining which comments to address, classifying review comments by priority, or implementing fixes for code review feedback.
go-package-skill-creator
by ItalyPaleAle
Create skills for Go packages by fetching documentation from pkg.go.dev and generating structured SKILL.md files with usage patterns, examples, and best practices. Use when the user wants to create a skill for a specific Go package (e.g., "create a skill for github.com/lestrrat-go/jwx/v3") or needs to document how to use a Go library.
spec-kit
by samChang72
GitHub Spec Kit (Specify) - 嚴謹的 Spec-Driven Development 工具包，適用於大型企業專案。
openclaw-notify
by linuxlewis
Notify OpenClaw gateway when background tasks complete. Use when you were dispatched by OpenClaw/TARS for background work and need to ping the user that you're done, failed, or blocked.
update
by cadrianmae
Update the current development session with progress notes
copilot-customization
by ThomasRohde
Create, scaffold, and configure GitHub Copilot customizations for VS Code projects. Covers custom instructions (.instructions.md), prompt files (.prompt.md), custom agents (.agent.md), agent skills (SKILL.md folders), hooks (.github/hooks/), and MCP server integration. Use when asked to "set up copilot", "create an agent", "add instructions", "create a prompt", "scaffold a skill", "configure hooks", "customize copilot", or when building any GitHub Copilot customization for VS Code or GitHub.com.
diff-check
by b1tank
Author's cleanup checklist before committing or submitting a PR. Use before any commit or PR to ensure code is clean, focused, and ready for review. Checks for debug code, secrets, redundant changes, and scope creep.
git-trunk-based-workflow
by octivi
Plan and execute Git Trunk-Based Development workflows on a repository with main as trunk. Use whenever the user asks about branch strategy, branch naming, rebasing on main, merge conflicts during rebase, PR flow, merge strategy, safe history rewrite, or branch cleanup, even if they do not mention "trunk-based" explicitly. For commit message formatting and Conventional Commits wording, delegate to git-commits.
gh-pr-feedback
by brucehart
Address GitHub pull request review feedback using the gh CLI. Use when given a PR number and asked to read the PR comments/reviews, implement unaddressed reviewer updates, prioritize project owner feedback, and submit the fixes as a stacked/sub-PR targeting the original PR branch.
yeet
by lgariv-dn
"Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (gh)."