Crew Open Pr

This handles the common case where feature branches are based on other feature branches in your fork, not on upstream's main.

Read these sources (in order of priority):

1. SPEC.md — resolve TASK_DIR using the canonical resolution recipe (see Session Capture block below) and read $TASK_DIR/SPEC.md for goal, context, acceptance criteria, and ## Tests > ### Manual section
2. Runbook — check for $TASK_DIR/runbook.md; if present, read its **Pass:** lines to extract human-judgment verification steps for the "How to test" section (do NOT include the file path — it's a local agent artifact, not committed to the repo)
3. Commit log — git log $BASE..HEAD --oneline for what was done
4. Full diff — git diff $BASE...HEAD --stat for scope; git diff $BASE...HEAD for details if the stat is small enough (<30 files)

Step 2: Generate the description

Use the template in pr-template.md

Step 3: Push and create the PR

git push -u origin HEAD

Present the title and description to the user. Title format: same as the primary commit message, or a summary if there are multiple commits.

Before creating, ask: "Did you use LLM assistance for this PR?" If yes, append to the end of the description body:

---
🤖 Co-authored with AI assistance.

After approval:

gh pr create --draft --title "TITLE" --body "BODY" --base BASE --repo "$TARGET_REPO"

PRs are always opened as drafts. Mark ready for review manually when appropriate.

If the repo uses a PR template, read it first and fill in the sections rather than using the default format above.

Step 4: Report back

Show the PR URL and a one-line summary.

Next: build workflow complete. Watch for review comments — run crew resolve PR if they arrive.

Session Capture

After creating the PR, resolve TASK_DIR and append to $TASK_DIR/SESSION.md (if found):

if [ -n "${CREW_TASK_DIR+x}" ]; then
  TASK_DIR="$CREW_TASK_DIR"
elif TASK_DIR=$(~/.agent/tools/resolve-task-dir.py 2>/dev/null); then
  export CREW_TASK_DIR="$TASK_DIR"
else
  echo "Warning: resolve-task-dir failed — check git remote and branch." >&2
  TASK_DIR=""
fi

[TIME] crew-open-pr: PR_URL — PR_TITLE

Also log the transition:

~/.agent/tools/log-progress.py "$TASK_DIR" "COMMITTING → PR_OPEN ($PR_URL)"

Then suggest: "Want to journal this session?"

Rules

• Derive, don't invent. The summary comes from SPEC.md and commits, not from re-reading the code.
• Always ask before creating. Show the title + description and wait for "looks good" — same pattern as crew-commit.
• Always draft. PRs are opened as drafts. Mark ready manually.