feedback

Feedback Skill

Purpose

This skill handles the review cycle after /execute creates a PR. It reads PR comments, creates an immutable feedback.md record in the story directory, applies fixes, and updates the PR. The feedback document is a permanent historical record of what was raised and how it was resolved.

Pipeline position: /execute → PR created → reviewer comments → /feedback → feedback.md + PR updates → merge → Done

---

First Steps

When this skill is invoked:

1. Read the template: templates/feedback-template.md
2. Identify the PR:
   • If the user specified a PR number, use that
   • If on a feature branch, check for an open PR:

     ~/.local/bin/gh pr list --head "$(git branch --show-current)" \
       --repo ABilenduke/content-engine --json number,title --jq '.[0]'
     

   • If no PR found, ask the user for the PR number
3. Read PR details:

   ~/.local/bin/gh pr view {number} --repo ABilenduke/content-engine \
     --json title,body,reviews,comments,reviewDecision
   

4. Locate the story directory: Find the story that produced this PR by:
   • Checking the PR description for story document paths
   • Checking the branch name for feature/story naming
   • Asking the user if neither works
5. Read existing story documents: Load plan.md and design.md for context on what was intended
6. Read PR review comments:

   # General PR comments
   ~/.local/bin/gh pr view {number} --repo ABilenduke/content-engine --comments
   
   # Inline code review comments
   ~/.local/bin/gh api repos/ABilenduke/content-engine/pulls/{number}/comments \
     --jq '.[] | {path: .path, line: .line, body: .body, user: .user.login}'
   
   # Review summaries
   ~/.local/bin/gh api repos/ABilenduke/content-engine/pulls/{number}/reviews \
     --jq '.[] | {state: .state, body: .body, user: .user.login}'
   

7. Begin processing feedback

---

Process

Phase 1: Gather & Categorize Feedback