review-implementing

Implements code review feedback systematically using tracked todo lists and edits.

Updated Aug 12, 2026
One-click install
npx skills add https://github.com/Barbaros911/As-mine --skill review-implementing-barbaros911
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-implementing
Source: https://github.com/Barbaros911/As-mine/tree/main/.claude/skills/review-implementing
Command: npx skills add https://github.com/Barbaros911/As-mine --skill review-implementing-barbaros911

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a list of reviewer comments or PR feedback into actual code changes is error-prone: items get skipped, ambiguous requests get misinterpreted, and progress is hard to track. This Skill parses review feedback into discrete tasks and implements each one methodically with real-time status tracking. ## Core Features & Use Cases - Feedback Parsing: Splits numbered lists, bullet points, and unstructured reviewer notes into distinct actionable change requests. - Todo-Driven Implementation: Converts each feedback item into TodoWrite tasks, keeping exactly one task in progress and marking completions immediately. - Validation & Edge-Case Handling: Runs affected tests and lint checks (e.g., uv run ruff check), and handles conflicts, breaking changes, and missing referenced code by asking for clarification. - Use Case: A reviewer leaves eight comments on your pull request. Paste them in, and the Skill creates a todo list, locates each referenced function with Grep/Glob, applies edits following project conventions, runs tests, and reports a summary of all changes. ## Quick Start Address these code review comments and implement the requested changes one by one.

Frequently Asked Questions about review-implementing

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

FAQPage Schema
How do I implement code review feedback systematically?▼

Parse the reviewer notes into individual items, create a todo list with one task per change, then implement each item sequentially while marking completions in real time. Run affected tests after each change to verify nothing breaks.

How to address PR review comments without missing any?▼

Convert every comment into a tracked todo item before editing any code. Keep only one task in progress at a time and mark each completed immediately, which guarantees no feedback item is skipped or batched silently.

What should I do when reviewer feedback is ambiguous or conflicting?▼

Ask the reviewer or user for clarification before implementing ambiguous items. For conflicting feedback, explain the conflict clearly and request guidance rather than guessing which interpretation is correct.

Should tests be run after implementing review suggestions?▼

Yes, run all tests affected by the changes and check for linting errors before marking a task complete. If tests fail after a change, fix them first to ensure the implementation does not introduce regressions.

What happens if review feedback references code that does not exist?▼

Stop and ask for clarification instead of guessing. Verify the intended file or function with the user before proceeding, since implementing against a wrong assumption wastes effort and may introduce bugs.