New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Comments

by LedgerHQ in LedgerHQ/ledger-live

Stop writing so many comments. An agent skill from LedgerHQ/ledger-live.

MITAuto-check passed

Install Comments

skills CLI
$ npx skills add LedgerHQ/ledger-live --skill comments -a claude-code

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

GitHub CLI
$ gh skill install LedgerHQ/ledger-live 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/LedgerHQ/ledger-live.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/comments .claude/skills/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
comments
GitHub stars
622
Token cost
~857 tokens
SKILL.md length
196 words
Files
1
Skills in repo
50
Repo updated
First seen
Licence
MIT

At a glance

Stop writing so many comments. An agent skill from LedgerHQ/ledger-live.

  • SKILL.md covers 🧀 Avoid comments, 💡 Treatments and ☝️ When comments are necessary
  • Reaches github.com

What it does

Comments is an agent skill from LedgerHQ/ledger-live. Stop writing so many comments. Follow these suggestions instead!

Its SKILL.md is about 860 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Mono-repository for Ledger Wallet apps and related packages. The licence is MIT.

Example prompts

  • “/comments”

What it can do on your machine

Read from SKILL.md and the folder at commit 30d7883. 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

    No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript and yaml).

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

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    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

Comments loads about 857 tokens when it runs. Until then it costs about 18 tokens; SKILL.md has 196 words of instructions outside code blocks.

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

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 LedgerHQ/ledger-live at commit 30d7883, republished under its MIT licence (© LedgerHQ). 196 words, ~857 tokens.

Download SKILL.mdSave it as .claude/skills/comments/SKILL.md (or your agent's skills folder).
name
comments
description
Stop writing so many comments. Follow these suggestions instead!

Comments in code

🧀 Avoid comments

Comments are code smells because they go out-of-date, bloat context, and lead to confusion.

Don't reference existing comments in the codebase – follow these rules

  • Avoid adding comments – always prefer good names (explainer variables, functions, tests)
  • Use test names to describe behaviour – unit tests are living documentation
  • Good code explains itself – don't add comments that duplicate what the code already conveys

💡 Treatments

When code isn't clear, make it clearer:

  • Rename variables and functions to make comments unnecessary
  • Extract variables and functions to improve readability
  • Use assertions to explain behaviour
Use test names to explain non-obvious details

❌ Bad

ts
it("diffs the current value against resolved when targeted", () => {
  const { result } = renderHook(() => useJsonEditor(makeProps()));
  act(() => result.current.setDiffTarget("resolved"));
  // Current equals resolved → every line is unchanged.
  expect(result.current.diffJson.every((l) => l.state === "none")).toBe(true);
});

✅ Good

ts
it("resets the state of every line when the diff is resolved", () => {
  const { result } = renderHook(() => useJsonEditor(makeProps()));
  act(() => result.current.setDiffTarget("resolved"));
  expect(result.current.diffJson.every((l) => l.state === "none")).toBe(true);
});
Let code speak for itself

❌ Bad

ts
/* Whether the filter trigger should be displayed */
showFilter: boolean;

✅ Good

ts
showFilter: boolean;
Replace comments with explainer variables

Move the comment into a variable name:

Before

ts
// NB `app.trustchain` is an encrypted db path: while the app is password-locked it reads back
// as the ciphertext string. Importing it would regenerate member credentials and null the
// trustchain (LIVE-36130). IsUnlocked re-runs this thunk once the encryption key is set.
// `undefined` must still go through: that is the legitimate "nothing persisted" case.
if (typeof data === "string") return;

After

ts
const dataIsEncrypted = typeof data === "string";
if (dataIsEncrypted) return;

☝️ When comments are necessary

Comments are only for vital information that can't go anywhere else. Always prefer not adding comments. If a comment is the only way, follow these guidelines:

  • Be concise: Use as few words as possible to convey the necessary information.
  • Use JSDocs: Only when describing a shared function.
  • Prefer a link: If the comment is explaining a workaround for a known issue, link to the issue or docs.

❌ Bad

yaml
# pnpm patches add 'patch_hash=HASH' to virtual store paths, which prefab 2.1.0
# (introduced via AGP 8.11) misparses as an option flag due to a clikt bug that splits
# positional path arguments at '='. Pinning prefab to 2.0.0 in gradle.properties avoids
# this; keeping path segments ≤ 80 chars shortens virtual-store paths to reduce the
# likelihood of triggering prefab path-parsing issues as an additional safeguard.
android.prefab.version=2.0.0
virtual-store-dir-max-length=80

✅ Better

yaml
# Workaround for Prefab 2.1.0/Clikt bug
# See: https://github.com/google/prefab/issues/187
android.prefab.version=2.0.0
virtual-store-dir-max-length=80

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

Files

Just SKILL.md in .agents/skills/comments of LedgerHQ/ledger-live.

Open the folder on GitHubat commit 30d7883

Compare with similar skills

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.

Comments compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Comments this skillLedgerHQ/ledger-live622—~857Automated safety check: PassMIT
No Commentscursor/plugins10k7 repos~640Automated safety check: PassNone
Commentsanthropics/claude-for-legal9.6k1 repos~1kAutomated safety check: PassApache-2.0
Suggestion Boxpaperclipai/paperclip99k—~1.3kAutomated safety check: PassMIT
Clean Up Commentsthedaviddias/Front-End-Checklist74k—~435Automated safety check: PassMIT
Comment Checkercode-yeongyu/oh-my-openagent70k—~160Automated safety check: PassCustom licence

Similar skills

  • No Comments

    cursor/plugins

    Official

    Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.

    10k GitHub starsUsed in 7 repos~640 tokens
    Auto-check passed

  • Comments

    anthropics/claude-for-legal

    Official

    Review open NPRM comment periods, log decisions, track deadlines.

    9.6k GitHub starsUsed in 1 repo~1k tokens
    Auto-check passed

  • Suggestion Box

    paperclipai/paperclip

    Quietly suggest a concrete improvement after observing material, generalizable friction in agent work.

    99k GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • Clean Up Comments

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing templates, rendered HTML, or shared components related to Remove comments and debug code in production.

    74k GitHub stars~435 tokensUpdated yesterday
    Auto-check passed

  • Comment Checker

    code-yeongyu/oh-my-openagent

    A skill your agent uses when Codex needs to understand or respond to automatic comment-checker feedback emitted after an edit-like PostToolUse hook.

    70k GitHub stars~160 tokensUpdated today
    Auto-check passed

  • Writing Comments

    withastro/astro

    Official

    How to write JSDoc (/ /) and inline (//) comments in the Astro codebase, for contributors reading the source — not end users.

    63k GitHub stars~2.7k tokensUpdated today
    DevelopmentAuto-check passed

More from LedgerHQ/ledger-live

All 50 skills in this repo

  • Impacting PRs

    LedgerHQ/ledger-live

    Find which open PRs are impacted by a migration/sunset/refactor and notify their authors — blocking review when the old path is already gone from develop, heads-up comment when it is only deprecated…

    622 GitHub stars~3.3k tokensUpdated today
    Auto-check passed

  • Cloud Sync Module

    LedgerHQ/ledger-live

    Write, review or debug a cloudSyncModule.ts — a CloudSyncDataManager that syncs one slice of user data through Ledger Sync (Cloud Sync).

    622 GitHub stars~2.4k tokensUpdated today
    Auto-check passed

  • Codeownership

    LedgerHQ/ledger-live

    Maintain CODEOWNERS file and team directories. An agent skill from LedgerHQ/ledger-live.

    622 GitHub stars~687 tokensUpdated today
    Auto-check passed

  • Coin Families Contract

    LedgerHQ/ledger-live

    Coin-specific families logic must live in families/. An agent skill from LedgerHQ/ledger-live.

    622 GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Data Layer Advanced

    LedgerHQ/ledger-live

    Structure a Ledger Wallet data layer where one API response serves several entities.

    622 GitHub stars~509 tokensUpdated today
    Auto-check passed

  • Debug Rn Native Crash

    LedgerHQ/ledger-live

    Investigate native React Native crashes (Fabric/Hermes/iOS) in ledger-live-mobile when JS error logs are missing or unhelpful.

    622 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

Questions about Comments

What does Comments do?

Stop writing so many comments. An agent skill from LedgerHQ/ledger-live. Comments is an agent skill from LedgerHQ/ledger-live. Stop writing so many comments.

How do I install Comments in Claude Code?

Run `npx skills add LedgerHQ/ledger-live --skill comments -a claude-code`. Or copy the skill folder (.agents/skills/comments in LedgerHQ/ledger-live) into .claude/skills/comments in your project. Claude Code loads it when a task matches its description.

How do I install Comments in Codex?

Run `npx skills add LedgerHQ/ledger-live --skill comments -a codex`. Or copy the skill folder (.agents/skills/comments in LedgerHQ/ledger-live) into .agents/skills/comments in your project. Codex loads it when a task matches its description.

Can I use 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 LedgerHQ/ledger-live --skill 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/comments, .gemini/skills/comments, .github/skills/comments and .opencode/skills/comments in your project.

What does Comments need to run?

SKILL.md names no scripts, command-line tools or credentials: Comments is instructions for the agent only.

Does Comments access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is 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 Comments use?

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 Comments use?

About 857 tokens (SKILL.md is roughly 3.4k 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 Comments?

Skills that share tags, products or a category with Comments: No Comments (cursor/plugins, 10k stars), Comments (anthropics/claude-for-legal, 9.6k stars), Suggestion Box (paperclipai/paperclip, 99k stars) and Clean Up Comments (thedaviddias/Front-End-Checklist, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Comments?

LedgerHQ (a GitHub organization) maintains it in LedgerHQ/ledger-live, which has 622 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on October 8, 2026.

Source: LedgerHQ/ledger-live on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.