Use this agent to manage project work using GitHub Issues and the GitHub CLI (gh). The agent creates, edits, and tracks issues; maintains acceptance criteria as checklists; manages labels, assignees, milestones, and Projects; opens/links PRs; and enforces Conventional Commits and a clean Git workflow.
Agente specializzato nella gestione delle operazioni git autorizzate. Gestisce commit, push, merge, tag e consultazione stato repository. Unico agente autorizzato a eseguire comandi git tramite runinterminal. Invocabile manualmente dal dropdown o tramite subagent delegation da git-commit.prompt.md, git-merge.prompt.md…
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
Domain-layer git operations agent. Encapsulates status inspection, diff analysis, staging, commit message construction, rebase, and history traversal as a reusable layer that the git-rebase-stack command delegates to (the git-commit and github-pr skills intentionally handle their git mechanics inline). Performs…
Use this agent when you need to review code changes before committing to GitHub to ensure they follow project guidelines. Examples: Context: User has finished implementing a new feature and wants to commit their changes. user: 'I've finished implementing the WhatsApp bot integration. Can you review the changes before…
Use this agent when the user has made code changes and needs to create a git commit message. This includes:\n\n \nContext: User has just finished implementing a new feature and wants to commit their changes.\nuser: "I've just added user authentication to the app. Can you help me commit this?"\nassistant: "I'll use the…
Haiku utility agent for the drain loop — records runLog entries on hub tasks and performs checkpoint pushes after reviews pass. Touches git and the hub only as instructed.
Triage codex adversarial-review findings, form a minimal fix plan, implement the fixes on the current feature branch, run local verification, commit, and push. Designed to be dispatched once per clodex review iteration with the codex JSON output as input. Returns a structured summary the orchestrator uses to update…
Use this agent when you need to perform any git write operations for the MCP server including commits, pushes, merges, or branch operations. This agent ensures proper MCP server deployment practices and Linear issue tracking. Returns structured data about git operations. Examples: Context: The user has just completed…
Exception-path rectification agent for milestone-pipeline v2. Re-verifies every finding, fixes C/H and small M, records dispositions, reruns checks, and commits locally. It never publishes or self-certifies code-complete; an independent closure verifier runs afterward.
Use this agent when the user has made changes to files and needs to commit them following the project's commit rules. This agent analyzes changes, generates appropriate commit messages, and executes the commit. Examples:\n\n \nContext: User has just finished implementing a new feature and modified several…
Use this agent when code changes have been made and are ready to be committed. It should be triggered before committing to ensure documentation is updated to reflect the changes. This includes updating CHANGELOG, README, and any relevant docs files.\n\nExamples:\n\n- User: "I've finished implementing the new…
Intelligently handles the complete git commit workflow including pre-commit validation, auto-fixes, test validation, and commit retries. Minimizes context usage through efficient iteration and concise summaries.
Version control and pipeline manager for web-mcp. Owns branching strategy, commit standards, review handoff, and release versioning. Creates branches, stages and commits changes with conventional commit messages, and pushes — but never opens a PR or merges into main. Use for any git workflow step: starting work on a…
★not rated 0 15d agoA84 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: