risk-work

Find and fix security, reliability, performance, observability, and maintainability risks in the witwave repository.

2|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/witwave-ai/witwave --skill risk-work-witwave-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: risk-work
Source: https://github.com/witwave-ai/witwave/tree/main/.agents/self/evan/.claude/skills/risk-work
Command: npx skills add https://github.com/witwave-ai/witwave --skill risk-work-witwave-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code that works today can still break under foreseeable conditions — slow upstreams, unbounded growth, unpinned CI tools, or silent failures that are impossible to diagnose in production. This Skill runs a single-pass find-and-fix sweep across five risk categories in the witwave-ai/witwave repo, turning fragile code into committed, tested fixes without manual triage. ## Core Features & Use Cases - Five-category risk taxonomy: Scans for security (CVEs, secrets, insecure patterns), reliability (missing timeouts, retries, unpinned CI tooling), performance (unbounded growth, blocking-in-async), observability (swallowed errors, missing metrics), and maintainability (flag-only structural issues). - Analyzer-driven and pattern-matched detection: Runs govulncheck, gosec, pip-audit, bandit, gitleaks, and trivy for security, plus targeted greps for the four operational categories. - Depth-gated validation and fix-bar: An 8-concern validation gauntlet filters false positives, and a 5-rule fix-bar decides which findings get atomic per-finding commits versus flagged in memory. - Use Case: After an outage, run "fix reliability risks in harness depth 6" to scan the harness section for missing timeouts and silent degradation, auto-fix the safe findings with per-finding commits, and delegate push plus CI watch to iris. ## Quick Start Ask the agent to work risks in the witwave repo, for example by saying "fix risks in operator depth 5" or "find reliability risks in harness".

Frequently Asked Questions about risk-work

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

FAQPage Schema
How do I scan a repo for security and reliability risks automatically?▼

Invoke the skill with a phrase like "fix risks" or "scan for risks", optionally specifying depth, sections, and categories. It runs analyzers such as govulncheck, pip-audit, bandit, and gitleaks for security, plus targeted greps for reliability, performance, and observability patterns.

What risk categories does the risk scan cover?▼

It covers five categories: security (CVEs, secrets, insecure patterns), reliability (missing timeouts, retries, unpinned CI tools), performance (unbounded growth, blocking-in-async), observability (silent failures, swallowed errors), and maintainability (structural coupling, flag-only).

Which findings get auto-fixed versus only flagged?▼

A finding auto-fixes only if it passes all five fix-bar rules: function-body-contained or semver-compatible dep bump, limited blast radius, existing test coverage, severity meeting the depth threshold, and the category gate. Maintainability findings are always flag-only because their fixes are structural refactors.

What does the depth parameter control in a risk scan?▼

Depth (1-10) controls how much context is read per candidate, which categories are surfaced, and how rigorously the 8-concern validation gauntlet is walked. Depth 1-2 covers only Critical/High security findings, while depth 5 and above enables all five categories and Medium-severity auto-fixes.

How are risk findings tracked across runs?▼

Findings are persisted to a shared memory file with [pending], [fixed: SHA], or [flagged: reason] markers, one run section per sweep. Each fix becomes its own atomic commit, and push plus CI watch is delegated to the iris agent with fix-forward semantics.