flutter-template: Skill for Claude Code

Flutter Template Create Pull Request

Create or update a GitHub PR for the current branch. This workflow may commit and push, so ask before changing branches, committing, or pushing unless the user's request already clearly authorizes those actions.

Read First

• AGENTS.md
• docs/PROJECT_OVERVIEW.md
• docs/PROJECT_GUIDELINES.md
• git status
• relevant task docs under .claude/tasks/, when present

Step 1: Collect PR Metadata

If the user did not provide these when invoking the skill, ask before proceeding:

1. Type of work: one of chore, feat, fix, refactor
2. Ticket number: e.g. MOB-120, or confirm that there is no ticket
3. Short description: plain-English summary for the commit and PR title

Step 2: Decide Branch And Base

This repo may use stacked PRs. The PR base is the branch the current branch should merge into, which is not always the default branch.

Try to detect the parent branch:

git show-branch --all 2>/dev/null \
  | grep '\*' \
  | grep -v "$(git rev-parse --abbrev-ref HEAD)" \
  | head -1 \
  | sed 's/.*\[\(.*\)\].*/\1/' \
  | sed 's/[\^~].*//'

Alternative: use git log --format=%D HEAD --decorate and pick the nearest branch that is not HEAD.

If detection fails or is ambiguous, ask the user which branch this PR should target.

Ask whether to create a new branch or push the current branch unless the user already made that clear:

Should I create a new branch for these changes, or push to the current branch <current>? The PR will target <detected-or-confirmed-base>.

If creating a new branch, ask for the branch name or derive one from <type>/<ticket>/<slug>.

Step 3: Verify Build And Review

Run the build-verify skill:

.claude/skills/build-verify/scripts/verify.sh

It runs the Flutter verification suite for this repo: dependency sync, code generation when needed, analyzer, tests, iOS and Android native builds when in scope, and formatting. If it fails, fix the root cause and re-run before continuing.