review-comments

Locate // REVIEW annotations in source files and propose concrete edits.

11|Updated Sep 5, 2025

Search Tags:#workflow #refactor #review #code #static-analysis #code-review #review-comments

Ready to run

npx skills add https://github.com/thrawn01/claude-dotfiles --skill review-comments-thrawn01

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-comments
Source: https://github.com/thrawn01/claude-dotfiles/tree/main/skills/review-comments
Command: npx skills add https://github.com/thrawn01/claude-dotfiles --skill review-comments-thrawn01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you automatically locate and address // REVIEW annotations embedded in source files, reducing manual review time and preventing missed retests.

Core Features & Use Cases

Identify // REVIEW markers in code and summarize next steps.
Propose concrete changes to address each review note.
Integrate with your workflow to apply fixes when you provide the target file.

Quick Start

Provide the path to a file containing // REVIEW comments and I will read the file, identify all comments, and begin implementing or outlining fixes.

Frequently Asked Questions about review-comments

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automatically locate and resolve REVIEW comments in source code?▼

To resolve REVIEW comments in source code, this skill scans your target file, identifies all // REVIEW markers, and proposes concrete edits or notes to address each annotation. It ensures changes comply with coding standards and integrate safely without removing unrelated content.

What is the best way to summarize required changes from code review annotations?▼

Summarizing required changes from code review annotations involves reading the file fully to locate all REVIEW markers. This skill automatically extracts these markers and outlines the necessary next steps to implement or resolve each specific review note.

How do I address REVIEW markers without breaking existing code logic?▼

Addressing REVIEW markers safely requires applying edits that comply with coding standards and integrate with existing code. This skill reads the entire file fully before proposing changes, ensuring it never removes unrelated content or breaks current logic.

Can I apply this to a specific target file or ticket for static analysis?▼

Yes, you can apply this to a specific target file or ticket for static analysis. By providing the file path, the skill reads the file fully, identifies all REVIEW annotations, and begins implementing or outlining the required fixes.

Does this workflow support identifying all review markers before refactoring?▼

Yes, the workflow supports identifying all review markers before refactoring by scanning the entire source file. It locates every // REVIEW annotation and summarizes the required changes so you can address them systematically.