no-comments SKILL.md skillA
no-comments from axlaser/pitwall is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add axlaser/pitwall/no-comments@git:20261015.15ef6c0Pins git:20261015.15ef6c0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- axlaser/pitwall
- Path
.claude/skills/no-comments/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261015.15ef6c0, committed Oct 15, 2026
- Size
- 5,470 bytes
- Repository stars
- 6
- License
- MIT
Spawn Comment Sicko, or a swarm of them over the whole repo, fix accepted findings, and offer encodings for claimed constraints.
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
# No comments Spawn Comment Sicko. Act on accepted findings. Defer to Comment Sicko's fresh perspective. ## Scope Use the caller's files or diff. Otherwise use the current diff against the base branch, `dev` (`master` when the branch is `dev`), including the working tree. The whole repo (`/no-comments all`, "the repo", "everything") or a directory runs as a swarm. ## Swarm N Comment Sickos in parallel, one slice each, drained into one report and one plan. Open a todolist with one entry per phase before launching anything: Frame, Fan out, Aggregate, Plan. ### Frame 1. Done means every file in scope has an accepted sicko result or is reported as a gap. The artifact is the Plan below. 2. List the files with `git ls-files` over the scope, code only: `*.ts`, `*.tsx`, `*.js`, `*.mjs`, `*.yml`, `*.sh`, `*.ps1`. Count each file's comment lines. 3. The files in scope must have no uncommitted changes (`git status --short -- <files>`), so the swarm's deletions can be reviewed and reverted on their own. Otherwise ask to commit or stash first. …
Read the whole file at its exact version.
How to install
mdr add axlaser/pitwall/no-comments@sha256:a9e812cb641db81eThe line at the top of this page pins the label git:20261015.15ef6c0, 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_7cqt2rb7uij4qpr2)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 15, 2026.
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 (5470 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
axlaser/pitwall · 6 stars · license MIT · pushed 2026-10-17 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_7cqt2rb7uij4qpr2 GET https://markdownregistry.com/api/v1/resolve?ref=axlaser/pitwall/no-comments GET https://markdownregistry.com/api/v1/blob/a9e812cb641db81e683085bd87343b3d91c8130b7b04e732f2aa081508b599f4
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.