ops-rework-loop

Label-triggered loop that acts on PR review feedback. When a reviewer has left comments and labels a PR `ops/auto-rework`, it reads every actionable point, commands `ops-change · implement` scoped to that feedback and `ops-change · verify`, pushes, replies on the threads, re-requests review, and clears the label — then stops. It never waits for CI and never merges: it hands the PR back so there is one merge path behind one human gate. Runs in a cloud routine or locally. Trigger: a PR labelled `ops/auto-rework`, or "rework PR #N".

インストールへ移動

リポジトリ: umbraco/umbraco-ai-ops
ソースの最終更新活動: 2026年7月28日 10:58
検出された SKILL.md の言語: 英語
スター: 1
フォーク: 0

インストール方法

デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。

npx skills add https://github.com/umbraco/umbraco-ai-ops --skill ops-rework-loop

コマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。

ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。

ソースファイルを確認

インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。

SKILL.md

ソースの指示 · 読み取り専用プレビュー

検索に戻るインストールに戻る

ops-install

Onboard a repo to the engine, and prove it is covered. Detects the repo's setup, writes the facts detection cannot reach to `.claude/ops-repo-meta.json`, reports capability coverage against the catalog (present / inherited / missing), scaffolds a stub for every missing capability from its catalog entry, asks whether each INHERITED default actually fits (coverage matches names, not behaviour), interviews the human to fill that stub's TODOs, creates every `ops/` label on the repo its role implies, installs the caller workflow on every repo that emits routed events, and validates the routing overlay. It checks its OWN version first, because onboarding with a stale installer wastes time on bugs already fixed. Seven of its ten steps are deterministic scripts. Interactive, run once per repo. Trigger on "onboard this repo", "install the ops engine", "check capability coverage".

2026-07-30

ops-repo-meta

Ambient facts about this repo and its family, returned as structured data: `identity` (repo, default branch, the trigger labels), `topology` (which repo fills the `code` / `issues` / `releases` / `learnings` role), and `lines` (the live version lines, which is primary, and the port direction). The framework default detects what it can and reads a repo's declared facts; a repo that has facts detection cannot reach ships its own `ops-repo-meta` instead. Called by name with (action, context-json) . NOT for direct use — never select it from a description match.

2026-07-29

ops-port-loop

Land a change that has already shipped on one line onto this repo's other live lines. Fired by the port label on a merged PR, or by `ops-merge-loop` straight after it lands one. Works out the target lines from the repo's declared port order — never from a branch name a human typed — and drives each one through the repo's own `ops-change` as a real change with its own verify and CI. It never lands a port: each gets the same human gate as any other PR. Trigger via loop-dispatch on Pull request: Labeled `ops/port`.

2026-07-29

このリポジトリのすべてを見る

name

ops-rework-loop

description

ops-rework-loop

The review-response half of the issue loop, split out so it can be event-driven. ops-issue-loop takes a ready issue to a CI-green PR and stops. When a reviewer reviews that PR and labels it ops/auto-rework, this loop addresses the feedback — closing the write → review → rework → land chain with no long-lived "watch my review" session.

Like the issue loop, it owns orchestration, not build steps. The editing is ops-change, which the repo provides. This loop only sequences: read feedback → change, scoped → verify → push → reply → clear the label.

It does not land its own fix. It hands the PR back to the human, who applies the landing label, and ops-merge-loop lands it. One merge path, one human gate — a rework loop that merged its own work would have quietly created a second of each.

What it calls

Capability · action	Why	Visibility
`ops-change · implement`	make the changes the review asked for	service
`ops-change · verify`

ops-rework-loop

インストール方法

ソースファイルを確認

ops-rework-loop

What it calls

ops-rework-loop

What it calls

Trigger and scope

CI is asynchronous, and this loop never waits for it

Step 1 — read the feedback

Step 2 — change it, scoped

Step 3 — push, reply, clear the label

Guardrails

Running as a routine

ops-rework-loop

ソース情報

インストール方法

ソースファイルを確認

このリポジトリの他の Skills

このリポジトリの他の Skills

ops-rework-loop

What it calls

ops-rework-loop

What it calls

Trigger and scope

CI is asynchronous, and this loop never waits for it

Step 1 — read the feedback

Step 2 — change it, scoped

Step 3 — push, reply, clear the label

Guardrails

Running as a routine