check SKILL.md skillA
check from varun-singhh/lfg is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add varun-singhh/lfg/check@git:20261024.eedafdaPins git:20261024.eedafda in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- varun-singhh/lfg
- Path
plugin/skills/check/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261024.eedafda, committed Oct 24, 2026
- First version recorded
- Oct 15, 2026
- Size
- 5,336 bytes
- Repository stars
- 10
- License
- MIT
The green gate: fixes lint (never suppresses), type-checks, runs affected tests then the full suite, builds like CI, replays CI locally and reads the branch's GitHub CI status read-only. Use when the user says "is it green?", "run the checks", "fix the lint", "will CI pass?", or after /build or /fix finishes and before /review-coach or /ship.
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
# /check: get to green, honestly ## Step 0: preflight 1. `lfg graphs ensure`. Non-zero exit: stop and show its output. Continue on a stale graph only if the user typed `--allow-stale`. 2. `lfg run path`. Exit 1 (no current run): `lfg run new check-<branch-slug>`. 3. `lfg rule graph-first` and follow it for every lookup below. ## Steps 1. **Scope the change.** `detect_changes_tool` on the working tree (uncommitted work included) → the changed nodes. Note the lane from `tasks.json` or `lfg lane --json`. 2. **Lint, fixed by hand.** Run the repo's lint/format autofix command (from `~/.lfg/repos/<repo-id>/commands.json`, else the repo's own scripts). Then fix every remaining error and warning in the touched files by editing the code. The fix is always in the code: the lint config, rule list and inline directives stay as they were. 3. **Types.** Run the repo's type-check command. Fix every error at its cause. 4. **Affected tests first.** For each changed node: `query_graph_tool` with `tests_for`. Run just those tests for fast feedback. Changed nodes with no test → record as **untested** (gate 2) and tell the user; write the missing test if the seam is agreed in `tasks.json`. …
Read the whole file at its exact version.
How to install
mdr add varun-singhh/lfg/check@sha256:c8d7c2e8af4bdee2The line at the top of this page pins the label git:20261024.eedafda, 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_wmbje3ds2bvco4gt)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Oct 15, 2026 and Oct 24, 2026, about one every 3 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261024.eedafda latest | 2026-10-24 | eedafda | 5,336 B | A | view · diff |
| git:20261022.72a0719 | 2026-10-22 | 72a0719 | 5,324 B | A | view · diff |
| git:20261020.f1b0c39 | 2026-10-20 | f1b0c39 | 4,841 B | A | view · diff |
| git:20261015.6b3a06b | 2026-10-15 | 6b3a06b | 4,464 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 (5336 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
varun-singhh/lfg · 10 stars · license MIT · pushed 2026-10-26 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_wmbje3ds2bvco4gt GET https://markdownregistry.com/api/v1/resolve?ref=varun-singhh/lfg/check GET https://markdownregistry.com/api/v1/blob/c8d7c2e8af4bdee2424541ee699cd6c4031fe737009e221a7d67ec786edfe6b3
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 varun-singhh/lfg
Every file in varun-singhh/lfg