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 locationtesting
Use when the user asks to create test sets, enumerate scenarios, generate edge cases, or draft a coverage matrix before implementation.
testing
Use when the user asks to review, audit, score, or validate test sets for missed cases before execution or merge.
tools
Test harness plugins in isolation using tmux panes. Runs MCP servers, unit tests, typecheck, and Claude plugin loading. Use when user says "test plugin", "check plugin", "run plugin tests", "validate plugin", or names a specific plugin to test.
development
Guide for designing integration and e2e tests using BDD (Behavior-Driven Development) methodology with Cucumber-style Given/When/Then scenarios. Use when writing or reviewing tests for any service, API, or component. Language-agnostic — covers scenario structure, step notation, assertion principles, async patterns, and common anti-patterns.