pre-push-gate-debugging SKILL.md skillB
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
pre-push-gate-debugging from arasz/ai-badger is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add arasz/ai-badger/pre-push-gate-debugging@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- arasz/ai-badger
- Path
features/common/skills/pre-push-gate-debugging/SKILL.md- Versions recorded
- 4
- Latest version
- v1.0.0, committed Sep 11, 2026
- First version recorded
- Aug 7, 2026
- Size
- 10,777 bytes
- Repository stars
- 3
- License
- MIT
Use when a pre-push quality gate blocks git push or a lane fails: read the gate's own logs first (reproduce one lane), run single lanes for fast iteration, test the working tree you intend to push, handle E2E/infra cross-run state contamination, worktree node_modules gotchas, and build a manual repro harness when lane output hides the real error.
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
# Pre-push verification gate debugging Repos with heavy local gates block `git push` until every lane passes (lefthook pre-push hook calling a verify script that runs docs, unit, E2E, infra and frontend lanes). This skill is for operating and debugging that gate without burning whole-gate cycles. The methods here are generic; keep a repo-specific playbook beside the gate script (lane list + commands, log layout, repro steps) as this skill's reference when one exists. ## Detect and understand the gate - `lefthook.yml` → `pre-push` → `script` + `runner` (+ `root`). Read the script's header comments FIRST: usage, lane names, exit codes, env vars (`VERIFY_MODE`, `VERIFY_SKIP`), self-test, and the "reproduce / bypass / logs" failure contract. - A blocked push ends with `🥊 quality gate (Ns)` and `exit status 1`. The hook buffers lane output — never diagnose from the push output alone. ## Workflow 1. **Read the gate's own logs first.** The failure block prints: - `reproduce: bun <script> <lane>` — run exactly this to re-run one lane (minutes, not the whole gate). - `logs: <dir>/<lane>.log` — the lane's full output; `<dir>/progress.log` is the run timeline …
Read the whole file at its exact version.
How to install
mdr add arasz/ai-badger/pre-push-gate-debugging@sha256:6a8ef7759e60ccdaThe line at the top of this page pins the label v1.0.0, 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_xnj5bl53bvg3nh3l)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Aug 7, 2026 and Sep 11, 2026, about one every 12 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-09-11 | c8da0f0 | 10,777 B | B | view · diff |
| v1.0.0 | 2026-08-08 | 9006bf5 | 10,775 B | B | view · diff |
| v1.0.0 | 2026-08-07 | 7cebf20 | 10,762 B | B | view · diff |
| git:20260807.bfbf1be | 2026-08-07 | bfbf1be | 10,567 B | B | view |
Audit of the latest version
- fail: No script tag (matched: <script)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (10777 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
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
arasz/ai-badger · 3 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_xnj5bl53bvg3nh3l GET https://markdownregistry.com/api/v1/resolve?ref=arasz/ai-badger/pre-push-gate-debugging GET https://markdownregistry.com/api/v1/blob/6a8ef7759e60ccda768b078d501ec505754e4c904f5052cf134ee2af2b8db037
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.