writing-comments
100 / 100 · Low risk
Fine to try.
How to write JSDoc (/** */) and inline (//) comments in the Astro codebase, for contributors reading the source — not end users. Use whenever writing or editing comments in .ts/.js source, including comments added incidentally while fixing bugs or building features. Does not cover the @docs-generated config/error reference.
What this skill can do
We found nothing in the files we read that matches our rules. That does not prove the skill is safe: see the limits of static scanning.
Install
Paste this into your terminal. It downloads exactly the version we scanned, not whatever is newest.
if [ -e ~/.agents/skills/'writing-comments' ] || [ -L ~/.agents/skills/'writing-comments' ]; then echo 'A skill folder named writing-comments already exists — not replacing it' >&2; false; else d=$(mktemp -d) && git clone --quiet --filter=blob:none --no-checkout 'https://github.com/modem-dev/ossrules' "$d" && git -C "$d" checkout --quiet '9625409b6c20077e1d92909e15e800608a85a776' -- 'public/files/astro/.agents/skills/writing-comments' && mkdir -p ~/.agents/skills && cp -R "$d"/'public/files/astro/.agents/skills/writing-comments' ~/.agents/skills/'writing-comments' && rm -rf "$d"; fi
Codex reads ~/.agents/skills directly. For Claude Code, Cursor, Copilot, Gemini CLI, Antigravity or OpenCode, also link it. For Claude Code: ln -s ~/.agents/skills/'writing-comments' ~/.claude/skills/'writing-comments' (other agents: ~/.cursor/skills, ~/.copilot/skills, ~/.gemini/skills, ~/.gemini/config/skills, ~/.config/opencode/skills). Or install through the finder skill, which does both.
Badge for your README
[](https://zalavijaysinh.github.io/skilltrust/repos/modem-dev/ossrules/)
Score history
| Date | Version | Score |
|---|---|---|
| 2026-11-07 | 9625409 | 100 |