playground-claude-skills/skills/pr-feedback-implementer/SKILL.md

name, description

name	description
Pull Request Feedback Implementer	This workflow fetches comments from a pull request, checks which comments needs to be implemented as code, draft implementation plan, and implements them. Trigger when user wants to check comments, address comments, or implement feedback for a pull request.

Pull Request Feedback Implementer Workflow

This skill provides a structured workflow for guiding user through the process of implementing feedback for a pull request. Act as an active guide, walking users through these stages: picking comments which need to be implemented as code, drafting an implementation plan, and implementing the feedback.

When to Offer This Workflow

Trigger condition:

• User mentions "address comments", "check comments", "implement feedback" for pull request
• User mentions git or bitbucket
• User mentions "pull request", "PR", "merge request", "MR"

Stage 1: Fetch Comments from Pull Request

Goal: Gather all relevant comments which need to be implemented as code.

Steps:

1. If not specified yet, ask user to specify the repository name, workspace organization name, pull request number or rough description. If user specify comment URL, skip to stage 2.
2. Fetch latest pull requests from repository using available tool / MCP
3. Let user select the pull request to work on
4. Fetch non outdated comments from selected pull request using available tool / MCP
5. Present the comments as numbered list to the user for review and selection.
6. For each comment, execute stage 2 onwards

Stage 2: Implementation Plan

Goal: Create implementation plan for comments

Comments can be vague and not verbose, prompt user with the implementation plan for each comment. The goal is to gather requirement from user, improve the plan until user is satisfied with the plan.

Guidelines:

1. Stick with user coding style
2. Always DRY, reuse if possible
3. Small changes are preferred
4. If code base has tests, ask user if they want to update the tests
5. Do not generate extra documentaiton unless user explicitly ask for it

Steps:

1. With available tools/MCP clone the repository if not already present and checkout the branch. You can ask user if the code is present locally and available for your context first. If yes, don't clone and use local code base.
2. Prompt user for each comment with your suggestion on how to address that particular comment. Iterate with user feedback, revise implementation plan so that user is satisfied.
3. Save the implementation plan in files, one file per comment
4. Once it's done for all comments, go to stage 3

Stage 3: Implementing

Goal: Write and update the codebase

Steps:

1. Read previously saved implementation plans
2. For each plan, modify the codes
3. Ask user feedback and see if anything needs to be changed
4. Once user is satisfied, proceed to the next plan.