skills/fix-comments/SKILL.md
Read agent-review comments from .vscode/agent-comments.json, fix each pending comment in the code, and mark it as applied. Use when user says "fix comments", "apply comments", or "resolve comments".
npx skillsauth add popoffvg/dotfiles fix-commentsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Read the agent-review comments file and apply fixes to the codebase.
Read the comments file at .vscode/agent-comments.json in the current workspace root. If it doesn't exist, tell the user there are no comments.
Parse the JSON. The format is:
{
"version": 1,
"comments": [
{
"id": "uuid",
"absPath": "/absolute/path/to/file.ts",
"line": 10,
"text": "Description of what to fix",
"fileHash": "sha256hex",
"createdAt": "ISO8601",
"status": "pending",
"resolved": false
}
]
}
Filter to only status: "pending" (or missing status) comments. Skip applied, failed, skipped, or resolved: true.
For each pending comment, in order:
absPathline (1-based)text field — it describes what needs to be fixed"status": "applied""status": "failed" and "lastError": "reason"Write back the updated JSON to .vscode/agent-comments.json after processing all comments.
Summary: Print how many comments were applied, failed, or skipped.
fileHash) doesn't match the current file content, warn the user but still attempt the fixabsPath doesn't exist, mark as failedline is out of range, use context from text to find the right locationtools
Improve a whole CLAUDE.local.md — the private, per-project rules captured from user corrections. Wraps each conditional rule in a <task-relevant> block so it only surfaces for matching work, merges duplicates, generalizes one-off facts, drops stale entries, and routes raw project facts to engram. Use when the user says "improve claude.local", "clean up the local rules", "claude.local is bloated", or after the Stop hook has appended many rules.
testing
WM pipeline and conventions shared across all phases. Agents must read this before spec, impl, or verify work.
development
One entry point for spec writing, implementation, and bug fixing. Default is new (write spec → grill loop → produce notes → author TODO bodies). Other subcommands: verify (audit), revise (sync to shipped), prototype (settle a decision), code-map (diagram), impl (execute one TODO), fix (analyze cause, correct thoughts, fix behavior), help (this page). Invoke as /code <subcommand>.
development
Red-Green-Refactor cycle for bug fixes. Before fixing a bug, first write a failing test that reproduces it (Red), then make the minimal change to pass (Green), then clean up the code (Refactor). Use on any bug fix, error correction, failing test repair, or when user says "fix this bug".