Use this agent when the user wants to save work, sync repos, undo changes, check history, or manage branches. All git operations happen through natural language — the user never needs to know git commands. Examples: Context: User finished working and wants to save. user: "Save my work" assistant: "I'll use…
Use this agent when you need to create git commits with properly formatted conventional commit messages. The agent will check for staged changes and create commits following the Conventional Commits 1.0.0 specification. Examples:\n\n \nContext: User has made code changes and staged them for commit\nuser: "I've…
Use this agent when you need to perform any Git version control operations, GitHub repository management, or related tasks. This includes creating commits with proper conventional commit format, managing pull requests, handling issues, working with branches, analyzing repository history, and using GitHub CLI tools.…
Use this agent when you need to prepare, validate, or execute a software release. This includes creating release branches, updating version numbers, generating changelogs, validating release readiness, creating GitHub releases, publishing to package registries (PyPI, npm, etc.), and coordinating the entire release…
Agent "pr-writer" from junianwoo/claude-toad, covering generated by claude toad — review before use, context about this project, writing the pr description, what and why.
Use to set up and own the repository's plumbing — git branch model, commit/PR conventions, CI, signing, fastlane, build flavors, and secrets handling. Produces docs/23-git-strategy.md and the CI/build config. Triggered early in /app-init and whenever the build/release pipeline needs work.
Use when the sprint is done and the team wants to prepare a release — assembles a signed, submission-ready build for iOS and Android, owns version bumps, build numbers, release notes, and the submission checklist. You never upload or submit to a store — that is always the human founder's action. Triggered by /app-ship…
Use this agent when bead work is not visible on DoltHub, when configuring or repairing a bd Dolt remote, when deciding between bd backup and bd dolt push, when taming sprawled per-project dolt servers by reaping idle ones, or when diagnosing Dolt-remote drift. It knows the #1 root cause (no remote configured) and that…
Use this agent when the user requests a morning report, daily summary, or overview of their GitHub activity. Trigger phrases include 'morning report', 'github report', 'daily github summary', 'what's happening on github', or 'check my github status'. This agent should be used proactively when the user starts their day…
Canonical pre-commit check for any wiki write. The Verification Gate is a small, project-extensible criteria list that every ingest skill (/wiki-experiment, /wiki-source, or any future write skill) runs before staging and committing.
Canonical procedure for pushing changes to the wiki sub-repo when multiple agents may be writing concurrently. The reference implementation at scripts/wiki-write-protocol/protocol.sh handles the optimistic-push-with-retry mechanics (CI-validated on 9 scenarios); this file is the agent-facing procedure that tells…
Use as the FINAL stage of a proposal-to-pr run to record what happened, as one retrospective file under .claude/retrospectives/. Dispatched fresh, having NOT done the work, so it reads artefacts — the pipeline state file, review-evidence.md and its ## Probe — stage 2 score, progress.md, git history — rather than the…
TypeScript library packaging and npm publishing specialist. Use for preparing libraries for npm, generating declaration files, configuring dual packages (ESM/CJS), and managing library releases.
Write-capable worker subagent for the autonomous orchestrator. Implements a plan on a candidate branch, commits, pushes, and returns the candidate.v1 envelope.
Use this agent when validating phase transitions in GitHub Elements workflow. Ensures DEV to TEST to REVIEW order is maintained, checks prerequisites before transitions, and blocks invalid transitions. Use before any phase transition, when validating workflow state, or checking if transition is allowed. Examples…
CI/CD & release-engineering currency expert. Researches latest GitHub Actions, runner images, CodeQL, base-image, and MCP-registry publishing practices on official sources and compares them against this repo's workflows and Dockerfile. Use for the ci slice of a currency review, or ad-hoc "are our workflows/actions…
Review a change against the history of the code it touches. Use git blame and log to catch changes that contradict why the surrounding code exists — reintroducing a fixed bug, removing a guard that was added on purpose, or undoing a deliberate decision. Reports only high-confidence findings backed by a specific past…
3 6d agoA66 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: