code-comments

Comments Extraction Skill

Extract comment locations from manifest-owned code lines for analysis by the comment-cleaner agent.

What This Skill Does

• Detects comments inside a tightly scoped change manifest
• Extracts all comments with line numbers and context
• Outputs structured JSON for downstream processing
• Supports multiple programming languages

When to Use

Activate this skill when:

• Preparing manifest-owned comment cleanup operations
• Auditing code documentation coverage
• Analyzing comment patterns in a codebase
• Working with the comment-cleaner agent

Supported Languages

Extension	Single-line	Multi-line
.py, .sh, .rb, .yml, .yaml	#	N/A
.js, .ts, .tsx, .jsx, .go, .rs, .java, .kt, .swift, .c, .cpp, .h, .hpp	//	/* */
.html, .xml, .vue, .svelte	N/A	<!-- -->
.css, .scss, .less	N/A	/* */
.php	//, #	/* */

Usage

Extract Comments from a Change Manifest

Use a generated or validated change manifest as the cleanup boundary. This skill extracts comments inside that boundary; it does not decide which files or lines are cleanup-owned.

# Required for comment-cleaner
rp1 agent-tools comment-extract manifest manifest --change-manifest .rp1/work/features/example/change-manifest-001.json --code-root .

Manifest shape:

{
  "version": 1,
  "source": "build",
  "codeRoot": "/absolute/path/to/repo",
  "files": [
    {
      "path": "src/auth.ts",
      "ownedHunks": [{ "startLine": 20, "endLine": 28 }],
      "allowedOperations": ["remove_comments"]
    }
  ]
}

Generated manifests can come from /build, /build-fast, or /code-clean-comments. Build workflows generate manifests from their recorded baseline; standalone cleanup uses rp1 agent-tools change-manifest generate with --source code-clean-comments --scope ... to convert file, directory, git ref, git range, or existing-manifest input into the same manifest shape.