pr-retrolisted

# PR Retro Skill Learn from PR outcomes by analyzing accept/reject patterns. ## Overview After a PR is merged or rejected, analyze what worked and what didn't to improve future contributions. **Output:** `.agents/learnings/YYYY-MM-DD-pr-{repo}-{outcome}.md` **When to Use**: - After a PR is merged (capture success patterns) - After a PR is rejected (understand why) - After receiving significant review feedback - Periodically to review contribution patterns --- ## Workflow ``` 1. PR Discovery -> Find the PR to analyze 2. Outcome Analysis -> Merged/rejected/changes requested 3. Feedback Extraction -> What did reviewers say? 4. Pattern Identification -> What worked/didn't 5. Lesson Extraction -> Reusable learnings 6. Output -> Write retro document ``` --- ## Phase 1: PR Discovery ```bash # If PR number provided gh pr view <number> --json state,reviews,comments,mergedAt,closedAt # Find recent PRs by you gh pr list --state all --author @me --limit 10 # Find PRs to a specific repo gh pr list -R <owner/repo> --state all --author @me --limit 10 ``` --- ## Phase 2: Outcome Analysis | Outcome | Meaning | Focus | |---------|---------|-------| | **Merged** | Success | What worked? | | **Closed (not merged)** | Rejected | Why? | | **Open (stale)** | Ignored/abandoned | What went wrong? | | **Changes requested** | Needs work | What feedback? | ```bash # Get PR outcome gh pr view <number> --json state,mergedAt,closedAt,reviews ``` --- ## Phase 3: Feedback Extracti