Update GitHub issues from triage, investigation, or prioritization reports — adds labels, posts comments, sets milestones, and closes issues with safety checks
Read a triage, investigation, or prioritization report and apply the recommended actions to GitHub. This is the only skill in the issue workflow that modifies GitHub state.
/update-issues --from-report [path] [--dry-run]
--from-report — Path to a report JSON file (auto-detects type: triage decisions, investigation decisions, or resolutions). If path omitted, uses the most recent report JSON in .work/triage/reports/.--dry-run — Show what would be done without making changes. This is the DEFAULT behavior on first invocation — you must confirm before actions are applied.Read the JSON file and determine report type:
verdicts array → Triage decisions (DECISIONS-*.json)investigations array → Investigation decisions (*-INVESTIGATION-DECISIONS.json)resolutions array → Resolution decisions (RESOLUTIONS-*.json)For each issue in the report, determine the GitHub actions to take:
From triage decisions:
| Verdict | Actions |
|---|---|
| Close - Fixed | Close issue (reason: completed), add label triaged, remove label triage |
| Close - Duplicate | Close issue (reason: not planned), comment linking canonical issue, add label duplicate |
| Close - Not a Bug | Close issue (reason: not planned), add label not-bug, comment explaining why this is not a defect |
| Close - Already Exists | Close issue (reason: not planned), add label already-exists, comment explaining the existing feature |
| Close - Invalid | Close issue (reason: not planned), comment with explanation |
| Close - Stale | Close issue (reason: not planned), comment explaining staleness |
| Request More Info | Add label needs-more-info, comment requesting specific info |
| Retype - Bug | Change issue type to bug |
| Retype - Feature Request | Change issue type to enhancement |
| Valid - Needs Triage | No action (needs investigation first) |
| Valid - Already Triaged | No action |
From investigation decisions:
| Result | Actions |
|---|---|
| Confirmed Bug | Add label triaged, remove label triage |
| Confirmed Bug (blocked) | Add label triaged, remove label triage, add blocked label (blocked, blocked: vscode, blocked: git, blocked: cli, or blocked: language-server based on blockedBy field) |
| Likely Fixed | Add label needs-more-info, comment asking reporter to verify on latest version |
| Cannot Reproduce | Add label needs-more-info, comment requesting updated repro steps |
| Inconclusive / Insufficient | No action (needs human review) |
From resolution decisions:
| Recommendation | Actions |
|---|---|
| shortlist | Set milestone to "Shortlist", add label triaged, remove label triage |
| backlog | Set milestone to "Backlog", add label triaged, remove label triage |
| wont-fix | Close issue (reason: not planned), add label wontfix, comment with rationale |
| community-contribution | Add label needs-help (if bug) or needs-champion (if enhancement), comment inviting contribution |
Critical: Before applying ANY action, verify current issue state:
gh issue view <number> --repo gitkraken/vscode-gitlens --json state,labels,milestone
For each issue, check:
Before executing any actions, present a summary table:
## Actions to Apply
| Issue | Action | Details | Status |
| ----- | ------------- | ----------------------------------- | ---------------------------- |
| #1234 | Close | Reason: not planned, Comment: "..." | Ready |
| #1234 | Add label | `duplicate` | Ready |
| #2345 | Add label | `needs-more-info` | Ready |
| #2345 | Comment | "Could you provide..." | Ready |
| #3456 | Set milestone | Backlog | Ready |
| #4567 | Close | Reason: completed | ⚠️ Already closed — skipping |
### Summary
- Actions ready: N
- Skipped (already applied): N
- Warnings: N
Ask for confirmation before proceeding. The user may choose to:
Execute approved actions using gh CLI:
# Add label
gh issue edit <number> --repo gitkraken/vscode-gitlens --add-label "<label>"
# Remove label
gh issue edit <number> --repo gitkraken/vscode-gitlens --remove-label "<label>"
# Set milestone
gh issue edit <number> --repo gitkraken/vscode-gitlens --milestone "<milestone>"
# Post comment
gh issue comment <number> --repo gitkraken/vscode-gitlens --body "<message>"
# Close with reason and comment
gh issue close <number> --repo gitkraken/vscode-gitlens --reason "not planned" --comment "<message>"
# Close as completed
gh issue close <number> --repo gitkraken/vscode-gitlens --reason "completed" --comment "<message>"
Execution order per issue: Labels first, then milestone, then comment, then close (if applicable). This ensures the issue has correct metadata before closing.
Error handling: If a gh command fails, log the error and continue with remaining actions. Report all failures at the end.
Write an audit log to .work/triage/reports/YYYY-MM-DD-ACTIONS.md:
# Actions Applied — YYYY-MM-DD
Source report: <path to source JSON>
Report type: triage | investigation | resolution
Applied at: <ISO timestamp>
Applied by: <git user>
## Actions Taken
| Issue | Action | Result |
| ----- | ----------------------------- | --------------------------------------- |
| #1234 | Closed (not planned) | ✓ Success |
| #1234 | Added label `duplicate` | ✓ Success |
| #2345 | Added label `needs-more-info` | ✓ Success |
| #2345 | Posted comment | ✓ Success |
| #3456 | Set milestone: Backlog | ✗ Failed: milestone "Backlog" not found |
## Summary
- Successful: N
- Failed: N
- Skipped: N
--force or bypass safety checksThis skill consumes output from the other issue workflow skills:
/triage recent → /update-issues (apply triage verdicts)
/triage recent → /investigate --from-report → /update-issues (apply investigation results)
/triage recent → /investigate --from-report → /prioritize --from-report → /update-issues (full pipeline)