Skip to content

docs(autopilot): auto-open review artifacts at human review gates #187

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
jankneumann merged 3 commits into from
Jun 5, 2026
Merged

docs(autopilot): auto-open review artifacts at human review gates #187

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
5c0afa7
docs(autopilot): auto-open review artifacts at human gates
jankneumann May 25, 2026
e85d460
docs(merge-pull-requests): open review artifacts before cleanup approval
jankneumann May 26, 2026
a791035
docs(autopilot): make /review-artifacts invocation best-effort
jankneumann Jun 5, 2026
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
3 changes: 3 additions & 0 deletions skills/autopilot/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -139,6 +139,7 @@ Failure here is non-fatal — the helper logs a warning and writes

If argument was a description (no existing change-id):
- Invoke `/plan-feature <description>` (tier auto-detected based on coordinator availability)
- **Before showing/answering the proposal approval gate prompt**, **best-effort** invoke `/review-artifacts <change-id>` to open proposal/design/spec/tasks artifacts in a new VS Code review session. The helper is local-only (depends on the VS Code CLI / a desktop environment) and will be unavailable in cloud harnesses — treat its failure as non-fatal: log a short notice (`[autopilot] /review-artifacts unavailable — skipping artifact pre-open`) and continue to the approval gate.
- Wait for proposal approval before continuing

If argument was an existing change-id:
Expand Down Expand Up @@ -537,6 +538,8 @@ Write final handoff document.

**STOP — Await human approval for merge via `/cleanup-feature <change-id>`.**

Before presenting merge-approval questions, **best-effort** invoke `/review-artifacts <change-id>` so the reviewer has the relevant artifacts open prior to choosing gate outcomes. The helper is local-only (VS Code CLI dependency) — when it's unavailable (cloud harness, headless CI), log a short notice and proceed to the approval prompt without it; do not block the gate on artifact pre-opening.

## Progress Reporting

At each state transition, report:
Expand Down
1 change: 1 addition & 0 deletions skills/merge-pull-requests/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -517,6 +517,7 @@ Merged local OpenSpec PRs eligible for post-merge cleanup:
|----|-----------|--------|----------------|---------|
| #42 | add-user-export | openspec/add-user-export | 2 worktree registry entries, 3 local branches | `/cleanup-feature add-user-export --post-merge --pr 42` |

Before asking the operator to approve, invoke `/review-artifacts <change-id>` for each listed change-id so review artifacts are open in VS Code first.
Ask the operator: Proceed with post-merge cleanup for these changes?
Only run the listed cleanup commands after explicit approval.
```
Expand Down