6,999 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.
Interpret and act on a moire finding. Use when moire check or moire verify reports a CONFLICT or BROKEN result against another agent's worktree, or when deciding how to respond to an overlap with concurrent in-flight work.
Kicks off a new feature by finding the next incomplete phase in specs/roadmap.md, creating a git branch, interviewing the user about scope/decisions/context, and writing a dated spec directory under specs/ containing plan.md, requirements.md, and validation.md. Trigger when the user says "feature spec", "next phase"…
Two-circuit backup & GitHub sync system for Home Assistant. Circuit 1 — real git inside /config with a deploy key, a pre-commit secret scanner and meaningful commits; Circuit 2 — full encrypted HA backups in GitHub Releases. Use EVERY time the task involves: backing up Home Assistant, syncing its config, git in…
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.
★not rated 17 5d agoA
tokens not measured
originalMIT
Enforces commit message format, changelog discipline, and file organization. Ensures git history is useful and documentation is current. WHEN to use it - before committing code, when creating or updating documentation, when organizing project files, or during code reviews involving git history.
An automated Git release workflow that takes code changes through a branch, commit, pull request, review checks, squash merge, and return to the main branch. A pull request is a request to review and merge changes into a shared branch.
A skill for managing pull requests in Forgejo repositories using the forgejo-cli. Supports creating, listing, viewing, merging, closing, and commenting on PRs.
Detects new MAF releases, extracts breaking changes, and keeps the toolkit's registry/matrix/guide current. Pipeline: (1) deterministic data extraction via GitHub Actions + Python helpers + dotnet-inspect, opens a PR with raw data and TODOs on a per-version branch (never commits direct to main), (2) optionally, a…
Work on a OneDev pull request. Use when the user asks to review, merge, resolve merge conflicts, approve, request changes, address feedback, investigate or fix a failed build, improve, or continue PR work.
Draft a GitHub pull request that edits a founder-kernel page. Kernel pages under docs/founder-kernel/ are PR-only per spec §4 (never written by the runtime); this skill walks the user through reading the current markdown, applying the requested change, validating wikilinks + manifest counts, and opening a draft PR for…
Drive a whole phase or feature-set to "merged + Done" — themed batching over /drive, front-loaded architectural questions, phase-gate ceremonies, and lossless resume. The long-horizon recipe ABOVE /drive; pair with native /goal " delivered" for hands-off, multi-turn completion.
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.
★not rated 13▲
+1 27d agoA
tokens not measured
originalApache-2.0
Cross-agent repo-local progress checkpoint workflow for any git repository. Use this skill whenever the user says save progress, checkpoint, snapshot the current lane, capture key chat context, write down what matters before closing, or wants the next session to resume immediately from Codex, Claude Code, opencode, or…
Use when taking a repo open source, or hardening one that already is. Run /oss-launch and it scans the repo (stack, existing files, git remote, secrets), asks only what it cannot infer, then generates a tailored OSS file collection (README, LICENSE, CONTRIBUTING, CODEOFCONDUCT, SECURITY, CHANGELOG, .gitignore…
Walk a code change (or full release branch) through a 12-item production-readiness checklist and produce a go / no-go report with concrete remediations.
Review GitHub pull requests using gh CLI and the GitHub API. Use when asked to review a PR, inspect PR changes, or choose approve/comment/request-changes.
Enrich an existing PKUP report directory — group commits into tasks, filter out non-creative groups, and write Polish descriptions. Use when the user has already generated a PKUP report and wants to clean it up or add "Zaprojektowałem..." descriptions.
★not rated 11 26d agoA59 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: