メニュー
Ship-phase subskill for ORC Phase 8. Handles commit, push, and PR file generation from the team's template (pr.md in this folder). Coordination skill: always runs inline. Not for direct user invocation.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/azure-id/orc --skill orc-prコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Did the thing we shipped hold up. Use for "/orc-aftermath", "did that change stick", "what did we ship last month and how did it go", "which runs came back". Read-only and report-only: it grades past runs from the repository's own future — files rewritten soon after, a test we added deleted or skipped, the commit reverted, a promise that was HOLDING now BROKEN — all from git log, ORC's traces and the pact ledger. No vendor, no telemetry, no instrumentation. Churn is a SIGNAL, never a verdict: it reports the signal and its strength, never "this change was bad", and never a person's name.
System Analyst for ORC. Use for "/orc-analyze", "analyze this doc for scope X", or "analyze this requirement against the code" — turning a requirement (a document, PDF by path or pasted, OR a plain-language request) into a precise, code-grounded requirement set BEFORE any planning. Bounds the deliverable to exactly the asked scope, pulls related adjacent scopes in only as anchored "do not build" context, maps each requirement to real files with quote-anchored file:line evidence, and challenges the user with recommended options. Opt-in DEEP mode adds a scout-driven code sweep, verify-every-claim, and alternatives + risks. Also auto-triggers inside /orc on a doc or ambiguous requirement. The orchestrator dispatches this to a subagent — it never analyzes itself.
The lane that says what an agent should NOT try here, and why. Use for "/orc-boundary", "should the agent even attempt this", "where does automation stop in this repo", "why did ORC refuse that". Three verdicts per AREA — EXECUTE, ESCALATE, REFUSE — each derived from four deterministic questions: can the agent verify itself, does it know this area, is the change reversible, and is this a decision rather than a fact. A REFUSE always names what would make it a yes, so "no" is never a shrug. Writes one boundary card per area, consulted in O(1) by every other lane. It gates ORC's own dispatch, never your instructions.
SOC 職業分類に基づく
SKILL.md を表示中
| name | orc-pr |
| description | Ship-phase subskill for ORC Phase 8. Handles commit, push, and PR file generation from the team's template (pr.md in this folder). Coordination skill: always runs inline. Not for direct user invocation. |
../../config.md)stack-gate.md — full /orc + /orc-ultra only).
Measure the change, compare against stacked_pr_loc / stacked_pr_files, and
on a tripped threshold ask the ONE P0 question. "Yes" (with a ticket AND a
resolved PR template) → write stacked-pr/<slug>/STACK-FROM.md and hand off to
/orc-pr-setup → /orc-pr-driver; anything else (under threshold, off,
declined, no ticket, no template) → continue this procedure as one regular PR.target_branch as base.stack_gate: { tripped: bool, loc, files, decision: under-threshold | off |
declined | no-ticket | no-template | handoff, slug } — always present in
full /orc / /orc-ultra; handoff means no PR was created here.The file pr.md in this folder is the team's default PR template. Replace the
placeholder with your real template — the skill reads whatever is there. Template
resolution when it is still the placeholder (project .github/, docs/,
CLAUDE.md, or three recommended options) is
../../../_shared/pr-templates.md — shared with the stacked-PR lanes.