Git & VCS
Git operations, commit helpers, branch management
context-ingestion
by sxg
Scan project folder structure, validate organization, clone GitHub repository, and generate an inventory of available materials. First step of writer workflow. Use when starting a new manuscript project.
requesting-code-review
by Jackiexiao
"Use when finishing major work and needing code review before merge."
github-to-skills
by Ontos-AI
Automated factory for converting GitHub repositories into specialized AI skills. Use this skill when the user provides a GitHub URL and wants to "package", "wrap", or "create a skill" from it. It automatically fetches repository details, latest commit hashes, and generates a standardized skill structure with enhanced metadata suitable for lifecycle management.
git-commit-bullets
by bowentan
"Perform git commit with the message body written as a bullet list. Use when committing with git and the user wants bullet-list commit bodies."
golang-testcontainers
by baotoq
Write integration tests in Go using testcontainers-go with real databases, caches, and message queues in Docker containers. Covers PostgreSQL, MySQL, Redis, RabbitMQ, Kafka, and custom containers with idiomatic Go testing patterns.
work-jira
by choru-k
Interact with Jira issues via CLI. View ticket details, list assigned issues, create new tickets. Use for "work-jira", "jira", "view ticket", "my jira issues", "create jira ticket".
github-branch-policy
by Oceanswave
Audit GitHub repository branch governance and workflow hygiene. Use when asked to review rulesets, required status checks, update restrictions, bypass/update behavior, delete-on-merge settings, auto-merge workflow reliability, stale branches, ghost workflow registrations, or branch-policy drift.
git-commits
by DaleSeo
Best practices for creating high-quality Git commits. Covers commit message conventions (Conventional Commits), atomic commits, staging strategies, and when to amend vs create new commits. Helps AI agents generate clean, meaningful commit history.
changelog
by khw1031
CHANGELOG.md에 변경 사항과 담당자를 정리하고 package.json 버전을 올립니다. changelog 작성, 변경 이력 정리, 버전 올리기, 릴리즈 노트, CHANGELOG 업데이트 요청 시 사용.
gitflow-changesets-releases
by TevfikBGunes
Follow Gitflow with Changesets for branching, versioning, and releases. Manual changeset creation is recommended for reliability. Use when (1) creating or merging feature, release, or hotfix branches, (2) writing conventional commits, (3) adding or versioning changesets, (4) running tests before PR or release, or (5) the user asks about releases, changelog, branching, or gitflow.
upstream-sync
by dris1153
Sync forked/cloned open source repositories with upstream changes. Fetches upstream diffs, evaluates each change against the local project, and applies changes by directly editing files (no git merge/rebase). Use when user wants to fetch, review, analyze, or integrate new commits from an upstream/original open source repository into their customized fork. Trigger on keywords like "sync upstream", "merge upstream", "rebase upstream", "fork sync", "upstream changes", "new commits from original repo".
forge-update
by fwehrling
FORGE Updater — Updates all FORGE skills from the latest GitHub release. Usage: /forge-update
agile-workflow
by yabasha
Comprehensive agile development and repository management skill. Sprint planning, backlog grooming, issue triage, story point estimation, parallel developer orchestration, branch strategy, conventional commits, release management, code review, CI/CD, monorepo management, Kanban, retrospectives, repository health, and team coordination.
commit
by iulspop
Commits staged changes using the conventional commits format with proper type, scope, and description. Use when committing code changes to maintain a clean, standardized git history.
just
by SecKatie
just is a handy command runner for saving and running project-specific commands. Features include recipe parameters, .env file loading, shell completion, cross-platform support, and recipes in arbitrary languages. This skill is triggered when the user says things like "create a justfile", "write a just recipe", "run just commands", "set up project automation with just", "understand justfile syntax", or "add a task to the justfile".
collab
by teslasoft-de
Track collaboration state between Claude sessions using git branches. Enables seamless context switching by persisting progress in feature branches. Use for multi-session work, handoffs, and publishing completed work. Keywords: collab, git, branch, session, checkpoint, resume, publish.
ci-monitor
by dhughes
This skill should be used when the user asks to "monitor the PR", "watch the CI", "check if CI passes", "let me know when CI finishes", "watch the checks", "monitor CI status", "tell me when the build completes", or any variation requesting to track GitHub PR check status until completion. Also use this skill proactively after creating or updating a PR when the user would benefit from knowing the CI result.
git-commits
by Klohto
Creates commits, PRs, and branch names using Conventional Commits style matching @klohto's patterns. Use when writing commit messages, creating PRs, or naming branches.
changelog-generator
by Hiccup-za
Automated changelog generation with semantic versioning. Triggers on: generating changelogs, updating versions, releasing software, version bumps, changelog updates, semantic versioning, and when users ask to "update changelog", "bump version", "create release", or "generate changelog". Use when user: needs to update CHANGELOG.md, bump package.json version, create a release, generate changelog entries, or follow semantic versioning and Keep a Changelog standards.
Skill-Updater
by tempest-01
Git-based skill auto-updater for OpenClaw. Syncs skills to GitHub, checks clawhub versions, auto-merges local modifications, and pushes updates daily via cron. Includes conflict detection and formatted QQ summaries.
gotcha-summarizer
by lian-yang
"Automatically summarizes technical lessons learned from conversations into docs/gotchas/. Supports 18+ programming languages with confidence scoring. Use at the end of conversations to capture: (1) Frontend/Backend bugs and root causes, (2) Framework issues (React/Vue/Next.js/Nuxt/Databases/APIs), (3) Code quality improvements (precision, caching, concurrency, etc.), (4) Performance optimization insights, (5) Testing/CI/CD/Git issues, (6) Any technical lessons worth documenting. Features: three-layer classification (Domain → Category → File), fuzzy duplicate detection, i18n support (zh/en), multi-code block grouping, error tracking statistics."
git-branch
by erinrugas
Creates and manages branches with clear naming and safe branching flow. Use when starting work, switching context, or cleaning up branches.
skill-publisher
by L61
Publish and distribute skills to GitHub and npm. Use when user wants to "publish skill", "release skill", "distribute skill", "share skill", or "deploy skill to npm". Handles GitHub repository creation, npm package publishing, and installation testing.
aico-worktree
by yellinzero
Create isolated git worktree for feature development. Handles directory selection, gitignore verification, project setup, and baseline test verification. Use this skill when: - Starting feature work that needs isolation from current workspace - Before executing implementation plans on a new branch - Want to work on multiple branches/features simultaneously - User asks to "create worktree", "isolate this work", "separate branch" - Need clean baseline before starting major changes Safety: ALWAYS verify worktree directory is gitignored before creating. Process: Check directory → Verify ignored → Create worktree → Run setup → Verify baseline tests