Menu

Individual skill

chaos-code-risk-scan

0upvotes

Scan a source code repository for resilience risks that a Harness chaos experiment can prove (outbound calls without timeouts, retries without backoff, missing graceful shutdown, health checks that mask dependency state, unbounded queues and pools, local state), map each one to a generic SourceCode risk rule, and report them to Harness as a CodeRepository risk scan. Use when the user asks to scan a repo or service code for resilience or chaos risks, or wants code findings they can verify with chaos experiments. Do not use for manifest or pipeline risk scans (those run in Harness), to create or run chaos experiments (use chaos-experiment), or for security or code quality review. Trigger phrases: scan this repo for resilience risks, chaos code scan, find chaos-provable risks, code risk scan, resilience review of this service.

skills/observability-governance/chaos-code-risk-scan/SKILL.md

Read pinned source

Source commit e01dc7275f7e261f390be2fe7be4559feadb74ef

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
134
Repository last updated
Oct 28, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Chaos Code Risk Scan

Find resilience risks in a repository that a chaos experiment can turn into a
pass/fail result, and send them to Harness as a `CodeRepository` risk scan.
Harness then scores them, adds them to the scan report and, for modules linked
to a chaos service, recommends experiments.

The work is split so evidence cannot be invented: scripts extract facts and
verify snippets; you only map verified facts to rules and write the
explanation; the server re-validates everything.

One prompt runs the whole flow. Do not ask the user to choose an org, project, module,
service, rule, or to approve a create or a submit. The only stops are a missing
`origin` remote, or a tool error that a single retry does not clear. Report those
Back to top