Skip to content
cccskills
FreePublished on GitHub

comment-accuracy-review

Review comment, JSDoc, TODO, README, and docs-to-code factual consistency, stale or low-value comments, and Chinese comment/variable appropriateness; do not use for general code review, broad documentation rewrites, or auto-editing comments without approval.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md2.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Comment Accuracy Review

Use this skill when ROSE needs a narrow, read-only pass over whether explanatory text still matches the code it describes.

Trigger

  • Comments, JSDoc, TODOs, README snippets, or nearby docs may be stale, misleading, redundant, or contradicted by implementation.
  • A review asks whether docs-to-code claims, examples, parameters, return values, errors, environment notes, or operational steps are factually accurate.
  • Chinese comments, Chinese variable names, or bilingual text need appropriateness checks for clarity, tone, maintainability, and consistency with repository language patterns.

Near Misses

  • General review, large documentation authoring, style-only writing, or implementation are different primary intents. Return the exact mismatch or approved edit need to ROSE; do not invoke another skill or agent here.

Required Routing

  • Owner: ROSE/aili-delivery-flow; direct read-only inspection is the default.
  • Optional agent: one fresh code-review or docs-research assignment only when a concrete capability/context gap independently passes the delegation gate.
  • Default mode: read-only; report findings and recommended edits, but do not modify comments automatically.

Boundaries

  • Compare text claims to the current repository evidence, not to intent or stale plans.
  • Flag comments that restate obvious code, describe old behavior, overpromise guarantees, hide uncertainty, or use TODOs as unmanaged task trackers.
  • Preserve useful intent comments that explain non-obvious constraints, trade-offs, invariants, data formats, or external behavior.
  • Treat generated, vendored, third-party, or upstream-copied comments as out of scope unless the task explicitly includes them.

Verification

  • Cite file paths and line anchors for both the questioned text and the code evidence that confirms or contradicts it.
  • Classify each finding as inaccurate, stale, unverifiable, redundant, language/terminology concern, or acceptable.
  • If edits are later approved, require focused diff inspection and any relevant docs/build/typecheck command for the touched surface.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Review a single academic paper, preprint, DOI, arXiv link, or user-provided PDF/text with source-grounded critique. Use for paper summaries, methodology review, novelty checks, reproducibility concerns, or "review this paper" requests; do not use for multi-paper surveys, systematic literature reviews, citation management, or implementation from a paper.

The English summary is being prepared. Showing the original description.

Rosetears520/aili-workflows2Updated Sep 27, 2026

AI regression scouting routing. Use when agents, prompts, skills, model/tool routing, harness fixtures, or generated-output expectations change and need regression scenarios; do not use for ordinary product-code regressions.

The English summary is being prepared. Showing the original description.

Rosetears520/aili-workflows2Updated Sep 27, 2026

Run the AILI delivery lifecycle from natural-language IDEATE, DEFINE, BUILD, and SHIP intent or the equivalent slash shortcuts; use for idea shaping, spec/test definition, bounded BUILD package queues, review-repair closeout, or adapter routing without exposing internal stage commands.

The English summary is being prepared. Showing the original description.

Rosetears520/aili-workflows2Updated Sep 27, 2026

Android native Kotlin/Compose app development, Material 3 UI, accessibility, and Gradle builds.

The English summary is being prepared. Showing the original description.

Rosetears520/aili-workflows2Updated Sep 27, 2026

Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.

The English summary is being prepared. Showing the original description.

Rosetears520/aili-workflows2Updated Sep 27, 2026

Route an explicitly requested independent/delegated browser QA assignment or durable E2E evidence need; do not trigger for direct Playwright/DOM/console/network inspection, ordinary UI implementation, backend-only work, or production-mutating flows.

The English summary is being prepared. Showing the original description.

Rosetears520/aili-workflows2Updated Sep 27, 2026

See all skills by Rosetears520

Report a problem with this skill