Agent skill

Code Comments

by bholmesdev in bholmesdev/hubble.md

Use while implementing or reviewing edge cases, failure paths, or unexpected behavior to document the non-obvious constraints in code.

MITAuto-check passedDevelopment

Install Code Comments

skills CLI
$ npx skills add bholmesdev/hubble.md --skill code-comments -a claude-code

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

GitHub CLI
$ gh skill install bholmesdev/hubble.md code-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/bholmesdev/hubble.md.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/code-comments .claude/skills/code-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
code-comments
GitHub stars
1.5k
Token cost
~149 tokens
SKILL.md length
56 words
Files
1
Skills in repo
13
Repo updated
First seen
Licence
MIT

At a glance

Use while implementing or reviewing edge cases, failure paths, or unexpected behavior to document the non-obvious constraints in code.

  • Improve code comments
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Tasks that involve Technical documentation

What it does

Code Comments is an agent skill from bholmesdev/hubble.md. Use while implementing or reviewing edge cases, failure paths, or unexpected behavior to document the non-obvious constraints in code. Also use when asked to add or improve code comments.

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

It sits in Development, covering Technical documentation. The repository describes itself as: The best notepad for you and your agents. The licence is MIT.

When your agent uses it

  • Improve code comments
  • Tasks that involve Technical documentation

Example prompts

  • “/code-comments”

What it can do on your machine

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

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

  • Network

    No URLs in SKILL.md.

    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

Code Comments loads about 149 tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 56 words of instructions outside code blocks.

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

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 bholmesdev/hubble.md at commit 571a523, republished under its MIT licence (© bholmesdev). 56 words, ~149 tokens.

Download SKILL.mdSave it as .claude/skills/code-comments/SKILL.md (or your agent's skills folder).
name
code-comments
description
Use while implementing or reviewing edge cases, failure paths, or unexpected behavior to document the non-obvious constraints in code. Also use when asked to add or improve code comments.

Code comments

When implementing edge cases, failure paths, or unexpected behavior, always document why that code was written.

  • Use the codebase's terms in plain English.
  • Skip comments when a clear name or small code change makes the behavior obvious.
  • Do not restate conditions, narrate the PR or conversation, or describe behavior that has not been verified.

© bholmesdev, 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/code-comments of bholmesdev/hubble.md.

Open the folder on GitHubat commit 571a523

Compare with similar skills

Code 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.

Code Comments compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Code Comments this skillbholmesdev/hubble.md1.5k—~149Automated safety check: PassMIT
Diagram Designcathrynlavery/diagram-design44k1 repos~7.5kAutomated safety check: PassMIT
Simple Englishmoeru-ai/airi50k2 repos~4.6kAutomated safety check: PassMIT
Get API Docs with chubandrewyng/context-hub14k2 repos~775Automated safety check: PassMIT
Doc SyncJetBrains/ideavim10k2 repos~2.6kAutomated safety check: PassMIT
Mailspring App ScreenshotsFoundry376/Mailspring18k—~1.4kAutomated safety check: PassGPL-3.0

Similar skills

  • Diagram Design

    cathrynlavery/diagram-design

    Creates branded diagrams, from architecture, flowchart and sequence to charts and maps, as self-contained HTML with inline SVG, with import from draw.io, Mermaid and Excalidraw.

    44k GitHub starsUsed in 1 repo~7.5k tokens
    DevelopmentAuto-check passed
  • Simple English

    moeru-ai/airi

    Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop.

    50k GitHub starsUsed in 2 repos~4.6k tokens
    DevelopmentAuto-check passed
  • Get API Docs with chub

    andrewyng/context-hub

    Fetches current documentation for third-party APIs and SDKs with the chub CLI before the agent writes code against them, instead of relying on remembered API shapes.

    14k GitHub starsUsed in 2 repos~775 tokens
    DevelopmentAuto-check passed
  • Doc Sync

    JetBrains/ideavim

    Official

    Keeps IdeaVim documentation in sync with code changes. An agent skill from JetBrains/ideavim.

    10k GitHub starsUsed in 2 repos~2.6k tokens
    DevelopmentAuto-check passed
  • Mailspring App Screenshots

    Foundry376/Mailspring

    Captures screenshots of the running Mailspring dev app for docs, PRs or visual checks by launching it with a debugging port, driving the UI and clipping to an element.

    18k GitHub stars~1.4k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Draw.io Diagram Studio

    Agents365-ai/drawio-skill

    Creates and edits editable draw.io diagrams from descriptions, code, infrastructure files, SQL and API schemas, with sync, review, test and export tools.

    10k GitHub stars~2.4k tokensUpdated 5 days ago
    DevelopmentAuto-check: notes

More from bholmesdev/hubble.md

All 13 skills in this repo
  • Changelog

    bholmesdev/hubble.md

    Add a user-facing entry to CHANGELOG.md for work that just landed.

    1.5k GitHub stars~564 tokensUpdated 6 days ago
    Auto-check passed
  • Review PR

    bholmesdev/hubble.md

    Review a pull request or local branch diff for correctness, security, lifecycle, error handling, tests, and meaningful performance risks.

    1.5k GitHub stars~800 tokensUpdated 6 days ago
    Auto-check passed
  • Triage

    bholmesdev/hubble.md

    Triage an incoming GitHub, Jira, Linear, or other issue-tracker issue against the current codebase and related issues, then return a structured decision with exactly one triage state.

    1.5k GitHub stars~1.5k tokensUpdated 6 days ago
    Auto-check passed
  • Simplify

    bholmesdev/hubble.md

    Use this skill automatically when you feel your code is ready for human review, and whenever writing or reviewing code comments.

    1.5k GitHub stars~886 tokensUpdated 6 days ago
    Auto-check passed
  • Write Product Spec

    bholmesdev/hubble.md

    Write a PRODUCT.md spec for a significant Hubble user-facing feature, focused only on user experience and observable behavior.

    1.5k GitHub stars~966 tokensUpdated 6 days ago
    Auto-check passed
  • Write Tech Spec

    bholmesdev/hubble.md

    Write a TECH.md spec for a significant Hubble feature after researching the monorepo architecture.

    1.5k GitHub stars~1.1k tokensUpdated 6 days ago
    Auto-check: notes

Categories

Questions about Code Comments

What does Code Comments do?

Use while implementing or reviewing edge cases, failure paths, or unexpected behavior to document the non-obvious constraints in code. md. Use while implementing or reviewing edge cases, failure paths, or unexpected behavior to document the non-obvious constraints in code.

When should I use Code Comments?

Code Comments fits situations like: improve code comments; tasks that involve Technical documentation.

How do I install Code Comments in Claude Code?

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

How do I install Code Comments in Codex?

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

Can I use Code 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 bholmesdev/hubble.md --skill code-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/code-comments, .gemini/skills/code-comments, .github/skills/code-comments and .opencode/skills/code-comments in your project.

What does Code Comments need to run?

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

Does Code Comments access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

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

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

About 149 tokens (SKILL.md is roughly 596 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 Code Comments?

Skills that share tags, products or a category with Code Comments: Diagram Design (cathrynlavery/diagram-design, 44k stars), Simple English (moeru-ai/airi, 50k stars), Get API Docs with chub (andrewyng/context-hub, 14k stars) and Doc Sync (JetBrains/ideavim, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Code Comments?

bholmesdev (a GitHub user) maintains it in bholmesdev/hubble.md, which has 1,483 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 1, 2026.

Source: bholmesdev/hubble.md on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.