15,311 mods in this category, of every kind an
agent can take. Each one carries what it costs per session, what the
scan found, and whether it is the original.
Use when committing changes with git — staging files and writing commit messages. Makes the agent keep each commit focused on one logical change and write a clear, conventional message explaining why, instead of dumping unrelated edits into a single vague "update" commit.
Lets the agent work with GitHub: search code, read and create issues and pull requests, and manage repositories through the GitHub API. Runs locally from the @modelcontextprotocol/server-github npm package. Needs 1 environment variable to run.
Address review comments on your own pull request: implement valid suggestions, reply to invalid ones, and resolve threads. Covers inline review threads, review body comments, and plain PR timeline comments. Use when: user says "address PR comments", "implement PR feedback", "respond to review comments", "handle review…
Estrutura Git e CI/CD para projetos Oracle/APEX/ORDS. ATIVE em estrutura de projeto Oracle no Git, commit de objetos do banco, script de deploy, GitHub Actions para Oracle, export APEX split via SQLcl, versionamento de módulos ORDS, GMUD naming (001projetoddlobjeto.sql), deploy-db/deploy-apex/deploy-ords, branch…
Two-agent autonomous loop (Builder + Reviewer) for shipping multi-phase coding deliverables end-to-end without mid-run human input — finished work on an isolated harness branch with a PR opened back to the source branch.
★not rated 2 4mo agoA
tokens not measured
originalMIT
Guide users through TCR (Test && Commit || Revert), TCRDD, and git-gamble workflows. ALWAYS trigger when a user mentions TCR, TCRDD, "test commit revert", "git gamble", or "git-gamble". Trigger when a user wants to combine TDD with automatic commits/reverts, enforce baby steps via a commit-or-revert loop, or asks…
Repository-agnostic Neneko CR workflow for triaging, reviewing, fixing, reporting, approving, and optionally merging GitHub pull requests across any project. It separates external-PR review from own-PR maintenance, checks current-head CI and review threads, verifies problem necessity and solution fit, requires an…
Process and reconcile new Just Press Record iPhone recordings into a configured Git-backed Markdown vault. Use when the user invokes $vcr or asks to process the configured Just Press Record capture source; do not use for generic transcription or unrelated voice apps.
Release workflow for the edloidas/skills collection. Validates git state, analyzes commits since the last tag, recommends a version bump (major/minor/patch), updates Claude and Codex packaging metadata, commits, tags, and pushes.
Split one chunky branch into a stacked set of review-friendly PRs. Re-carves the cumulative diff into fresh, ordered commits — plan approved by you first, every PR tip green, final tip provably identical to your branch.
★not rated 2 1mo agoA
tokens not measured
originalMIT
Use Ghostpatch as an agent-native open-source contribution plugin for Codex, Claude Code, and other coding agents. Trigger when a user wants the agent to find repositories, discover GitHub issues, qualify candidates, solve issues locally, review diffs/tests, and raise approval-gated pull requests using the Ghostpatch…
A read-only code review guide that checks a defined set of changes against the intended requirement, project rules, and evidence from the code and tests.
Explicit-only workflow for coordinating one Codex App background thread per task in Codex-managed worktrees. Use only when the user invokes $codex-managed-worktree-threads. Do not use for natural-language-only parallel work requests, ordinary subagent delegation, manual git worktrees, tmux workflows, Codex CLI worker…
Polish any GitHub repository's surface — labels (emoji rating tiers, P0–P3 priority, impact severity), issue forms, PR template, CI workflows, CODEOWNERS, rulesets, docs. Repo meta & config only — no code logic touched. Use when creating a new repo or polishing an existing one.
Multi-agent development orchestrator: classify by complexity, implement in isolated git worktrees with TDD + Tidy First, review under a two-party boundary, and stop at open PRs for human merge.
One-shot release pipeline: commit, push, PR, merge, and branch cleanup. Auto-adapts branch strategy -- git-flow (feature to develop to main) if a develop branch exists, otherwise GitHub Flow (feature to main). Runs a pre-merge gate bundle: functional check (verify.sh or the project's test command), security scan…
★not rated 2 3mo agoA
tokens not measured
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: