crap-analyzer skillA
crap-analyzer is agent-read markdown (skill) from swingerman/engineer: Use to produce a risk-based refactor + test plan for recently-changed code on a diff/branch/PR by computing CRAP (complexity × untested) on changed methods. Multi-language — TypeScript, JavaScript, Python, Java, Kotlin, Go, Ruby, C#, Rust, PHP — auto-discovers how the repo generates coverage. Triggers — "/crap-analyzer", "analyze CRAP", "compute CRAP", "find risky methods", "find complex untested methods"..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# CRAP Analyzer CRAP (Change Risk Anti-Patterns) flags functions that are both **complex** and **poorly tested** — the worst-risk code to ship. ``` CRAP(m) = comp(m)² × (1 − cov(m))³ + comp(m) ``` This skill scopes analysis to a diff, ranks findings worst-first, and turns each finding into a concrete refactor + test-stub proposal. ## Workflow 1. **Determine the diff.** First that works: - `gh pr diff` / `gh pr diff <number>` if a GitHub PR is referenced. - `git diff --merge-base <main-branch>` — detect the main branch with `git remote show origin | grep 'HEAD branch'`. - `git diff --cached` for staged changes. - `git diff HEAD~N..HEAD` for a named commit range. - Explicit file list if the user names files. Pipe the diff to `scripts/compute_crap.py --diff -`. 2. **Locate or generate coverage.** Let the script auto-discover coverage files first (lcov, Cobertura, JaCoCo, Clover, Go `coverage.out`, coverage.py JSON). If nothing is found, follow [references/coverage-discovery.md](references/coverage-discovery.md) to detect the toolchain, then ask before running it. On decline, proceed with coverage=0% and flag it in the report header. 3. **Run the analyzer.** …
Read the whole file at its exact version.
How to install
mdr add swingerman/engineer/crap-analyzer@git:20260525.78c79demdr add swingerman/engineer/crap-analyzer@sha256:7ad02cce7eed634cPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_jv2e5trxeuxiuvb5)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260525.78c79de latest | 2026-05-25 | 78c79de | 4,792 B | A | view · diff |
| git:20260514.b485f22 | 2026-05-14 | b485f22 | 4,785 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4792 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
swingerman/engineer · 150 stars · license MIT · pushed 2026-09-22 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_jv2e5trxeuxiuvb5 GET https://markdownregistry.com/api/v1/resolve?ref=swingerman/engineer/crap-analyzer GET https://markdownregistry.com/api/v1/blob/7ad02cce7eed634ca3dcd514e4d6538703d83a6ef7ddb1510baaae8d2eb2169b
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.