workflow-green-repo SKILL.md skillA
workflow-green-repo from kensaurus/cursor-kenji is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add kensaurus/cursor-kenji/workflow-green-repo@git:20260923.68c095ePins git:20260923.68c095e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- kensaurus/cursor-kenji
- Path
skills/workflow-green-repo/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260923.68c095e, committed Sep 23, 2026
- First version recorded
- Aug 17, 2026
- Size
- 7,515 bytes
- Repository stars
- 9
- License
- MIT
Drive a repository to a green baseline — typecheck, lint, tests, and build passing from a clean checkout — when fixing is authorized. Use when "make the repo green", "get CI passing", or "fix all the failing tests".
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# workflow-green-repo — Whole-Repository Greening **Degree of freedom: MIXED.** Root-cause of each failure `[HIGH freedom]`; gate discovery, worklist, and no skip/silence `[LOW freedom — run exactly]`. Bring the repository to a verified-green baseline: every configured health gate passes from a clean state. This is broad, authorized cleanup — the one place where fixing unrelated pre-existing failures is the goal, not scope creep. > **Green is defined by a fresh from-scratch run of every gate, not by the > failures you happened to see.** Enumerate first, externalize the worklist, > fix root causes in batches, and re-run until zero. ## How to reason 1. **Authorize** — whole-repo green was explicitly asked 2. **Enumerate** — real commands + baseline failures, not assumed 3. **Fix-root** — no skip, narrow, or ignore 4. **Prove** — fresh from-scratch run of every gate ## Worked example > **Authorize:** user said "get CI passing on this repo." > **Enumerate:** `pnpm typecheck` 14 errors in `lib/billing`; `pnpm test` 3 failures on date TZ. > **Fix-root:** restore the `Invoice` discriminant the last refactor dropped; fix TZ in the test clock, do not `.skip` the suite. …
Read the whole file at its exact version.
How to install
mdr add kensaurus/cursor-kenji/workflow-green-repo@sha256:ee81c0c05b4c756eThe line at the top of this page pins the label git:20260923.68c095e, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_dl6zrftgoidhaed3)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Aug 17, 2026 and Sep 23, 2026, about one every 9 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260923.68c095e latest | 2026-09-23 | 68c095e | 7,515 B | A | view · diff |
| git:20260923.cf348bd | 2026-09-23 | cf348bd | 7,593 B | A | view · diff |
| git:20260821.2a41031 | 2026-08-21 | 2a41031 | 7,229 B | A | view · diff |
| git:20260818.5be6466 | 2026-08-18 | 5be6466 | 5,862 B | A | view · diff |
| git:20260817.5b93a21 | 2026-08-17 | 5b93a21 | 5,814 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 (7515 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
kensaurus/cursor-kenji · 9 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_dl6zrftgoidhaed3 GET https://markdownregistry.com/api/v1/resolve?ref=kensaurus/cursor-kenji/workflow-green-repo GET https://markdownregistry.com/api/v1/blob/ee81c0c05b4c756e6140213a40fbb88113cde8862ebbc3e2bcb86d41424a3278
Your AI assistant 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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from kensaurus/cursor-kenji
Every file in kensaurus/cursor-kenji