What counts as proof of feedback incorporation?

Any verifiable evidence such as test results, logs, diffs, or screenshots produced by the prove skill.

How do you respond to each PR comment?

For each comment, reply with concrete changes or request clarification using the github-comment-respond skill.

When should you re-request review?

Once every comment is addressed and proof is provided, use github-pr-update to re-request the reviewer.

impl-feedback

npx machina-cli add skill bryanp/agent-skills/feedback --openclaw

Files (1)

SKILL.md

960 B

Synthesize feedback on a specific step of an implementation plan from the given Github pull request. Feedback is provided as pull request comments.

Rule: Identity

First use the identity skill to assume the identity of the agent.

Rule: Commit Work

Use the git-branch skill to work from the existing branch for the pull request.
Use the git-commit skill to commit your work after proving it works.

Rule: Update Proof

Use the prove skill to capture proof that the feedback has been incorporated.

Rule: Update Comments

Respond to each comment with proof that the comment was addressed, or requesting more information if needed. Use the github-comment-respond skill to respond.

Rule: Request Review

If all feedback has been addressed fully (e.g. you aren't waiting on a reply) then re-request review from the reviewer. Use the github-pr-update skill.

Source

git clone https://github.com/bryanp/agent-skills/blob/main/code/impl/feedback/SKILL.mdView on GitHub

Overview

The impl-feedback skill translates pull request feedback into concrete changes for a specific step in an implementation plan. It coordinates identity, branch actions, and proof updates to ensure feedback is captured, verified, and communicated back to reviewers.

How This Skill Works

First assume the agent's identity, then use the existing PR branch to apply feedback. Commit the changes with git-commit after proving they work, capture proof with the prove skill, and respond to each comment with proof via github-comment-respond. When all feedback is addressed, re-request review with github-pr-update.

When to Use It

When a PR presents explicit feedback about a specific implementation step.
When you need verifiable evidence that feedback has been incorporated (proof).
When coordinating changes on the correct branch tied to the PR.
When reviewers request clarifications or additional tests for a step.
When all feedback is addressed and you want to re-request a review.

Quick Start

Step 1: Identity - use identity skill to assume agent identity and locate the PR.
Step 2: Branch and apply - use git-branch to check out the PR branch and implement feedback.
Step 3: Prove, report, and request review - run prove to capture results, respond to comments with github-comment-respond, then github-pr-update to re-request review.

Best Practices

Reference the exact PR comment and the targeted implementation step.
Work on the existing branch from the PR using git-branch and git-commit after changes.
Prove changes work by capturing evidence with the prove skill.
Respond to each comment with concrete proof or a request for more info using github-comment-respond.
After all feedback is incorporated, re-request a review with github-pr-update.

Example Use Cases

Addressing a performance tweak suggested in a PR for step 2 of the plan by adding a benchmark and including results.
Responding to a correctness concern in step 4 by adding unit tests and a test log.
Clarifying ambiguous feedback on deployment step by requesting more info and adding a clarifying comment.
Updating the PR with a small refactor to satisfy stylistic feedback on a specific function.
Capturing proof of successful integration of feedback into the feature branch and notifying the reviewer.

Frequently Asked Questions

Add this skill to your agents