Review Implementing

Process and implement code review feedback systematically. Use when user provides reviewer comments, PR feedback, code review notes, or asks to implem

What Is Review Implementing?

The Review Implementing skill is a purpose-built tool designed to help developers systematically process and act on code review feedback. Whether you’re working from a pull request (PR) review, a set of reviewer comments, or a collection of requested changes, this skill streamlines the entire workflow of parsing feedback and turning it into productive, actionable tasks. With Review Implementing, you can ensure that reviewer suggestions are not only understood but also implemented thoroughly, reducing the risk of missed or misunderstood changes and improving overall code quality.

Why Use Review Implementing?

Code reviews are essential for maintaining high standards in collaborative software development, but the process of addressing feedback can often be messy and error-prone. Feedback may come in various formats—numbered lists, bullet points, or even informal comments—and it’s easy to overlook or misinterpret suggestions, especially in large or complex PRs.

Review Implementing solves these challenges by:

  • Systematically extracting actionable tasks from diverse feedback formats.
  • Breaking down complex or ambiguous comments into clear, manageable todos.
  • Providing a repeatable workflow that ensures all feedback is addressed, reviewed, and tracked.
  • Reducing cognitive load by automating the parsing and tracking of review items, letting you focus on high-value implementation work.

By using this skill, teams can foster a more disciplined, reliable, and efficient review process, which ultimately leads to better-maintained codebases and more productive development cycles.

How to Get Started

Getting started with Review Implementing is straightforward. Here’s a step-by-step guide:

  1. Collect Reviewer Feedback: Copy and paste the reviewer comments, PR feedback, or code review notes into your workflow. The feedback can be in any format—numbered, bulleted, or plain text.

  2. Initiate the Skill: Trigger the Review Implementing skill when you’re ready to address the feedback. Simply indicate your intent (e.g., “address these comments” or “implement feedback”).

  3. Parse and Organize Feedback: The skill will automatically parse the feedback, splitting it into distinct, actionable items. Ambiguous or unclear feedback items are flagged for clarification before proceeding.

  4. Generate a Todo List: Each feedback item is transformed into one or more specific, measurable tasks using a Todo tool. Complex feedback is broken down further for clarity.

  5. Begin Implementation: The first todo is marked as in_progress, and you can start systematically working through the tasks. The skill leverages search (Grep), file discovery (Glob), and editing tools to help you efficiently locate and modify relevant code.

Example Workflow

Suppose you receive the following code review feedback:

1. Add type hints to the extract_user_info function.
2. Fix duplicate tag detection in tag_utils.py.
3. Update the docstring in chain.py for clarity.
4. Add a unit test for the edge case where input is empty.

The skill automatically parses these into actionable todos:

  • Add type hints to extract_user_info function
  • Fix duplicate tag detection logic in tag_utils.py
  • Update docstring in chain.py
  • Write unit test for empty input edge case

Key Features

1. Intelligent Feedback

Parsing

  • Handles numbered and bulleted lists: Automatically splits feedback into individual items, even from mixed or unstructured formats.
  • Extracts distinct change requests: Ensures no feedback is missed due to formatting inconsistencies.
  • Ambiguity detection: Prompts for clarification on vague comments to prevent erroneous implementations.

2. Automated Todo

Generation

  • Actionable task creation: Every feedback item becomes a concise, measurable todo.
  • Task breakdown: Complex suggestions are decomposed into smaller, achievable steps.
  • Progress tracking: The first task is marked as in_progress, with status updates as you work through the list.

3. Seamless Codebase

Navigation

  • Grep integration: Quickly locates relevant functions, classes, or code blocks based on feedback context.
  • Glob support: Finds files matching patterns, expediting navigation in large codebases.
  • Current state inspection: Reads and displays relevant code to inform your edits.

4. Guided Code

Editing

  • Edit tool integration: Applies changes directly and systematically, following project conventions for formatting, naming, and documentation.
  • Consistency enforcement: Encourages adherence to coding standards and style guides.

Practical Example

If a reviewer suggests, “Add type hints to the extract_user_info function,” the workflow would be:

  1. Locate the function:
    grep "def extract_user_info" *.py
  2. Edit the function:
    def extract_user_info(user: dict) -> dict:
        # function body...
  3. Mark the todo as done and continue to the next item.

Best Practices

  • Clarify before acting: If any feedback item is unclear, always seek clarification before implementation.
  • Break down complex feedback: Divide multifaceted comments into atomic tasks to avoid partial implementations.
  • Follow project conventions: Adhere to established coding standards, formatting, and documentation practices.
  • Test after each change: Run relevant tests after each modification to ensure correctness and prevent regressions.
  • Document changes: Update documentation and changelogs to reflect feedback-driven changes.

Important Notes

  • Not a substitute for communication: While Review Implementing automates much of the workflow, direct communication with reviewers remains critical for resolving ambiguities.
  • Supports various feedback formats: Handles numbered, bulleted, or plain-text feedback, but highly unstructured comments may require manual intervention.
  • Designed for iterative workflows: Encourages frequent, incremental updates and feedback cycles, rather than monolithic change sets.
  • Integration with other tools: Works best when combined with version control, continuous integration, and testing frameworks.
  • Regularly update the skill: Keep the skill and its dependencies up to date to benefit from improvements and bug fixes.