adr
Write an Architecture Decision Record (ADR) for a feature — Context / Decision / Status / Consequences / Alternatives, filed as…
Uncommitted code risk assessment with breaking change detection, blast radius analysis, and scope metrics. Use when: evaluating PR risk, pre-commit risk check, large refactoring review. Not for: security vulnerabilities (use /codex-security), code correctness (use
$ npx -y skills add sd0xdev/sd0x-dev-flow --skill risk-assess --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/risk-assessContext preview
The summary Claude sees to decide when to auto-load this skill.
Uncommitted code risk assessment with breaking change detection, blast radius analysis, and scope metrics. Use when: evaluating PR risk, pre-commit risk check, large refactoring review. Not for: security vulnerabilities (use /codex-security), code correctness (use
name: risk-assess description: "Uncommitted code risk assessment with breaking change detection, blast radius analysis, and scope metrics. Use when: evaluating PR risk, pre-commit risk check, large refactoring review. Not for: security vulnerabilities (use /codex-security), code correctness (use /codex-review-fast). Output: 3-dimension weighted score + risk level + gate."
1. Run `bash scripts/run-skill.sh risk-assess risk-analyze.js --json` to collect deterministic scores 2. Parse the JSON output — overall_score, risk_level, dimensions, flags, gate, next_actions 3. **If risk_level = Critical** (score 75-100) — highlight all breaking signals, recommend splitting PRs 4. **If risk_level = High** (score 50-74) — auto-escalate to `--mode deep`, detail blast radius 5. **If risk_level = Medium** (score 30-49) — summarize dimensions, note areas of concern 6. **If risk_level = Low** (score 0-29) — brief summary, confirm safe to proceed 7. Add qualitative interpretation beyond the scores (e.g., "high blast radius but all dependents are test files")
The script analyzes 3 dimensions + 2 conditional flags:
| Dimension | Weight | What It Measures | |-----------|--------|-----------------| | breaking_surface | 45% | Removed exports, renamed APIs, changed signatures, deleted modules | | blast_radius | 35% | Number of files importing changed modules (grep-based) | | change_scope | 20% | File count, LOC delta, directory span, rename ratio |
| Flag | Trigger | What It Checks | |------|---------|---------------| | migration_safety | Migration/schema files in diff | Rollback/down file exists | | regression_hint | (v2 stub) | Future: git history analysis |
| Score | Level | Gate | Exit Code | |-------|-------|------|-----------| | 0-29 | Low | PASS | 0 | | 30-49 | Medium | PASS | 0 | | 50-74 | High | REVIEW | 1 | | 75-100 | Critical | BLOCK | 2 |
If the script fails, report the error and suggest running manually:
bash scripts/run-skill.sh risk-assess risk-analyze.js --json
## Risk Assessment Report | Field | Value | |-------|-------| | Score | **[N]/100** | | Risk Level | [icon] [level] | | Gate | [PASS/REVIEW/BLOCK] | ### Dimensions [table of dimension scores + weights] ### Breaking Change Signals [list of detected signals — only if any] ### Next Actions [prioritized action items] ## Gate: [sentinel]
Language: English | 繁體中文 | 简体中文 | 日本語 | 한국어 | Español The harness layer for Claude Code. Let the model choose the path. Keep "done" verifiable. Full control plane on Claude Code. Skills-only distribution for Codex CLI and other compatible agents.
Repo: sd0xdev/sd0x-dev-flow
Write an Architecture Decision Record (ADR) for a feature — Context / Decision / Status / Consequences / Alternatives, filed as…
Architecture design and documentation. Produces 3-architecture.md with component diagrams, data flow, integration points, and architecture decisions. Reads…
Context-aware Q&A with auto context gathering. Use when: user has a quick question about codebase, git history, rules, docs, or skills during development. Not…
Industry best practices conformance audit with mandatory adversarial debate. Produces audit artifact: verdict (OK/WARN/FAIL) + gap roadmap + debate proof. Use…
Bug fix workflow. Use when: fixing bugs, resolving issues, regression fixes. Not for: new features (use feature-dev), understanding code (use code-explore).…
Bump package and plugin version in sync. Updates package.json, .claude-plugin/plugin.json, and install-state manifest to the same version. Use when: user says…