From flutter-craft
Verifies tests and builds for completed Flutter features, then presents options to merge locally to base branch, push and create GitHub PR, keep as-is, or discard.
npx claudepluginhub vp-k/flutter-craftThis skill uses the workspace's default tool permissions.
Guide completion of Flutter development work by presenting clear options and handling chosen workflow.
Finishes Git development branches: verifies tests pass, presents options to merge locally, push/create GitHub PR, keep as-is, or discard; executes choice and cleans up worktrees.
Guides finishing development branches: verifies tests pass, presents options for local merge, GitHub PR creation, keeping as-is, or discard, executes git/gh commands, cleans worktrees.
Verifies tests pass on completed feature branch, presents options to merge locally, create GitHub PR, keep as-is or discard; executes choice and cleans up worktree.
Share bugs, ideas, or general feedback.
Guide completion of Flutter development work by presenting clear options and handling chosen workflow.
Core principle: Verify tests → Present options → Execute choice → Clean up
Announce at start: "I'm using the flutter-finishing skill to complete this work."
Before presenting options, verify everything passes:
# Static analysis
flutter analyze
# Expected: No issues found!
# All tests
flutter test
# Expected: All tests passed!
# Optional: Build check
flutter build apk --debug
# Expected: Built successfully
If tests fail:
Flutter tests failing (N failures). Must fix before completing:
[Show failures]
Cannot proceed with merge/PR until tests pass.
STOP. Don't proceed to Step 2.
If tests pass: Continue to Step 2.
# Find merge base
git merge-base HEAD main 2>/dev/null || git merge-base HEAD master 2>/dev/null
# Or ask: "This branch split from main - is that correct?"
Present exactly these 4 options:
Implementation complete. All tests passing. What would you like to do?
1. Merge back to <base-branch> locally
2. Push and create a Pull Request
3. Keep the branch as-is (I'll handle it later)
4. Discard this work
Which option?
Don't add explanation - keep options concise.
# Switch to base branch
git checkout <base-branch>
# Pull latest
git pull
# Merge feature branch
git merge <feature-branch>
# Verify tests on merged result
flutter analyze
flutter test
# If tests pass, delete feature branch
git branch -d <feature-branch>
Then: Cleanup worktree (Step 5)
# Push branch
git push -u origin <feature-branch>
# Create PR
gh pr create --title "<feature-title>" --body "$(cat <<'EOF'
## Summary
- Implemented [feature] following Clean Architecture
- Added [Layer] layer components
- [Test coverage details]
## Test Plan
- [ ] flutter analyze passes
- [ ] flutter test passes
- [ ] Manual testing of [scenarios]
## Flutter Version
- Flutter: X.X.X
- Dart: X.X.X
🤖 Generated with [Claude Code](https://claude.com/claude-code)
EOF
)"
Don't cleanup worktree - might need for PR review fixes.
Report: "Keeping branch <name>. Worktree preserved at <path>."
Don't cleanup worktree.
Confirm first:
This will permanently delete:
- Branch: <name>
- All commits: <commit-list>
- Worktree at: <path>
Type 'discard' to confirm.
Wait for exact confirmation.
If confirmed:
git checkout <base-branch>
git branch -D <feature-branch>
Then: Cleanup worktree (Step 5)
For Options 1, 2, 4:
Check if in worktree:
git worktree list | grep $(git branch --show-current)
If yes:
# Navigate to main repo
cd <main-repo-path>
# Remove worktree
git worktree remove <worktree-path>
For Option 3: Keep worktree.
| Option | Merge | Push | Keep Worktree | Cleanup Branch |
|---|---|---|---|---|
| 1. Merge locally | ✓ | - | - | ✓ |
| 2. Create PR | - | ✓ | ✓ | - |
| 3. Keep as-is | - | - | ✓ | - |
| 4. Discard | - | - | - | ✓ (force) |
Before allowing completion:
# 1. Analysis must pass
flutter analyze
# Must show: No issues found!
# 2. Tests must pass
flutter test
# Must show: All tests passed!
# 3. (Optional) Build verification
flutter build apk --debug
# Must show: Built build/app/outputs/...
Skipping test verification
Open-ended questions
Automatic worktree cleanup
No confirmation for discard
Never:
Always:
Called by:
Pairs with: