12,308 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.
optimiziramsi's Claude Code toolkit as ONE plugin, organized topic-first — one folder per concern (git, commit, reporting, session, review, repo, instructions, flow, patterns, worktree, setup), each owning its own skills/commands/agents/hooks. Opinionated concerns carry env kill-switches; guards self-gate on project…
★not rated 2 23d agoA
tokens not measured
originalMIT
This skill should be used when the user asks to "autofix pr", "fix pr locally", "fix ci failures", "fix review comments", "iterate on pr", "fix failing checks", "fix pr comments", "make ci green", "fix the build", "address reviewer feedback", or wants to iteratively fix CI failures and review comments on a GitHub PR…
Share reusable agentic patterns from project repos back into an upstream template, safely. WHEN TO PROPOSE: (1) After pushing commits touching high-signal paths, (2) Sprint/milestone review, (3) When agentic tooling is created. Classify commits as: YES (portable), MAYBE (needs changes/judgment—offer to fix), or NO…
Write features, fix bugs, and create PRs for the NanoClawbster codebase. Works in an isolated dev workspace, pushes via Composio (CI validates on GitHub Actions), and deploys after user approval.
Cleans up local Git worktrees and branches whose work is provably absorbed elsewhere, deleting each risk group only after its own confirmation. Use after merging pull requests or after parallel agent worktree sessions.
Autonomous GitHub Issue Fixer agent called LoachBot. Picks the single most-recently-updated GitHub issue created by and assigned to you, implements a fix in a Pull Request, then unassigns the issue. Use when the user wants to work through issues assigned to them, or asks to "run LoachBot Issues", including repeated…
Manage multiple GitHub Pull Requests in parallel. In a single loop pass, for every PR: check CI status, auto-classify each failing check (transient infra / lint / binary-compat / build / test) and delegate to the matching fix-ci- skill, then handle unresolved review comments end to end (fetch → fix → commit → push →…
Drive a task queue (loop-tasks.md) to completion in ANY repo — detect the repo's own rules, then for each task plan → /review-plan → implement → verify → /review → fix all findings → commit → push → client doc → mark done. Autonomous between tasks; pauses only for genuine product decisions.
This skill should be used when the user asks to "create a PR", "open a pull request", "submit my changes", "push and create PR", "finalize my work", "/pr", or wants to commit, validate, and push their current branch as a pull request. Handles the full workflow: commit all changes, run quality gates with best-effort…
Command "code-review" from r0r1/claude_code_config, covering review github pr with linear issue specification, arguments provided, prerequisites check, step 1: extract github repository and pr information and step 2: fetch linear issue details.
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.
Use in this repository after local edits when an agent is asked to commit, push, open or update a PR, or prepare a submit handoff. Enforces Silk-specific docs sync, validation reporting, and commit/PR title naming.
Publish-copy rule. Defines inclusion (spec-derived paths to copy) and exclusion (internal tooling to never copy). The /publish-copy command MUST read this rule and copy only inclusion paths.
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.
★not rated 2 4mo agoA40 tokens
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: