Agent skill

Ccsn No Comments

by kenryu42 in kenryu42/cc-safety-net

Use in the cc-safety-net repo when bun run lint:comments or bun run check reports a comment, a stale comment-allowlist entry, or a file it cannot parse, and before writing a code comment there.

MITAuto-check passedDevelopment

Install Ccsn No Comments

skills CLI
$ npx skills add kenryu42/cc-safety-net --skill ccsn-no-comments -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install kenryu42/cc-safety-net ccsn-no-comments --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/kenryu42/cc-safety-net.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/ccsn-no-comments .claude/skills/ccsn-no-comments && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
ccsn-no-comments
GitHub stars
1.6k
Token cost
~907 tokens
SKILL.md length
534 words
Files
2
Skills in repo
5
Repo updated
First seen
Licence
MIT

At a glance

Use in the cc-safety-net repo when bun run lint:comments or bun run check reports a comment, a stale comment-allowlist entry, or a file it cannot parse, and before writing a code comment there.

  • Tasks that involve Pull requests
  • SKILL.md covers Each Reported Comment, Allowed Directives, Other Failures and Never Dodge The Check, plus 1 more section
  • Calls bun and git
  • Tasks that involve Technical documentation

What it does

Ccsn No Comments is an agent skill from kenryu42/cc-safety-net. Use in the cc-safety-net repo when bun run lint:comments or bun run check reports a comment, a stale comment-allowlist entry, or a file it cannot parse, and before writing a code comment there. Moves what each comment says into code, a test, or the PR description instead of deleting it and losing it.

Its SKILL.md is about 910 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Development, covering Pull requests, Technical documentation and Linting and formatting. It works with Git. The repository describes itself as: A pre-execution guard for AI coding agents. It blocks destructive Git and file system commands, plus common attempts to access sensitive files, before a tool call runs. Supports… The licence is MIT.

When your agent uses it

  • Tasks that involve Pull requests
  • Tasks that involve Technical documentation
  • Tasks that involve Linting and formatting

Example prompts

  • “/ccsn-no-comments”

What it can do on your machine

Read from SKILL.md and the folder at commit 2615848. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • bun
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Ccsn No Comments loads about 907 tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 534 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~81
When it runs · the whole SKILL.md, loaded when a task matches
~907

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from kenryu42/cc-safety-net at commit 2615848, republished under its MIT licence (© kenryu42). 534 words, ~907 tokens.

Download SKILL.mdSave it as .claude/skills/ccsn-no-comments/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
ccsn-no-comments
description
Use in the cc-safety-net repo when `bun run lint:comments` or `bun run check` reports a comment, a stale comment-allowlist entry, or a file it cannot parse, and before writing a code comment there. Moves what each comment says into code, a test, or the PR description instead of deleting it and losing it.

Fixing CC Safety Net Comment Failures

bun run lint:comments, part of bun run check and CI, rejects code comments. The lazy fix, deleting the comment, loses what it said. For each reported comment, decide which kind it is and move what it says to where that kind belongs. The Comments and Style Guide sections of AGENTS.md govern.

Each Reported Comment

  • Narration that restates the code, and commented-out code: delete it. The code already says the first, and git keeps the second.
  • An explanation of surprising behavior in this repo's own code: make the code say it with a clearer name, a named value or local boolean, or a type, then delete the comment. The Style Guide forbids a single-use helper function just to carry a name; name a value or condition inside the function instead, which the Style Guide allows even when it is used once.
  • A claimed constraint ("do not remove", "IMPORTANT", "must", a justification for a workaround): leave the code's behavior as it is, and check the claim before trusting it. Read git blame -L <start>,<end> <file> and the commit it points to, run git log -p -S '<distinctive fragment>' -- <file>, and search tests/ for a test that pins it. A constraint you confirm gets a test or a type when that is cheap: remove the workaround, see the new test or type check fail, then restore it. Otherwise, or when you cannot confirm or rule it out, state the claim and what you found in the PR description. The comment goes either way.
  • A fact about an external tool (git, POSIX shell, the OS, Bun, Node, a host agent) that code cannot express: remove it from the code, and put the fact and its source (documentation link, version, or commit) in the PR description. Only the maintainer adds entries to scripts/comment-allowlist.json; never add one or change its text.
Show full SKILL.md (223 more words)Show less

Allowed Directives

The check accepts exactly three comments without an allowlist entry:

  • a bare /** @internal */ with nothing else in it, for a test-only export (see the Knip section of AGENTS.md);
  • // oxlint-disable-next-line <rules> -- <reason>, with comma-separated rule names and a non-empty reason;
  • // @ts-expect-error <reason>, with a non-empty reason.

Before writing a lint suppression, check whether the rule is catching a real bug. If it is, fix the code instead.

Other Failures

  • cannot be parsed: fix the syntax error first, then rerun before acting on anything else reported for that file. The check misses comments after the error, so a stale entry for that file may be false.
  • stale entry for <path>: the entry's exact text is no longer a comment in <path>. If the check also reports that comment in <path> with edited text, restore the entry's exact text. If it reports the entry's exact text in another file, you moved the comment or renamed its file: keep the comment and the entry, and stop and ask the maintainer to move the entry. Otherwise the comment is gone: delete the entry from scripts/comment-allowlist.json.

Never Dodge The Check

  • Do not move comment text into strings or string constants.
  • Do not edit scripts/check-comments.ts to let a comment through.

Finish

Run bun run lint:comments until it passes, then run bun run check once as the final check.

© kenryu42, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .agents/skills/ccsn-no-comments of kenryu42/cc-safety-net.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 2615848

Compare with similar skills

Ccsn No Comments next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Ccsn No Comments compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Ccsn No Comments this skillkenryu42/cc-safety-net1.6k—~907Automated safety check: PassMIT
Lint Commit PRTresjs/tres3.8k—~1.1kAutomated safety check: PassMIT
PR Pushicebear0828/codex-proxy1.8k—~2.2kAutomated safety check: NotesCustom licence
PR Pushicebear0828/codex-proxy1.8k—~2.3kAutomated safety check: NotesCustom licence
Adk Setupgoogle/adk-python22k—~993Automated safety check: NotesApache-2.0
Check Pushpockethost/pockethost1.4k—~665Automated safety check: PassMIT

Similar skills

  • Lint Commit PR

    Tresjs/tres

    Lint local changes, auto-fix, conventional commit, and optionally create PR

    3.8k GitHub stars~1.1k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • PR Push

    icebear0828/codex-proxy

    Package the current working changes into a standards-compliant codex-proxy pull request: branch hygiene, commit message linting, CHANGELOG prompt, conventional commit, push, and gh pr create against…

    1.8k GitHub stars~2.2k tokensUpdated today
    DevelopmentAuto-check: notes
  • PR Push

    icebear0828/codex-proxy

    Package the current working changes into a standards-compliant codex-proxy pull request: branch hygiene, commit message linting, CHANGELOG prompt, conventional commit, push, and gh pr create against…

    1.8k GitHub stars~2.3k tokensUpdated today
    DevelopmentAuto-check: notes
  • Adk Setup

    google/adk-python

    Official

    Sets up a local ADK Python development environment in a git clone of the open-source adk-python repository: a uv virtual environment, all dependency extras, pre-commit hooks, and a first unit-test…

    22k GitHub stars~993 tokensUpdated today
    DevelopmentAuto-check: notes
  • Check Push

    pockethost/pockethost

    Run pnpm check:push (lint, types, tests) before git push or PR-ready work.

    1.4k GitHub stars~665 tokensUpdated 10 days ago
    DevelopmentAuto-check passed
  • Openqodex

    openqodex/openqodex

    Code review for the current change, before it is pushed. An agent skill from openqodex/openqodex.

    303 GitHub stars~1.9k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from kenryu42/cc-safety-net

  • Release Notes

    kenryu42/cc-safety-net

    Generate and publish concise, evidence-based notes in the body of the latest existing GitHub Release.

    1.6k GitHub stars~3.2k tokensUpdated today
    Auto-check passed
  • Verify Cc Safety Net

    kenryu42/cc-safety-net

    Launch and drive the real cc-safety-net CLI — the hook decision path, explain, status/doctor, logs, and the local policy GUI — against an isolated home, capturing evidence.

    1.6k GitHub stars~2k tokensUpdated today
    Auto-check passed
  • Cc Safety Net

    kenryu42/cc-safety-net

    Operate CC Safety Net: explain why a command was blocked, triage false positives, configure custom rulebooks, manage agent CLI integrations, and diagnose protection.

    1.6k GitHub stars~4.4k tokensUpdated today
    Auto-check: notes
  • Ccsn Find Simplifications

    kenryu42/cc-safety-net

    A skill your agent uses when working in the cc-safety-net repo to find non-obvious simplification candidates: dead, duplicated, speculative, over-built, or contract-exceeding surfaces in the shell…

    1.6k GitHub stars~2.9k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Ccsn No Comments

What does Ccsn No Comments do?

Use in the cc-safety-net repo when bun run lint:comments or bun run check reports a comment, a stale comment-allowlist entry, or a file it cannot parse, and before writing a code comment there. Ccsn No Comments is an agent skill from kenryu42/cc-safety-net. Use in the cc-safety-net repo when bun run lint:comments or bun run check reports a comment, a stale comment-allowlist entry, or a file it cannot parse, and before writing a code comment there.

When should I use Ccsn No Comments?

Ccsn No Comments fits situations like: tasks that involve Pull requests; tasks that involve Technical documentation; tasks that involve Linting and formatting.

How do I install Ccsn No Comments in Claude Code?

Run `npx skills add kenryu42/cc-safety-net --skill ccsn-no-comments -a claude-code`. Or copy the skill folder (.agents/skills/ccsn-no-comments in kenryu42/cc-safety-net) into .claude/skills/ccsn-no-comments in your project. Claude Code loads it when a task matches its description.

How do I install Ccsn No Comments in Codex?

Run `npx skills add kenryu42/cc-safety-net --skill ccsn-no-comments -a codex`. Or copy the skill folder (.agents/skills/ccsn-no-comments in kenryu42/cc-safety-net) into .agents/skills/ccsn-no-comments in your project. Codex loads it when a task matches its description.

Can I use Ccsn No Comments in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add kenryu42/cc-safety-net --skill ccsn-no-comments -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ccsn-no-comments, .gemini/skills/ccsn-no-comments, .github/skills/ccsn-no-comments and .opencode/skills/ccsn-no-comments in your project.

What does Ccsn No Comments need to run?

Going by SKILL.md and its folder, Ccsn No Comments needs the command-line tools its instructions call (bun and git).

Does Ccsn No Comments access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Ccsn No Comments safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Ccsn No Comments use?

Ccsn No Comments is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Ccsn No Comments use?

About 907 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Ccsn No Comments?

Skills that share tags, products or a category with Ccsn No Comments: Lint Commit PR (Tresjs/tres, 3.8k stars), PR Push (icebear0828/codex-proxy, 1.8k stars), PR Push (icebear0828/codex-proxy, 1.8k stars) and Adk Setup (google/adk-python, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ccsn No Comments?

kenryu42 (a GitHub user) maintains it in kenryu42/cc-safety-net, which has 1,582 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 8, 2026.

Source: kenryu42/cc-safety-net on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.