Skip to content

Docs: update Open Questions/Next Steps when closing PRs #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
graysurf merged 1 commit into from
Jan 11, 2026
Merged

Docs: update Open Questions/Next Steps when closing PRs #2

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions skills/close-feature-pr/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,6 +55,7 @@ Failure modes:
3. Review PR hygiene (aligned with `create-feature-pr`)
- Title reflects feature outcome; capitalize the first word.
- PR body includes: `Summary`, `Changes`, `Testing`, `Risk / Notes`.
- If PR body includes `Open Questions` and/or `Next Steps` and they are not already `- None`, update them to the latest status (resolve questions or confirm with the user, check off completed steps, link follow-ups).
- `Testing` records results (`pass/failed/skipped`) and reasons if not run.
- If edits are needed: use `gh pr edit <pr> --title ...` / `gh pr edit <pr> --body-file ...`.
4. Merge and delete branch
Expand Down
1 change: 1 addition & 0 deletions skills/close-progress-pr/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -63,6 +63,7 @@ If the progress file includes a `Links -> Planning PR` entry, ensure that planni
2. Preflight
- Ensure working tree is clean: `git status --porcelain=v1` should be empty
- Ensure checks pass (optional but recommended): `gh pr checks <pr>`
- If PR body includes `Open Questions` and/or `Next Steps` and they are not already `- None`, update them to the latest status before merge (resolve questions or confirm with the user, check off completed steps, link follow-ups).
3. Locate the progress file
- Prefer parsing the PR body `## Progress` link and extracting `docs/progress/...`
- If missing, fallback: search by PR URL inside `docs/progress/`:
Expand Down
Loading