claude

mcp-issue-loop

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.

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

Plugin mcp-issue-loop 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 (5)

  • issue-build-loop

    Build one `ai-ready` GitHub issue into a PR and report `build_succeeded` with its `pr` — then stop (CI is the Worker's; the independent review is review-loop's; fixes are rework-loop's; merging is merge-flow's). This loop never responds to reviews and never merges. Repo-agnostic — works whether or n

  • issue-discuss-loop

    Label-triggered loop that thinks an issue through *before* anyone builds it. Label an issue `ai-discussing` and it reads the whole thread, then does one of three things: writes the issue properly when it's a stub, asks questions when it can't yet, or pulls an already-written issue apart antagonistic

  • mcp-review

    The review a loop runs over a change before it reaches a human. Thin orchestration over real reviewer agents: it spawns Anthropic's pr-review-toolkit code-review agents for code quality, and our lightweight security-reviewer agent for vulnerabilities, then merges and confidence-filters the findings

  • review-loop

    The adversarial review of a PR in `ai-reviewing`, fired by the agent-orchestration Worker (route=review-loop) once the PR's CI is green. Starts from nothing but the PR, runs the repo's reviewer (mcp-review by default) on a stronger model than the build, posts what it finds as a real PR review with i

  • rework-loop

    Label-triggered loop that acts on PR review feedback. When a reviewer has left comments and labels the loop-authored PR `auto-reworking`, it reads the feedback, makes the changes, runs a local test gate and an independent code review, pushes and replies to the threads. When there is nothing to push

Subagents (2)

  • README
  • security-reviewer

    Lightweight per-PR security reviewer — threat-models a change's diff and finds real, exploitable vulnerabilities in it, with a concrete exploit path for each. Right-sized for a loop's per-PR gate (not a whole-repo audit — that's the separate periodic claude-security scan). Spawned by the mcp-review

View source on GitHub

More from hifi-phil/umbraco-mcp-ops

All 11 plugins →

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).

4 skills · 1 agent

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

claude-mem

claudecodex

Persistent memory for Claude Code: the next session starts where the last one left off.

29 skills · 1 MCP server · hooks

thedotmack/claude-mem 116,618

context7

claudecodex

Up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your coding agent's context.

1 MCP server

upstash/context7 64,709

mempalace

claudecodex

AI memory system — mine projects and conversations into a searchable palace. 47 MCP tools, auto-save hooks, guided setup.

3 skills · 6 commands · 1 MCP server · hooks

MemPalace/mempalace 60,536

Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer

8 skills · 1 MCP server

ChromeDevTools/chrome-devtools-mcp 55,181

gitnexus

claudecodex

Code intelligence powered by a knowledge graph. Provides execution flow tracing, blast radius analysis, and augmented search across your codebase.

12 skills · 1 MCP server · hooks

abhigyanpatwari/GitNexus 48,482

Maintain mcp-issue-loop?

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