comment-conventions
🔌Pluginrvanbaalen/skills
Installation
/plugin marketplace add rvanbaalen/skills/plugin install comment-conventions@rvanbaalen
|Language-agnostic code commenting and docblock conventions — present-tense comments, dev-focused content, mandatory docblocks on new functions/methods/components, a 3-source-line descending-length cap on docblock prose, and a no-chatter rule for inline comments (no prose walls, no business-logic essays, no step-by-step narration in the code path). Auto-fixes non-compliant docblocks and inline-comment walls on existing functions in the file being edited, leaving unusually long deliberate docblocks alone. Ships a PostToolUse hook that auto-validates Rule 4 on every Edit/Write.
Part of
rvanbaalen/skills
More from this repository10
TanStack Query v5 skill with three modes — code review, v4→v5 migration, and coding guidance for new v5 code. Grounded in the official v5 docs.
Stress-test a plan before implementation by walking the design tree one decision at a time, with a recommended answer for every question
Commit, Push, and Release — one-command workflow with release-please integration
Deterministic SVG generation, validation, and rendering for icons, diagrams, charts, UI mockups, and technical drawings.
Post a structured investigation/fix comment on the active GitHub PR, update progress, and mark resolved when done. Proactively proposes itself when an investigation lands on a root cause and fix plan.
Multi-step macOS disk-space cleanup: identify what's using disk, propose a safety-tiered plan, then execute with confirmation. Covers caches, dev tooling, VMs, Ollama models, orphaned app data, app uninstalls, and the Time Machine local-snapshot trap
Auto-suggest semver version bumps for changed plugins before pushing
Apple's eight core principles of design (Purpose, Agency, Responsibility, Familiarity, Flexibility, Simplicity, Craft, Delight) as a working framework for reviewing, critiquing, and building user interfaces — applied with the canonical examples and with trade-offs surfaced whenever honoring one principle costs another
Create a new GitHub issue with template, type, and label selection
Public Claude Code skills marketplace