wr-risk-scorer:assess-wip

Score uncommitted git diffs for pipeline risk before committing.

4|1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/windyroad/agent-plugins --skill wr-risk-scorer-assess-wip
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wr-risk-scorer:assess-wip
Source: https://github.com/windyroad/agent-plugins/tree/main/packages/risk-scorer/skills/assess-wip
Command: npx skills add https://github.com/windyroad/agent-plugins --skill wr-risk-scorer-assess-wip

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

On-demand WIP risk nudge. Scores the current uncommitted diff for pipeline risk. Use during development to catch high-risk changes before committing.

Core Features & Use Cases

  • Auto-scores the risk of in-progress changes in the working tree to steer development decisions.
  • Provides actionable guidance on which files or changes carry the most pipeline risk.
  • Helpful for early-stage branching and before commit gates to maintain governance.

Quick Start

Run the WIP risk assessment to get a guidance prompt for your uncommitted changes.

Frequently Asked Questions about wr-risk-scorer:assess-wip

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I assess pipeline risk for uncommitted git changes?

Assessing pipeline risk for uncommitted git changes involves analyzing staged and unstaged diffs to generate verdict-based guidance, helping you catch high-risk modifications before committing.

What is a WIP risk assessment in software development?

A WIP risk assessment quantifies the pipeline risk of your current working tree changes, providing early feedback during development to identify high-risk modifications and inform remediation decisions.

Can I score staged and unstaged git diffs before a commit gate?

Yes, you can score staged and unstaged git diffs before a commit gate. The assessment constructs a prompt from git diff output to evaluate pipeline risk and maintain governance.

When should I run a pre-commit risk check on my working tree?

You should run a pre-commit risk check during early-stage branching or right before commit gates to catch high-risk changes, steer development decisions, and maintain pipeline governance.

Does this pipeline risk assessment require any specific dependencies or components?

No specific dependencies or components are required. The Skill operates by constructing a self-contained prompt from your git diff output and delegating the risk scoring process internally.