ln-610-code-comments-auditor

Audit code comments and docstrings with six category checks and X/10 scores.

534|73|Updated Oct 24, 2025
One-click install
npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-610-code-comments-auditor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-610-code-comments-auditor
Source: https://github.com/levnikolaevich/claude-code-skills/tree/main/ln-610-code-comments-auditor
Command: npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-610-code-comments-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill audits code comments and docstrings across the codebase, evaluating WHY vs WHAT, density, forbidden content, docstring accuracy, and actuality, then produces a compliance score and actionable findings.

Core Features & Use Cases

  • Validate that comments explain rationale (WHY) rather than obvious code behavior (WHAT).
  • Check density (target 15-20%), forbidden content, and docstring accuracy.
  • Detect stale or legacy comments and ensure comments reflect current code.

Quick Start

Run a comprehensive comments audit to receive a compliance score and recommended actions for comment quality.

Frequently Asked Questions about ln-610-code-comments-auditor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit code comments and docstrings for quality across my codebase?

Code comment auditing evaluates inline comments and docstrings against six dimensions: whether comments explain rationale (WHY) rather than obvious behavior (WHAT), density targets (15-20%), forbidden content, docstring accuracy, staleness, and legacy cleanup. The audit produces compliance scores per category and actionable findings.

What's the difference between comments that explain WHY versus WHAT, and why does it matter?

WHY comments explain the reasoning or context behind code decisions; WHAT comments merely restate what the code obviously does. Effective comments focus on WHY—the non-obvious intent, constraints, or trade-offs—making code maintenance faster and reducing cognitive load for reviewers and future maintainers.

Can I run a comments audit as part of my code review workflow?

Yes. The Skill integrates into code review processes to catch comment quality issues before merge. It also works standalone after major refactors or as a component of broader documentation pipelines, scanning any tech stack and tech-agnostic to language or framework.

What does optimal comment density look like, and how is it measured?

Comment density targets 15-20% of source lines. The audit calculates this ratio and flags density outliers—both sparse codebases lacking necessary context and over-commented code that obscures readability—helping teams strike the right balance.

How does the Skill detect stale or outdated comments that no longer match the code?

The actuality check identifies comments whose content contradicts current code behavior, flagging them for refresh or removal. This prevents misleading documentation and ensures comments remain a reliable source of truth during maintenance and onboarding.

Can the audit detect forbidden or inappropriate content in comments?

Yes. The forbidden content check scans comments for policy violations, sensitive data, or inappropriate language, helping teams enforce code review standards and maintain professional documentation across the codebase.