Run any Skill in Manus with one click

$pwd:

gwt-manage-pr

Name: Gwt Manage Pr
Author: akiojin

// Use when the user wants to create, inspect, update, or unblock a pull request and expects one visible entrypoint for the PR lifecycle.

Run Skill in Manus

$ git log --oneline --stat

stars:3

forks:0

updated:May 6, 2026 at 07:39

File Explorer

5 files

SKILL.md

readonly

package.json

"author": "akiojin"

"repository": "akiojin/gwt"

View GitHub Repository

$ install --globalskills.sh

$ download --local

Run Skill in Manus

[HINT] Download the complete skill directory including SKILL.md and all related files

Run any Skill with one click

name	gwt-manage-pr
description	Use when the user wants to create, inspect, update, or unblock a pull request and expects one visible entrypoint for the PR lifecycle.

gwt-manage-pr — Unified PR Lifecycle Manager

Overview

Single skill for the full PR lifecycle: create, check status, and fix blockers. Auto-detects the appropriate mode from current branch PR state, or accepts an explicit mode from the user.

Use the current user's language for decision summaries, blocker reports, and next-step guidance returned from this workflow.

Canonical agent-facing surface is gwtd pr ... / gwtd actions ... for PR inspection, create/update, and fix flows. The current implementation may still use GitHub REST / gh internally as transport, while GraphQL remains the transport for unresolved review threads and thread reply/resolve.

Final Report Contract

Every final user-facing report from this workflow MUST state whether a PR was created, updated, fixed, or left unchanged. When a PR was created, pushed to, or fixed, include a PR Update Summary derived from the actual diff, commit range, and PR body. Do not invent changes from intent alone.

PR Update Summary must include:

PR number and URL
base/head branches
commit count or updated commit range
2-5 bullets describing what the PR updates
related Issue/SPEC numbers, or None
verification and CI/review status

For check and NO ACTION results, explicitly say no PR update was made. If an existing PR is only inspected, summarize the current PR status separately from PR Update Summary so the report does not imply new changes were pushed.

Final report shape:

## PR Result
- Action: Created | Updated | Fixed | Checked | No Action
- PR: #<number> <url> | None
- Branches: <base> <- <head>

### PR Update Summary
- Commits: <count or range>
- Updates:
  - <what changed>
- Related: #<issue/spec> | None
- Verification: <commands/checks and status>

### Next
- <remaining blocker or "None">

Omit PR Update Summary only when no PR was created, updated, or fixed; in that case include PR Update: none in the result.

gwtd resolution

Before executing any gwtd ... command from this skill or its references, resolve GWT_BIN first: executable GWT_BIN_PATH, then command -v gwtd, then $GWT_PROJECT_ROOT/target/debug/gwtd or ./target/debug/gwtd. Run the command as "$GWT_BIN" ...; if none exists, stop with an actionable gwtd not found error.

Mode Auto-Detection

On invocation, run Shared Preflight, then route:

Preflight — always runs first (see Shared Preflight).
Explicit mode (user said "check" / "fix" / "create"):
- "check status" / "PR status" / "is it merged?" → check mode
- "fix CI" / "fix the PR" / "resolve blockers" → fix mode
- "create PR" / "open PR" → create mode (with smart skip if open PR exists)
Auto-detect (no explicit mode) — use the commit-count-first decision from Preflight Step 7:
- open PR + mergeable: CONFLICTING|DIRTY|BEHIND → fix
- N > 0 + no open PR → create
- N > 0 + open PR + clean merge state → create (push-only + post-push fix)
- N = 0 + open PR → fix (check CI / reviews / conflicts)
- N = 0 + no open PR → report NO ACTION

Shared Preflight

Every mode begins with these steps. The order is intentional — commit count against the base branch comes before PR state lookup so that the MERGED shortcut ("PR is done therefore nothing to do") is structurally impossible.

Repo + branches:
- git rev-parse --show-toplevel / git rev-parse --abbrev-ref HEAD
- Base defaults to develop unless user specifies.
Branch protection: Only develop may target main. Refuse any other branch targeting main.
Working tree state: git status --porcelain. If dirty, pause and present options (continue / abort / cleanup). Do not auto-commit/stash.
Fetch: git fetch origin
Commit count against base (mandatory first check):
```
N=$(git rev-list --count "origin/$base..HEAD")
```
Baseline ref rule: ALWAYS compare against origin/<base> (the PR target branch, default origin/develop). NEVER use origin/<head> (the remote tracking branch of the current branch) — that only tells you if commits are pushed, not whether develop has your work. Confusing the two is the root cause of the MERGED-state false NO ACTION bug.
PR lookup + open-PR check:
- Prefer gwtd pr current as the normal read path for the current branch.
- Treat the literal line no current pull request as the canonical no-PR sentinel.
- If create mode needs lower-level repo/head lookup, treat it as internal transport managed by the toolchain rather than part of the agent-facing workflow.
- has_open_pr = any entry with state == "open" && merged_at == null
- When an open PR exists, inspect mergeable:. CONFLICTING, DIRTY, and BEHIND are blocking merge states and immediately upgrade routing to fix.
Route using the 2×2 matrix, with merge-state override:

Commits (N) Open PR? Action
N > 0 No CREATE new PR
N > 0 Yes PUSH ONLY to existing PR → then FIX
N = 0 Yes FIX (CI / reviews / conflicts)
N = 0 No NO ACTION

If the open PR reports mergeable: CONFLICTING, DIRTY, or BEHIND, use FIX immediately instead of push-only/create. Outside that override, PR state (MERGED / CLOSED) is not consulted.

Mode: Create

Detailed logic in references/create-flow.md.

Decision Rules

Create mode is entered from the Preflight 2×2 matrix when N > 0.

Do not create or switch branches. Always use the current branch as head.
If open PR exists and is CONFLICTING / DIRTY / BEHIND → enter Fix mode before any push-only path.
If open PR exists and merge state is clean → push only, return existing PR URL, enter Fix mode.
If no open PR → create new PR.
Branch sync: If behind origin/$base, merge origin/$base first (never rebase). Push after merge.

PR Title Rules

Format: <type>(<scope>): <subject> (Conventional Commits)
type: feat/fix/docs/chore/refactor/test/ci/perf
subject: imperative mood, under 70 chars, no capital, no period
Branch prefix feat//fix/ must match title type

PR Body Rules

Template: .codex/skills/gwt-manage-pr/references/pr-body-template.md
Required sections: Summary, Changes, Testing, Closing Issues, Related Issues, Checklist
Conditional sections (remove if N/A): Context, Risk/Impact, Screenshots, Deployment
Remove all  comments from final output
No TODO in required sections; derive content from diff/Issues/SPECs before asking user
Closing Issues: Closes #N or None only. Bare #N without keyword is forbidden.
Add reason to every unchecked checklist item

Create/Update Commands

Create: gwtd pr create --base <base> [--head <head>] --title "<title>" -f <file> [--label <label>]* [--draft]
Update: gwtd pr edit <number> [--title "<title>"] [-f <file>] [--add-label <label>]*
Transport note: the current implementation may still call GitHub REST / gh internally, but agent-facing workflow should stay on the gwtd pr surface.

Post-Create

After PR creation or push, automatically enter fix mode and use gwtd pr checks, gwtd pr reviews, gwtd pr review-threads, and gwtd actions logs/job-logs as the normal inspection path.

Mode: Check

Detailed logic in references/check-flow.md.

Read-only mode. Do not create/switch branches, push, or create/edit PRs.

Canonical Read Surface

Current branch PR: gwtd pr current
PR detail: gwtd pr view <number>
Checks: gwtd pr checks <number>
Reviews: gwtd pr reviews <number>
Unresolved threads: gwtd pr review-threads <number>
Actions logs: gwtd actions logs --run <id> / gwtd actions job-logs --job <id>

Output Contract

Human-readable summary using signal prefixes:

Prefix	Action	Meaning
`>>`	`CREATE PR`	Create a new PR
`>`	`PUSH ONLY`	Push to existing PR
`~`	`FIX`	Fix CI / reviews / conflicts on existing PR
`--`	`NO ACTION`	Nothing to do
`!!`	`MANUAL CHECK`	Manual check required

Per-status templates:

Templates map directly from the Preflight 2×2 matrix:

N > 0, no open PR: >> CREATE PR -- <N> new commit(s) not covered by any PR.
N > 0, open PR, clean merge state: > PUSH ONLY -- Unmerged PR #<number> open for <head>. + PR URL
Open PR with blocking merge state: ~ FIX -- PR #<number> is <mergeable>; resolve base sync/conflicts before push-only.
N = 0, open PR: ~ FIX -- PR #<number> open, checking CI/reviews/conflicts.
N = 0, no open PR: -- NO ACTION -- No commits ahead of <base>, no open PR.
Fallback: !! MANUAL CHECK -- Could not determine commit count. + reason

Append (!) Worktree has uncommitted changes. when dirty.

Commit Count (from Preflight Step 5)

The commit count N = git rev-list --count origin/<base>..HEAD is computed in the Shared Preflight and is the primary routing signal. Check mode simply reports it:

N > 0 + no open PR → >> CREATE PR -- <N> new commit(s) not in any PR.
N > 0 + open PR + clean merge state → > PUSH ONLY -- Unmerged PR open. + PR URL
open PR + mergeable: CONFLICTING|DIRTY|BEHIND → ~ FIX -- PR is blocked by merge state.
N = 0 + open PR → report CI / review / conflict status
N = 0 + no open PR → -- NO ACTION

The old "Post-Merge Commit Check" logic (merge_commit ancestry, fallback chain) is subsumed by git rev-list --count origin/<base>..HEAD which directly answers "does develop have all my work?" regardless of PR state.

Mode: Fix

Detailed logic in references/fix-flow.md.

Inspection Targets

CI failures: REST check-runs + GitHub Actions log extraction
Merge conflicts: mergeable / mergeStateStatus fields (CONFLICTING/DIRTY/BEHIND)
Reviewer comments: REST reviews + inline comments + issue comments (full text, no truncation)
Unresolved threads: GraphQL only
Change requests: Reviews with CHANGES_REQUESTED state

Diagnosis Report (mandatory format)

## Diagnosis Report: PR #<number>

**Merge Verdict: BLOCKED | CLEAR**
Blocking items: <N>

---

### BLOCKING

#### B1. [CATEGORY] <1-line title>
- **What:** Factual statement
- **Where:** file_path:line / check name / branch ref
- **Evidence:** Verbatim quote from output
- **Action:** Specific fix with file path/command
- **Auto-fix:** Yes | No (needs confirmation)

---

### INFORMATIONAL
#### I1. [CATEGORY] <1-line title>
- **What / Note**

---

**Summary:** <N> blocking, <M> informational.

Categories: CONFLICT, BRANCH-BEHIND, CI-FAILURE, CHANGE-REQUEST, UNRESOLVED-THREAD, REVIEW-COMMENT

Classification:

BLOCKING: merge conflicts, BEHIND, CI failure/cancelled/timed_out, CHANGES_REQUESTED, unresolved threads, unanswered review comments (any reviewer comment with no reply)
INFORMATIONAL: review comments that already have a reply, pending CI, outdated threads

Each CHANGE-REQUEST, UNRESOLVED-THREAD, and UNANSWERED-COMMENT is a separate B-item.

Execution Path

All Auto-fix: Yes --> proceed directly to fix.
Any Auto-fix: No --> ask user about those items only.

Fix Implementation

Apply fixes, commit, push.
For BRANCH-BEHIND: git fetch origin <base> && git merge origin/<base> && git push
For CONFLICT: inspect both sides, resolve if clear, ask user if ambiguous.

Comment Response Policy

No reviewer comment may be left unanswered or unresolved.

Every unresolved thread MUST receive a reply AND be resolved.
Reply content (every comment gets a reply, even if no code change was needed):
- Fixed: "Fixed: ." with commit reference.
- Not applicable: "Not applicable: ."
- Already addressed: "Already addressed in commit :
  ."
- Acknowledged: "Acknowledged: ." for informational comments.
After preparing the reply body, use gwtd pr review-threads reply-and-resolve <number> -f <file> to reply to and resolve all unresolved threads on the PR.
If that surface is unavailable, fall back to internal GraphQL transport with resolveReviewThread.
Verification: After resolving, re-check that no unresolved threads remain. Unresolved threads block the Merge Verdict.

Reviewer Notification (mandatory)

Post a PR summary comment via gwtd pr comment <number> -f <file>.

Verify Fix (mandatory)

Re-run inspection with --mode all. Loop until exit code 0.

CI pending --> poll 30s intervals until complete.
After fix push, re-poll for new CI run.

Loop Safety Guard

Same CI check fails 3 consecutive iterations --> report to user, ask continue/abort/change approach.

Diagnosis Report Anti-Patterns

Prohibited	Required Alternative
"We should look into..."	"Edit `path/file.ts:42` to..."
"There seem to be some issues"	"3 blocking items detected"
"This might be causing..."	"Root cause: `<error from log>`"
"Consider fixing..."	"Action: Fix `<what>` in `<where>`"
"Various CI checks are failing"	"2 CI checks failing: `build`, `lint`"

Comment Formatting Rules

No escaped newline literals (\n) in final comment text.
Use real line breaks. Verify before posting.
If raw escape sequences needed for explanation, use fenced code blocks only.

Issue Progress Comment Template

When work is tracked in Issues:

Progress
- ...

Done
- ...

Next
- ...

Bundled Scripts

PR lifecycle work is driven through the canonical gwtd pr ... and gwtd actions ... surfaces. Do not depend on retired repo-local helper script paths when running this workflow.

References

references/create-flow.md -- PR creation workflow details
references/check-flow.md -- PR status checking details
references/fix-flow.md -- CI/conflict/review fix details
references/pr-body-template.md -- PR body template

name	gwt-manage-pr
description	Use when the user wants to create, inspect, update, or unblock a pull request and expects one visible entrypoint for the PR lifecycle.