An agentic skills framework & software development methodology that works.
Add GitHub thread reply guidance to receiving-code-review
Jesse Vincent1455ac0631e2
diff --git a/RELEASE-NOTES.md b/RELEASE-NOTES.mdindex 9124c9bbd..fb68d5382 100644--- a/RELEASE-NOTES.md+++ b/RELEASE-NOTES.md@@ -1,6 +1,6 @@# Superpowers Release Notes-## v4.0.1 (2025-12-22)+## v4.0.1 (2025-12-23)### Fixes@@ -12,6 +12,10 @@ Fixed a confusing pattern where Claude would invoke a skill via the Skill tool,- Changed "read the skill" → "invoke the skill" in instructions- Updated slash commands to use fully qualified skill names (e.g., `superpowers:brainstorming`)+**Added GitHub thread reply guidance to receiving-code-review** (h/t @ralphbean)++Added a note about replying to inline review comments in the original thread rather than as top-level PR comments.+## v4.0.0 (2025-12-17)### New Featuresdiff --git a/skills/receiving-code-review/SKILL.md b/skills/receiving-code-review/SKILL.mdindex 85d8b0362..4ea72cdf0 100644--- a/skills/receiving-code-review/SKILL.md+++ b/skills/receiving-code-review/SKILL.md@@ -200,6 +200,10 @@ You understand 1,2,3,6. Unclear on 4,5.✅ "Understand 1,2,3,6. Need clarification on 4 and 5 before implementing."```+## GitHub Thread Replies++When replying to inline review comments on GitHub, reply in the comment thread (`gh api repos/{owner}/{repo}/pulls/{pr}/comments/{id}/replies`), not as a top-level PR comment.+## The Bottom Line**External feedback = suggestions to evaluate, not orders to follow.**