12,459 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.
A tool for creating structured GitHub Issues in Chinese, with one section written for people and another organized for AI tools. GitHub Issues are records for bugs, tasks, and feature requests, and sub-issues break larger work into linked parts.
Write git commit messages that follow the Conventional Commits standard. Use when the user asks for a commit message, or gives a change summary or diff and wants it written up for git.
Orchestrate the canonical task↔PR↔release flow end-to-end. Two modes — /dev-flow start scaffolds an OpenSpec change + branch + (optional) worktree + git hook ready for commits; /dev-flow ship validates the current branch + pushes + opens PR + monitors CI. Use whenever you start any non-trivial change in a…
Manage stacked branches and pull requests with the gh-stack GitHub CLI extension. Use when the user wants to create, push, rebase, sync, navigate, or view stacks of dependent PRs. Triggers on tasks involving stacked diffs, dependent pull requests, branch chains, or incremental code review workflows.
Splits a large change into small, single-purpose units of review — PRs, diffs, or CLs — each making one argument (one diff, one thesis) and each buildable and testable on its own. Use when a change is too big to review, when a feature builds on existing code, when working in a large monorepo with stacked diffs, or…
Ship and capture lessons workflow. Creates the PR, updates lessons learned, updates documentation, generates the sprint retrospective, and updates the backlog. Use at the end of a sprint cycle, or when the user says "ship", "capture", "lessons", "retro", "retrospective", "wrap up", or "done with this sprint". Also use…
Use when releasing this repository from the CLI by promoting develop to main with a fast-forward push, grading the release as patch/minor/major by what installed projects actually pay, computing the next version from the latest tag, and publishing a GitHub release with agent-written notes. No release PR, no…
A skill for automating the full pull-request lifecycle. A pull request is a proposed code change submitted for review before it is merged into a shared codebase.
Clears AI reviewer feedback on your PR: reads real review-thread state, sweeps the sibling instances the reviewer missed, gates every push on your repo's own tests, then requests re-review — hard-capped so it can never spam the PR. Works with Codex out of the box, or any reviewer bot you configure.
★not rated 5 15d agoA
tokens not measured
originalMIT
Language-agnostic autonomous codebase improvement loop using isolated git worktrees. Every experiment runs on its own branch — main is never touched until a winning change is merged. Works with any language or framework.
★not rated 5 6mo agoA
tokens not measured
originalMIT
Four stateless PreToolUse gates, a PostToolUse JSON-config guard, and a docs-consolidation trigger. Denies a git commit that changes code without staging its covering docs (per-plugin README/CLAUDE.md pairs, or the nearest README/CLAUDE/AGENTS walking up); asks before a new-project scaffold command (npm create vite…
★not rated 5
changed 7d agoA
tokens not measured
originalMIT
Publish task-scoped changes to GitHub through a branch/commit/push/PR flow, including fork-based external contributions. Use when the user wants changes pushed or a PR opened; draft PR is the default.
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: