القائمة
On-demand WIP risk nudge. Scores the current uncommitted diff for pipeline risk. Use during development to catch high-risk changes before committing.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Deep context-usage analyzer. Runs richer heuristics than run-retro Step 2c — per-turn attribution, per-plugin decomposition, suggestion generation, policy-breach detection. Produces a markdown report at docs/retros/<date>-context-analysis.md with an HTML-comment trailer carrying the bucket-snapshot for delta-from-prior comparison. Auto-fires from run-retro Step 2c when the combined trigger holds (calendar-elapse >14 days OR a bucket changes >20% AND >10 KB, once-per-day guard) per ADR-043 Amendments 2026-06-08 / 2026-06-17; also user-invokable on demand.
Run a session retrospective. Updates docs/BRIEFING.md with learnings and creates problem tickets for failures and friction.
Lightweight problem-capture skill for aside-invocation during foreground work — minimal duplicate-check, skeleton ticket file, single commit per capture (covers new ticket + inline README refresh per P094 per P199 Option 2 amendment 2026-06-05). Defers full duplicate analysis to /wr-itil:review-problems. Use this when the user (or agent mid-iter) wants to capture an observation quickly without disrupting current task flow. For full-intake new-problem creation, use /wr-itil:manage-problem.
Lightweight RFC-capture skill for aside-invocation during foreground work — mandatory problem-trace per ADR-060 I1 invariant, skeleton RFC file by default (or a fully-authored Scope + Tasks under the `--fix-time` flag, per ADR-073), single commit per capture, no inline README refresh. Defers full duplicate analysis and README refresh to /wr-itil:manage-rfc. Use this when the user (or agent) wants to capture an RFC quickly with a clear problem trace. For full lifecycle management, use /wr-itil:manage-rfc.
Declare, triage, mitigate, and close an incident using an evidence-first workflow. Restores service first, then hands off to manage-problem for root-cause work.
Create, update, or transition a problem ticket using an ITIL-aligned problem management workflow with WSJF prioritisation. Supports creating new problems, updating root cause analysis, transitioning status, and closing problems.
استنادا إلى تصنيف SOC المهني
| name | wr-risk-scorer:assess-wip |
| description | On-demand WIP risk nudge. Scores the current uncommitted diff for pipeline risk. Use during development to catch high-risk changes before committing. |
| allowed-tools | Read, Glob, Grep, Bash, AskUserQuestion, Skill |
Run a WIP (work-in-progress) risk assessment on demand. Scores the current uncommitted diff — staged and unstaged — for pipeline risk. Use during development to get early feedback before committing.
This skill is read-only. It does not commit, push, or modify files.
Unlike assess-release, this skill does not pre-satisfy the commit gate. WIP assessment is a development nudge; the pipeline gate is satisfied only by a full wr-risk-scorer:pipeline assessment (via assess-release or a commit attempt).
git add: confirm the uncommitted diff is within appetiteRun the following to capture the current WIP state:
# All uncommitted changes (staged + unstaged, non-binary)
git diff HEAD --stat
# Summary of what's changed
git status --short
If git diff HEAD is empty (clean working tree), report "No uncommitted changes detected" and exit. Do not invoke the subagent with an empty scope.
Build a self-contained prompt for the wip subagent that includes:
git diff HEAD --name-only)Invoke the WIP scorer via the Skill tool. The wr-risk-scorer:wip SKILL is a thin wrapper around the wip agent (per ADR-015 — see packages/risk-scorer/skills/wip/SKILL.md):
skill: wr-risk-scorer:wip
prompt: <constructed assessment prompt from step 2>
Wait for the wrapper to return. The wrapper invokes the wip agent internally and returns the agent's verdict verbatim.
Present the WIP risk nudge to the user. The wip subagent provides guidance and recommendations, not a formal gate score.
Check RISK_VERDICT from the subagent output and handle each case distinctly:
RISK_VERDICT: CONTINUE: changes are in-progress and within risk appetite. Highlight the highest-risk files or change patterns; note whether a full pipeline assessment (assess-release) is recommended before committing.
RISK_VERDICT: PAUSE: risk exceeds appetite. Prominently surface the RISK_REMEDIATIONS: block. Explain each remediation clearly. Do NOT suggest committing until remediations are addressed.
RISK_VERDICT: COMMIT (ADR-016): the uncommitted diff consists entirely of completed governance work (problem fixes, SKILL.md updates, closed problem transitions) and risk is within appetite. Present a prominent commit-now suggestion:
"The uncommitted changes look like completed governance work. Commit now to reduce WIP and feed the pipeline." Reason:
<RISK_COMMIT_REASON from subagent>
Use AskUserQuestion to offer: "Commit completed governance work now?" — Yes (user confirms and runs git commit) or "Not yet" (user defers).
$ARGUMENTS