AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Ln 613 Code Comments Auditor

skill-levnikolaevich-claude-code-skills-ln-613-code-comments-auditor · by levnikolaevich

Checks inline code documentation quality: WHY-not-WHAT, density, forbidden content, docstrings quality, actuality, legacy cleanup. Use when auditing comments and docstrings.

No reviews yet
0 installs
27 views
0.0% view→install

Install

$ agentstack add skill-levnikolaevich-claude-code-skills-ln-613-code-comments-auditor

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-levnikolaevich-claude-code-skills-ln-613-code-comments-auditor)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
3mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Ln 613 Code Comments Auditor? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

> Paths: File paths (references/, ../ln-*) are relative to this skill directory.

Inline Code Documentation Auditor (L3 Worker)

Type: L3 Worker

Specialized worker auditing inline code documentation quality: comments, docstrings, and language-specific documentation blocks.

Purpose & Scope

  • Audit inline code documentation for quality and compliance across 6 categories
  • Universal for any tech stack (auto-detect comment syntax)
  • Return structured findings to coordinator with severity, location, recommendations
  • Calculate compliance score (X/10) for Inline Code Documentation category
  • Scope is limited to comments/docstrings/JSDoc/XML docs
  • Out of scope: code design quality, naming quality, test quality, architecture quality, or feature correctness except where comments contradict code

Inputs

MANDATORY READ: Load references/audit_worker_core_contract.md and references/mcp_tool_preferences.md.

Receives contextStore with: tech_stack, project_root, output_dir.

Workflow

1) Parse Context: Extract tech stack, project root, output_dir from contextStore 2) Scan: Find all source files (use tech_stack for detection) Hex-line primary path: Use outline(file_path) and discovery-first read_file() for code files before analyzing comments. Use edit_ready=true, verbosity="full" only if the audit turns into a follow-up edit. Do not use hex-graph here - comment quality is a code-reading problem, not a semantic graph problem. 3) Extract: Parse inline comments + docstrings/JSDoc 4) Audit: Run 6 category checks (see Audit Categories below) 5) Collect Findings: Record each violation with severity, location (file:line), effort estimate (S/M/L), recommendation 6) Calculate Score: Count violations by severity, calculate compliance score (X/10) 7) Write Report: Build full markdown report per references/templates/audit_worker_report_template.md, write to {output_dir}/ln-613--global.md in single Write call 8) Return Summary: Return minimal summary to coordinator (see Output Format)

Audit Categories

| # | Category | What to Check | |---|----------|---------------| | 1 | WHY not WHAT | Comments explain rationale, not obvious code behavior; no restating code | | 2 | Density (15-20%) | Comment-to-code ratio within range; not over/under-commented | | 3 | No Forbidden Content | No dates/authors; no historical notes; no code examples in comments | | 4 | Docstrings Quality | Match function signatures; parameters documented; return types accurate | | 5 | Actuality | Comments match code behavior; no stale references; examples runnable | | 6 | Legacy Cleanup | No TODO without context; no commented-out code; no unsupported notes |

Scoring Algorithm

MANDATORY READ: Load references/audit_scoring.md.

Output Format

MANDATORY READ: Load references/templates/audit_worker_report_template.md.

Write JSON summary per references/audit_summary_contract.md. In managed mode the caller passes both runId and summaryArtifactPath; in standalone mode the worker generates its own run-scoped artifact path per shared contract.

Write report to {output_dir}/ln-613--global.md with category: "Inline Code Documentation" and checks: whynotwhat, density, forbiddencontent, docstringsquality, actuality, legacy_cleanup.

Return summary per references/audit_summary_contract.md.

When summaryArtifactPath is absent, write the standalone runtime summary under .hex-skills/runtime-artifacts/runs/{run_id}/evaluation-worker/{worker}--{identifier}.json and optionally echo the same summary in structured output.

Report written: .hex-skills/runtime-artifacts/runs/{run_id}/audit-report/ln-613--global.md
Score: X.X/10 | Issues: N (C:N H:N M:N L:N)

Severity mapping:

| Issue Type | Severity | |------------|----------| | Author names, dates in comments | CRITICAL | | Commented-out code blocks | HIGH | | Stale/outdated comments | HIGH | | Obvious WHAT comments | MEDIUM | | Density deviation >5% | MEDIUM | | Minor density deviation | LOW |

Critical Rules

Apply the already-loaded references/audit_worker_core_contract.md.

  • Do not auto-fix: Report violations only; coordinator aggregates for user
  • Fix code, not rules: NEVER modify rules files (rules.md, standards.md) to make violations pass
  • Code is truth: When comment contradicts code, flag the documentation for update; do not turn this into a general code-quality review
  • WHY > WHAT: Comments explaining obvious behavior should be removed
  • Universal: Works with any language; detect comment syntax automatically
  • Location precision: Always include file:line for programmatic navigation

Definition of Done

Apply the already-loaded references/audit_worker_core_contract.md.

  • [ ] contextStore parsed successfully (including output_dir)
  • [ ] All source files scanned (tech stack from contextStore)
  • [ ] All 6 categories audited
  • [ ] Findings collected with severity, location, effort, recommendation
  • [ ] Score calculated using penalty algorithm
  • [ ] Report written to {output_dir}/ln-613--global.md (atomic single Write call)
  • [ ] Summary written per contract

Reference Files

  • Comment rules and patterns: [references/commentsrules.md](references/commentsrules.md)

Version: 4.0.0 Last Updated: 2026-03-01

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.