feat(skills): refresh issue and PR descriptions after post-creation changes - #18
Merged
Merged
Conversation
…n changes Issue descriptions created by /tasks and PR descriptions created by /ship become stale when implementation deviates from the plan or review feedback triggers additional commits. This adds refresh steps to keep them current: - /implement Step 6: refresh issue description after implementation completes - /ship Step 6: mandatory issue refresh with final state (was optional view-only) - /ship Step 8: refresh PR description when post-creation commits are pushed - /sdd: orchestrate refreshes at Phase 4 and Phase 6 transitions https://claude.ai/code/session_018115ANUK8M1Lw271YcY9uV
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Issue and PR descriptions become stale when implementation deviates from the original plan or when review feedback triggers additional commits after PR creation. This adds refresh steps throughout the SDD pipeline to keep descriptions current.
What changed
skills/implement/SKILL.md: Added Step 6 — refresh the GitHub issue description after all tasks are implemented (mark completed tasks, update deviations, add new files)skills/ship/SKILL.md: Made Step 6 (issue refresh) mandatory instead of optional view-only; added Step 8 to refresh PR description when post-creation commits are pushedskills/sdd/SKILL.md: Updated Phase 4 and Phase 6 gates to include description refresh; added gotcha about stale descriptionsHow to test
/tasksto create an issue, then/implement— verify Step 6 prompts to refresh the issue description/ship— verify Step 6 updates the issue and Step 8 is available for post-PR updates/sddend-to-end — verify Phase 4 and Phase 6 gates mention description refreshBreaking changes
References
https://claude.ai/code/session_018115ANUK8M1Lw271YcY9uV