22,769 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.
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments. Triggers Greptile review, fixes all actionable comments, pushes/re-shelves, re-triggers review, and repeats. Use when the user wants to fully optimize a…
A release checklist for publishing a new version of the Usage4Claude app. It covers collecting changes, writing release documents, updating the version, checking the build, and preparing the commit that starts automatic publishing.
Coordinates a large batch of GitHub issues through separate Codex worker threads, tested pull requests, review loops, and gated merges. Use when the user asks one Codex thread to manage several coding sessions or complete a parent issue, milestone, or issue batch.
Rebase, rewrite, squash, reword and push Hardwood PR history — including contributor PRs whose author and committer identity must survive the rewrite. Use whenever the user asks to "rebase", "rebase onto main", "fix the commit message", "prefix with the issue key", "squash the commits", "force push (with lease)"…
Claude Code instructions for openwong2kim/wmux, covering language (owner decision, 2026-07-20), skill routing, design system and versioning & release (owner decision, 2026-07-05).
End-to-end implementation loop for the os-clovy repo: study the prompt, ask the clarifying questions that change what gets built, plan and architect on the session model while delegating bulk implementation and review to cheaper strong models, isolate work in git worktrees, validate with deterministic checks plus…
Read ghtkn's documentation with ghtkn docs list and ghtkn docs show before answering. ghtkn is a CLI that creates short-lived (8h) GitHub user access tokens from GitHub Apps. Use for any question about ghtkn, GHTKN environment variables, ghtkn get / exec / auth / agent / revoke, the ghtkn git credential helper, or…
Spin up an isolated agent to work a kube-coder issue. Given an issue number, creates a clean git worktree branched from a freshly-fetched origin/main, pulls the issue text, and launches a background Claude task that is BORN inside that worktree (workdir=worktree) so it cannot work in the shared clone. Use whenever the…
Orchestrate a NeoHaskell change end-to-end through the spec-gated pipeline - intake to merged PR with exactly two human gates. Use when implementing a feature, fixing a bug, or running any request that should produce a PR.
Instructions for ellipticmarketing/modelrelay, covering agent instructions, post-feature testing, git commits, release process (mandatory) and test architecture.
Run this skill from the repository root. Treat the release as a real public publish: verify the current remote state first, keep unrelated user changes out of release commits, and report exactly what was built, pushed, and released.
Project instructions for the Xiaozhi Client repository, covering its development principles, commands, quality checks, Git hooks, and release process. Git hooks are automated checks that run during commits.
Add existing screenshots or screen recordings to a GitHub pull request as a before/after or preview block. Use when a PR needs visual media attached to its description. Browser navigation and capture belong to agent-browser.
AGENTS.md instructions for educlopez/ui-craft: Contributor and agent papercuts in this repository live as GitHub issues labeled friction, not as files in the tree. A daily Cursor Cloud Agent investigates them.
Implement a GitHub issue in this repository by applying the shared implement-specs workflow with Oz-specific issue, spec-context, and summary-file handling. Use when issue details are provided in the prompt and the agent should produce the repository diff and a concise implementation summary, without creating commits…
★not rated 307▲
+3 3d agoA74 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: