7,078 mods tagged Git and workflow that install into Codex, 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.
Merge one branch (usually master) into the current branch while preserving local unstaged changes, resolving conflicts by understanding both sides, and catching silent semantic conflicts with the repo's own checks. Trigger on explicit /git-merge, or when the user asks to merge a branch/master into their current branch…
Open-source pipeline: fork, sanitize, and package private projects for safe public release. Chains 3 agents (forker, sanitizer, packager). Triggers: '/opensource', 'open source this', 'make this public', 'prepare for open source'.
A file-based handoff process between Codex and Claude Code. It moves work through six phases—specification, planning, building, review, polishing, and committing—using signal files to show which phase is current.
Review pending git changes and create senior-quality commits. Groups unrelated changes into separate logical commits, writes Conventional Commits messages that explain the why, and executes them — all on a tight token budget. Use when the user says "commit", "commit my changes", "commit like a pro", "ship this", or…
ZOEHIS Git delivery: commit, push, merge to release branches, cherry-pick, create tags. Use when committing code to master, pushing to remote, merging from master to release-1.166/1.168 branches, cherry-picking specific commits, tagging releases, or handling system parameter (jsonl) separate commits. Also manages the…
Guides users through repo-memory-workflow setup, task splitting, checkpointed AI development, and codex exec relay loops. Use when the project has AGENTS.md and .ai/TASK.md, or when the user says install this, initialize test, run a loop test, loop stuck, Round 1 starting, init, setup, Missing runloop, continue task…
Format changelog content according to Replit's changelog template structure. Use when converting raw changelog content into properly structured documentation with correct frontmatter, sections, and media formatting.
Create standardized, semantic git commits using the Conventional Commits specification. Analyze the actual diff to determine appropriate type, scope, and message.
Use this skill for Jujutsu megamerge workflows: maintaining one octopus merge over multiple independent work branches, staging new stacks, absorbing WIP into existing commits, restacking onto trunk, and publishing only individual branches.
A read-only tool that examines changes in a Git worktree, the folder containing a repository and its current edits, then drafts a commit message and a pull request (PR) title and description. If there are no current edits, it uses recent commits instead.
Prepare, validate, package, and publish portable Agent Skills through GitHub or npm. WHEN: "publish a skill", "publish SKILL.md", "ship a skill", "release an agent skill", "make this skill installable", "add a skill to my package".
Agent skill for interacting with code.storage, a managed Git infrastructure layer. Provides repository creation, branching, commits, file access, diffs, search, notes, GitHub sync, ephemeral branches, and forking through a RESTful HTTP API authenticated with customer-signed JWTs. Every repo operation scoped per-JWT.
Generate a concise, user-facing changelog from meaningful changes in the current repository and branch. Use when the user asks for a changelog, release notes, recent changes, or a summary of work over a date range or contributor scope.
Generates conventional Git commit messages from staged or unstaged code changes. Use when the user asks to commit, write a commit message, stage changes, or says things like "commit this", "what should my commit say", or "generate a commit message".
Use when the user wants to babysit a PR through the review/CI cycle, or invokes /pr-babysit. Polls for new review comments and CI failures, fixes them, resolves merge conflicts, and loops until the PR is ready to merge.
Automates the end-to-end contribution workflow to Alchemy open-source repos (github.com/alchemyplatform/) — read CONTRIBUTING, fork via gh, clone, set upstream, install deps with the right package manager, create a feature branch, run lint/tests, stage/commit, push, and open a Pull Request. Use this skill whenever the…
Use when asked to create, file, open, or raise a GitHub issue — including turning a bug report, a feature request, or a just-shipped backend change into a companion issue in another repository.
Analyze git status, batch commit changes by logical groups, and push to remote. No co-author or AI attribution info. Use when the user says "auto commit", "batch commit", "commit and push", or triggers /auto-commit.
Propose how to split the current git diff into logical commits — a Conventional Commit message plus the files to stage for each — then offer to create those commits once you approve the plan. Never adds agent or co-author attribution to commit messages. Use when asked to plan commits, write a commit message, or group…
End-to-end skill for creating git commits with proper tooling and safety checks. Use when you're asked to create a commit.
★not rated 2 7mo agoA27 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: