code-clean-comments

Comment Cleaner

Resolves a user scope into a durable change-manifest artifact, then spawns the comment-cleaner agent with only CHANGE_MANIFEST and CODE_ROOT.

The comment-cleaner agent remains manifest-only. Never pass SCOPE, BASE_BRANCH, branch, unstaged, or commit-range parameters to it.

1. Resolve Directories

Use generated Resolve Arguments directory values. Resolve {resolved_code_root} to CODE_ROOT when it is non-empty; otherwise use {codeRoot}. Use {workRoot} for the durable artifact directory.

Create the manifest directory if needed:

mkdir -p "{workRoot}/comment-clean-comments"

Choose the next numbered manifest/status path pair:

{workRoot}/comment-clean-comments/change-manifest-001.json
{workRoot}/comment-clean-comments/change-manifest-status-001.json

Increment the number if either file already exists. Set resolved_change_manifest_path and resolved_change_manifest_status_path to the selected pair.

2. Generate Manifest

Delegate all scope resolution to the typed generator:

rp1 agent-tools change-manifest generate \
  --code-root "{resolved_code_root}" \
  --out "{resolved_change_manifest_path}" \
  --status-out "{resolved_change_manifest_status_path}" \
  --source code-clean-comments \
  --scope "{SCOPE}"

Parse the ToolResult envelope into cleanup_manifest_result. The generator is responsible for existing manifest JSON, file, directory, git ref, and git range scopes. Do not inspect files, walk directories, parse git diffs, validate existing manifest JSON, or write manifest JSON yourself.

If cleanup_manifest_result.data.status != "created", cleanup_manifest_result.data.files == 0, cleanup_manifest_result.data.ownedLineCount == 0, or cleanup_manifest_result.data.manifestPath is missing, fail closed and do not dispatch comment-cleaner. Report the status path and skip reason instead.

If the tool fails or returns malformed output, fail closed and do not dispatch comment-cleaner. Report change_manifest_generate_failed with the intended status path.