12,306 mods tagged Git and workflow that install into Claude Code, measured the same four ways as everything else here: what each costs in tokens on every session, what a security scan found and why, whether it is the original, and what changed.
Entry point for any change request. Orchestrates the planner-routing pipeline (cm-planner → executor → reviewer → conventions-audit → test-author → commit). Use for any work that touches code or docs.
Prepare or create Git commits for the user. Use whenever the user asks to commit changes, split work into commits, write commit messages, stage files, or clean up a dirty worktree before committing, and after each completed phase of a sequenced coding or refactoring workflow. Creates descriptive commit messages…
Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas.
Drive a GitHub pull request from conflicts or failing checks to merge-ready status. Use when the agent should confirm the PR target, resolve against base, verify, push, observe Actions and mergeability, loop safely, and notify the result.
Sync local repos after a PR merge. Use when the user says "I merged", "just merged", "PR merged", or similar. Pulls both workspace repos and reinstalls skills if openclaw-skills changed.
Claude Code skills for Linux kernel development: StGit patch management, perf profiling analysis, trace-cmd event tracing, drgn live kernel debugging, and b4 patch workflows.
★not rated 2
changed 4d agoA
tokens not measured
originalMIT
Use when the user wants to share a project to GitHub. Runs a full pipeline: root audit, file naming and structure, document fixes (headings, code-block language tags, table alignment, explicit command interpreters), generate missing files (LICENSE, .gitignore, CONTRIBUTING.md, Issue/PR templates), README rewrite…
Bumps semver in canonical project files, updates changelog/README, scans for stale version literals, runs optional build/test, and git commit/push. Use when the user says publish new version, release, bump version, tag app version, or ship a release.
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…
Preserve engineering context when moving work between AI coding tools and IDEs. Use when migrating an active project between Qoder, QoderWork, Claude Code, Copilot CLI, Codex CLI, VS Code, Cursor, Windsurf, Gemini CLI, or Codex App; when locating local chat history; or when producing a portable, git-verified…
Manage GitLab Merge Requests using the glab CLI. Use this skill whenever the user mentions creating a merge request or PR, listing MRs, approving, merging, reviewing, checking out, or rebasing a merge request. Trigger on phrases like "create MR", "open a pull request", "approve MR.
Push code, automatically run /commit if not yet committed, compute elapsed time and log work to Jira accurately. Handles all edge cases: no-ticket, no-state, re-push, multi-task, duplicate worklog, corrupt state, negative elapsed, wrong commit author.
Run the full pre-PR review per AGENTS.md §7 — gates, tagged diff walk, pessimistic meta-check, acceptance-criteria mapping, commit hygiene, rebase status, PR-description draft. Use when the human says "ship it", "ready to PR", "open the PR", "pre-PR check", or invokes /pre-pr.
Commit changes across the LiteStack meta-repo and its submodules. Use this when the user asks to commit, save changes to git, or "commit this" while working at the LiteStack root. It commits inside each changed submodule first, then records the updated submodule pointers in the meta-repo, and pushes according to the…
Open a GitHub pull request using the kit PR template. Use when the user asks to open/create a PR, push and PR, or publish a branch. Write a detailed, product-facing description. Contracts and harness review stay local — never put feature IDs, contract paths, or harness sections in the PR title or body.
Reference for interacting with GitHub (gh CLI), and the Atlassian stack — Jira, Confluence, Bitbucket, JSM — via atlassian-cli. Use when reading/writing issues, PRs, pages, or comments in any of these tools.
Watch homelab/gitops peer repositories on the k8s-at-home GitHub topic for interesting commits, rank them, and post a summary to a Discord channel via webhook.
Reimplement a messy git branch with clean, narrative-quality commit history suitable for code review. Use when a branch has WIP commits, debug commits, or trial-and-error history that needs to be transformed into a reviewable story before creating a PR.
Bootstrap a new repo into Katala OS agent-context style — AGENTS.md inheriting the global baseline, cross-OS .gitattributes, shared pre-commit hook via core.hooksPath, optional hash-locked CONSTITUTION + manifest.lock.json + verify.sh, NEEDSREVIEW.md. Use when the operator asks to "start a new repo", "scaffold an…
Use when the user asks to commit, create a git commit, stage and commit changes, or wants a gitmoji commit message for staged changes.
★not rated 2 1mo agoA32 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: