Answers "why does this code exist" for colinhacks/zod by tracing file:line -> git blame -> commit -> PR -> linked issue via the provenance-mcp MCP tools (traceline, askwhy, searchhistory), then renders a cited WHY/EVIDENCE/STILL LIVE?/VERDICT/CONFIDENCE verdict. Never authors a reason without a citation -- marks NOT…
Distill a git repo's full history into durable engineering memory under .repo-memory/ (timeline, decisions, landmines, architecture). Use when the user wants historical/"why is this like this" context for a codebase, to onboard an agent onto a repo's past, or asks to run repo-history / analyze git history.
Mandatory git workflow: Conventional Commits, atomic commits, and strictly linear history via feature branches that rebase onto the default branch and integrate with --ff-only. Use whenever committing, staging, branching, merging, rebasing, or preparing a PR — including bare requests like "commit", "commit this", or…
Produce an evidence-backed release go/no-go decision from Git changes and machine-readable test reports. Use when preparing a release, reviewing deployment readiness, checking whether change evidence is complete, assessing DDL or API/configuration risk, creating a rollback checklist, or deciding whether a build may…
Drive the Tidy backup & sync tool from the terminal. Use whenever the user asks to back up, sync, schedule, push, pull, or manage their git-backed folders/repos (e.g. an Obsidian vault). Tidy is a git-based backup tool — each repo folder has one or more daily backup times, and every other goal is mapped to a tidy CLI…
Analyze Git changes, split them into coherent commits, infer message language and format, optionally close supplied GitHub issues, and execute safely. Manage persistent global or repository preferences for review versus direct submission and automatic or specified commit-message language through native Git config.…
Default workflow for executing and monitoring local, SSH, or GitHub publishing work through RunBeacon. Use whenever Codex needs to call a remote server or host, use SSH/SCP/SFTP credentials, securely save an IP/host plus username and SSH password, configure or select default credentials, configure a GitHub personal…
Triage and handle GitLab project, repository, issue, merge request, review, CI/CD, label, reaction, file, branch, and commit work through the bundled GitLab MCP server. Use when the user asks for general GitLab help, wants issue or merge-request summaries, needs repository context, or needs a GitLab operation that is…
Delegate independent coding, review, or research tasks to low-cost DeepSeek Harness agents in isolated Git worktrees, with duration-aware foreground or detached monitoring and Markdown review artifacts. Use when the user explicitly asks for DSH, DeepSeek, external/low-cost subagents, or batch delegation; do not use…
Safely preview and publish prebuilt game releases to exact itch.io channels with butler, license provenance, immutable receipts, and parent-build drift gates.
Discover approved Git and non-Git projects and safely inspect, edit, test, and use guarded Git delivery when available through ChatGPT Workspace MCP tools.
Run ONE iteration of the Kumihimo build loop — take the next item off the queue, ground it against PLAN.md, build it, verify it, document it, commit it. Use when Thomas invokes /kumihimo-iteration (often wrapped in /loop for unattended runs) or asks for another build pass on Kumihimo. Covers the queue, verification…
Pay in-scope completion debt and leave a verified, successor-ready repository, or guard an active candidate from known debt. Invocation authorizes the documented work; AUDIT is explicit read-only analysis.
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use…
Use when a repository's development server or test queue is managed by Worktree Switcher, or when the user asks to inspect, claim, start, switch, or test a registered project through its MCP tools. Do not use for creating, deleting, or pruning Git worktrees.
Work with Gerrit code review from the terminal using the gerrit-cli binary - search changes, read diffs and inline comments, draft and publish review comments, add reviewers, set topic or WIP, abandon and revert. Use whenever the user mentions Gerrit, a CL or change number, a Change-Id, a gerrit. URL, a patchset, or…
Verify multi-repo agent claims at Git HEAD with GitPin (index-free evidence). Use for catalog, search candidates, pin.prove / pin.proveset, pin.verify / pin.verifyset, EvidenceBrief, and citation checks. Never treat dirty worktrees or search hits as claims.
Use stash MCP to work with Bitbucket Server projects, repositories, and pull requests.
★not rated 0 8d agoA19 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: