claude

release-flow

Branching, merge, release, and dev-sync workflow skills for any repo — detects gitflow (dev + main) vs main-only and follows the matching conventions. Bundles release-and-branching, sync-dev, and auto-release-loop (issue+label-triggered release with two automated gates — green CI + an Opus pre-publish review against a growing checklist — no approval pause).

2 on GitHubby Phil Wv2.2.5MITupdated 19 days agoworkflow
/

Plugin release-flow from marketplace umbraco-mcp-ops in hifi-phil/umbraco-mcp-ops. Commands read from the repo's manifest — 19 days ago.

What it installs

Skills (4)

  • auto-release-loop

    Event-triggered release preparation with NO mid-flow human approval, guarded by two automated gates: green CI, then an Opus pre-publish review against a growing checklist. When an issue titled `release <version>` is labelled `auto-releasing`, this cuts the release branch, bumps version files + chang

  • release-and-branching

    Branching, merge, and release workflow for any repo. Detects whether the repo uses a two-branch gitflow (dev + main) or a simpler main-only model, then follows the matching conventions for branch naming, squash vs merge-commit, cutting a release, and tagging. Use whenever creating a branch to do wor

  • release-publish

    The after part of a release: once the orchestrator has merged the release PR, wait for the repo's own tag, post the release note, merge <main> back into <dev> through a PR, and report release_published with the tag. A small, mostly mechanical run, fired only by the agent-orchestration Worker (route=

  • sync-dev

    Move to the repo's main worktree, switch to the `dev` branch, and pull latest. Use when the user says "move/go back to dev", "switch to dev and pull", "get latest on dev", or otherwise wants the main worktree reset to an up-to-date dev branch.

Subagents (1)

  • release-reviewer

    Pre-publish reviewer for auto-release-loop (Step 2.5). Given a release PR's already-fetched facts and the pinned content of the files it changed, it checks the PR against the release-review-checklist AND reasons about whether anything looks wrong or risky to ship, then returns VERDICT: PASS, VERDICT

View source on GitHub

More from hifi-phil/umbraco-mcp-ops

All 11 plugins →

Label-driven loops that take an issue from rough idea to merged PR: `ai-discussing` talks it into shape before anyone builds it, `ai-ready` builds it to a PR, `auto-reworking` acts on your review feedback. Bundles issue-discuss-loop, issue-build-loop, rework-loop, and mcp-review. Fired by the agent-orchestration Worker as a cloud routine. Repo-agnostic.

5 skills · 2 agents

2

Iteratively trims a Claude Code skill (SKILL.md + its bundled resources) down to exactly what it needs — repeated review/fix rounds against a concrete duplication-and-bloat checklist, with a fresh independent reviewer each round, until two consecutive rounds find nothing left to change (or a hard cap is hit and reported as non-convergence, never silently accepted). Bundles the skill-tighten skill and its read-only skill-tightener-reviewer agent.

1 skill · 3 agents

2

Shared skill for writing the structured outcome artifact a loop appends to a comment it already posts, so the agent-orchestration Worker can read what happened and apply the labels itself. One marker format, one growing catalog of outcome shapes; loop plugins point here instead of each inventing their own. Loops report through post-outcome.sh, which signals the agent-orchestration Worker and prints the exact comment body to post. Bundles hooks that signal it too: heartbeats naming the step while a loop works, blocked on a permission prompt, and ended when a session stops without reporting (AGENT_OUTCOMES_ENDPOINT + AGENT_OUTCOMES_TOKEN; without the endpoint they send nothing). Also bundles the work-log skill: how a loop records its decisions and what it verified in the Worker's decision log and build log, with log-entry.sh to add and read entries.

2 skills · hooks

2

Single front door for a repo's automation loops so one routine per repo can handle every loop event instead of one routine per event. Deterministically routes each triggering GitHub event to the matching loop (via route-event.sh); a non-matching event is a quiet no-op. Router only; each loop owns its guardrails. Also bundles new-loop-routine — the standard config + canonical prompts + UI wiring for standing up one routine per repo. Requires github-ops + the loop skills.

3 skills

2

The self-learning system shared by every automated loop in this repo. SubagentStop/SessionEnd hooks capture proto-learnings — raw observations worth improving — as rows on a shared Slack canvas (not GitHub issues, which silently lose captures across an org boundary). The hooks fire for any loop, matching on shared conventions (github-ops, /goal) rather than naming individual loops, so a new loop needs no integration here. Bundles two separate skills: proto-learning-capture (reference for the capture half and its row schema) and triage-learnings (Loop B), which weekly dedupes/clusters the canvas inbox and routes each cluster to a tracked issue on the owning MCP repo, a gated PR to the shared umbraco-mcp-skills, or a loop-improvement issue on this repo. Install alongside any loop plugin to get capture for free.

2 skills · hooks

2

Two halves, deliberately separate. The branch-housekeeping SKILL reports the state of the remote branches across every configured Umbraco MCP repo in one run and posts a Slack digest — classifying each non-protected branch by its GitHub PR state (authoritative where git ancestry isn't, since these repos squash-merge) into safe-to-remove, merged-but-reused-since, closed unmerged, no PR, and open. It is informational and read-only — never deletes — so it needs no write scope and runs as a scheduled CLOUD routine as well as locally. The /clean-branches COMMAND is the separate, deliberate cleanup: a purely mechanical script with no model in the loop, which re-verifies every branch against the API — protected lists, live default branch, live protection, merged_at, and that the tip still matches what the PR merged — before deleting it. Run it only when you want branches gone. The command is LOCAL-ONLY — the GitHub MCP server exposes no branch-delete tool, so cleanup cannot be scheduled at all. Also flags any repo whose "Automatically delete head branches" setting is off, which is the durable fix cleanup only works around.

1 skill · 1 command

2

Similar plugins

superpowers

claudecodex

Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques

15 skills · hooks

obra/superpowers 316,836

Perform AI code review on Git diffs — supports workspace changes, branch ranges, and single commits with concurrent per-file analysis, codebase search, and deep context-aware review.

2 commands

alibaba/open-code-review 50,068

Backend API design, GraphQL architecture, workflow orchestration with Temporal, and test-driven backend development

9 skills · 1 command · 8 agents

wshobson/agents 42,461

beads

claudecodex

AI-supervised issue tracker for coding workflows

1 skill · 1 agent · hooks

gastownhall/beads 28,698

MiniMax AI skills library for frontend, fullstack, Android, iOS, shader, GIF sticker, document, presentation, spreadsheet, and multimodal media workflows

18 skills

MiniMax-AI/skills 13,828

worktrunk

claudecodex

Worktrunk is a CLI for Git worktree management, designed for parallel AI agent workflows. This plugin provides configuration guidance (LLM commit messages, project hooks, worktree paths), automatic activity tracking (🤖/💬 indicators in `wt list` showing active Claude sessions), and a `/wt-diff` pane showing each worktree's changes.

2 skills · hooks

max-sixty/worktrunk 12,481

Maintain release-flow?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins11 plugins