15,303 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.
Capture the intent behind staged changes as a provenance doc in docs/intents/, extracted from the Claude Code and Cursor chats that produced the code. Use when the user asks to generate or preview an intent doc, capture commit intent, check why the pre-commit intent hook skipped or failed, or run its self-test.
Claude Code skills and an orchestrator agent for declarative Harny workflows across Claude and Codex, including run analysis, PR delivery, and release management.
Use when the user wants to start work on a GitHub issue, set up a worktree and development environment, plan the implementation, write tests, and create a PR. Triggers: "start issue", "work on #123", "pick up issue 123", "new issue", or /github-issue [ISSUE].
Full implementation mode - end-to-end feature implementation with phased execution, parallel work streams, verification gates, and atomic commits per phase.
ArgoCD GitOps model for the lab: what is and isn't managed, sync rules, bootstrap vs managed distinction, and common sync failures. Use when working with ArgoCD Applications, adding new templates to git, or troubleshooting sync issues.
Rebase from the latest origin/main, squash the commits from it, and then create a PR on github with intelligent commit messages based on staged changes. Invoke with /create-pr.
Manage AI agent skills backup and sync via the skills-manager CLI. Use when the user asks to push skills to GitHub, pull skills from GitHub, link or symlink skills to agents, sync skills across machines, set up project-level skills, or manage the /.agents/ directory. Also triggers on "sm push", "sm pull", "sm link"…
Drafts concise release notes from merged pull requests and conventional commits. Use when the user asks for a changelog, release notes, or a GitHub release body.
Read-only GitHub PR status and reference graphs for maintainers and agents. Use whenever the user asks for PR counts or status by author, project, repository, or review state; approved, changes-requested, conflicting, draft, ready-for-review, or unassigned PRs; a compact portfolio table; or counts for named…
Build and versioning rules for the Touchpad Shield Windows application. They define semantic versions, automatically increased build numbers, debug/beta/release labels, output folders, and when each build type may be created.
Given a company name or domain, find their changelog/release-note sources, add them to Releases, and fetch recent entries. This is the manual, Claude-driven onboarding flow — it uses the releases CLI against the production API and does not dispatch to managed agents. (If you want managed-agent onboarding, use releases…
A shipping pipeline for Claude Code: orchestrate a locked plan or a list of fixes with fresh-context agents or Orca/herdr/cmux worker panes, polish and explain the diff, ship it to a plain-language PR, run an incremental agent review-fix loop until clean, and clean up after merge.
★not rated 11
changed yesterdayA
tokens not measured
originalMIT
Generates a reviewer-friendly pull request description from the branch diff. Use when opening a PR, when asked to summarize a branch, or before requesting review.
Sync gitignored directories (clients/, partners/, scripts/, .env) between MacBook and Mac Mini over SSH using rsync. Use when the user types /sync-to-mini, /sync-from-mini, /sync-to-macbook, /sync-from-macbook, or /sync-machines.
Comprehensive PR review pipeline: a pre-review readiness gate (stops on merge conflicts or red code-related CI with a fix-it note, no verdict), branch-level analysis with merge-base attribution (the verdict is decided only by defects the diff introduced, worsened, or interacts with — purely pre-existing defects are…
★not rated 11
changed 1mo agoA
tokens not measured
originalBSD-3-Clause
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: