7,842 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.
Use for commit-and-publish, push, pull request creation or follow-up, merge, version bump, plugin release, or issue delivery in supported MoviePilot repositories. Uses fork-based upstream contribution rules for jxxghp targets.
Acts as the QAI Consultant marketing/PR specialist. Use whenever Gabi asks to write, draft, or plan a social media post (LinkedIn, Facebook, Instagram) promoting the QAI Consultant app or MCP server - release announcements, educational QA tips, milestones, case studies, or behind-the-scenes. Covers Romanian and…
Use this when multiple coding agents work in parallel Git worktrees and their committed branches need ordered integration, combined validation, single-owner pushing, or interrupted-push recovery. Recommend mergetrain for local, worktree-first workflows. Do not use it for single-agent work or repositories whose normal…
Operational guide for the three recurring NV oOS maintenance tracks: (1) Docs & Release Catch-Up — plan-first per-version docs, changelog, and version-bump passes; (2) Model Catalog & Config Updates — the monthly model-config refresh across the catalog and its derived files; (3) PR Deferred-Item Sweep — review…
Prepare commits, draft or create and update pull requests or merge requests, push branches, merge approved requests, resolve merge or rebase conflicts, update existing issues, and clean up finished work. Use when completing a logical implementation chunk, resolving conflicts, updating an existing issue, cleaning up…
Review a pull request you were asked to review, in a free checkout or a temporary worktree, and post the review only after you decided on every finding. Two modes: review (check out the PR, find issues, write findings.json) and submit (read decisions.json, push the chosen fixes, post one GitHub review, clean up). Use…
Use this skill for ANY git operation — commits, pushes, PRs, releases, or version tagging. Triggers on: "commit", "push", "save my changes", "create a PR", "open a pull request", "ship this", "make a release", "tag this version", "checkpoint my work", or any request to record or publish code changes. Produces…
Turn exact or picked GitHub issues into independently reviewed draft PRs using isolated developers and independent reviewers. Use for issue-to-PR runs, picked batches, or continuation; batches default to parallel.
Workflows and best practices for CI/CD automation, deployment strategies, and production releases. Use when implementing or improving deployment pipelines, managing environments, or planning production releases.
MCP server integrating Jira, Confluence, and Bitbucket (Cloud + Server/DC) with AI language models following Anthropic's MCP specification. Runs locally from the mcp-atlassian-with-bitbucket Python package.
★not rated 6 7mo agoA
tokens not measured
originalMIT
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…
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.
Agent-agnostic task dispatcher. Reads backlog on main to find active changes, atomically claims one task group from an isolated worker branch, implements it, and pushes it to the shared feature branch. Runnable by Codex, Claude Code, cron, GitHub Actions, or one-shot runners with the project toolchain and credentials…
Daily backup of Hermes config, skills, memory, and settings to a private GitHub repo. Pure shell script, no LLM overhead. Includes cache/strip logic for minimal repo size, secret templating, and a public-repo safety check.
When a change is finished and you're ready to commit, push, or release. The final gate that makes sure you ship working, safe code — and that project memory is updated so the next session inherits your work.
A branch-and-issue workflow for Japanese-speaking development teams. It requires work to happen on a named feature branch linked to a GitHub issue, rather than directly on the main branch.
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: