code-comments SKILL.md skillA
code-comments from douglasjunior/agent-remote-control is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add douglasjunior/agent-remote-control/code-comments@git:20261025.9e7b1fbPins git:20261025.9e7b1fb in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- douglasjunior/agent-remote-control
- Path
.agents/skills/code-comments/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261025.9e7b1fb, committed Oct 25, 2026
- First version recorded
- Sep 25, 2026
- Size
- 4,950 bytes
- Repository stars
- 10
- License
- MIT
Defines when a comment is allowed and when it is noise in TypeScript and NestJS code. Eliminates obvious comments that repeat the code, section headers, explained imports and narration of past edits. Establishes the three-question test and the mandatory pruning pass before closing the task. Use when creating, editing or reviewing .ts, .json or YAML files.
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
# Source code comments > **Maintaining this skill** > > Update this document whenever **any rule described here** changes. The criterion is not > *which* rule — it is the nature of the change: the project's comment policy changed → > update; a technical refactor that preserves the described policy → leave it alone. This rule applies to the whole repository, in every TypeScript source file (`*.ts`), configuration file (`*.json`, `*.yaml`) and script. ## A comment is the exception, not a habit Avoid comments unless they are strictly necessary to explain a non-intuitive decision, an external technical constraint, a tradeoff or context that cannot be reached by reading the code alone. The code must be self-explanatory through expressive names, strict types and cohesive abstractions. Correct — explains external context and a constraint the code does not express on its own: ```typescript /* * The ACP SDK requires the cwd to be sent normalized in POSIX format to avoid * path resolution failures on Windows platforms and containerized environments. */ const normalizedCwd = cwd.replace(/\\/g, '/'); ``` Avoid — merely repeats the visible mechanics of the code: ```typescript …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_lf6zfb5rbguhqzni/fdaa922c4a9b52094711c1c9afd38a4a3fef9da72ccf538e9b1065dde547b876.json
Then /plugin install code-comments@markdownregistry-lf6zfb5rbguhqzni in Claude Code. It installs git:20261025.9e7b1fb, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add douglasjunior/agent-remote-control/code-comments@sha256:fdaa922c4a9b5209The line at the top of this page pins the label git:20261025.9e7b1fb, 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_lf6zfb5rbguhqzni)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in douglasjunior/agent-remote-control/code-comments since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of code-comments from somewhere else? Ask it: where did my code-comments come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 2 versions of this file, between Sep 25, 2026 and Oct 25, 2026, about one every 30 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261025.9e7b1fb latest | 2026-10-25 | 9e7b1fb | 4,950 B | A | view · diff |
| git:20260925.971e044 | 2026-09-25 | 971e044 | 5,265 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/code-comments/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (4950 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
douglasjunior/agent-remote-control · 10 stars · license MIT · pushed 2026-11-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_lf6zfb5rbguhqzni GET https://markdownregistry.com/api/v1/resolve?ref=douglasjunior/agent-remote-control/code-comments GET https://markdownregistry.com/api/v1/blob/fdaa922c4a9b52094711c1c9afd38a4a3fef9da72ccf538e9b1065dde547b876
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 douglasjunior/agent-remote-control
Every file in douglasjunior/agent-remote-control
Other files named code-comments
Browse by kind, by grade A, or by owner.
Kept in .agents/skills, the folder Codex reads. More agent skills for Codex.