skills/dimon94/flow-finishing-branch/SKILL.md
Decide how to complete a development branch: merge, PR, squash, or cleanup.
npx skillsauth add aiskillstore/marketplace flow-finishing-branchInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
When development work is complete, you need to decide how to integrate it. This skill guides that decision.
When to use:
- Small changes (< 5 files)
- Single developer
- No review needed
- Clean commit history
Command:
git checkout main
git merge --ff-only feature/xxx
git branch -d feature/xxx
Pros:
- Fast
- Clean history
- No merge commit
Cons:
- No review record
- No CI verification
When to use:
- Team projects
- Need review record
- CI verification required
- Production code
Command:
git push -u origin feature/xxx
gh pr create --title "..." --body "..."
Pros:
- Review record
- CI verification
- Discussion thread
- Audit trail
Cons:
- Takes longer
- Requires reviewer
When to use:
- Many small commits
- Messy commit history
- Want single commit in main
Command:
gh pr merge --squash
Pros:
- Clean main history
- Single logical commit
- Hides WIP commits
Cons:
- Loses detailed history
- Harder to bisect
When to use:
- Work was abandoned
- Experiment failed
- Requirements changed
Command:
git checkout main
git branch -D feature/xxx
git push origin --delete feature/xxx # if pushed
Pros:
- Clean slate
- No dead branches
Cons:
- Work is lost (unless needed later)
┌─────────────────────────────────────────────────────────────┐
│ Decision Matrix │
├─────────────────────────────────────────────────────────────┤
│ │
│ Files Changed Review Needed History Clean Action │
│ ───────────── ───────────── ───────────── ────── │
│ < 5 No Yes A) FF │
│ < 5 No No C) Sq │
│ Any Yes Yes B) PR │
│ Any Yes No C) Sq │
│ N/A N/A N/A (abandoned) D) Del │
│ │
└─────────────────────────────────────────────────────────────┘
Before choosing any option, verify:
□ All tests pass
□ Build succeeds
□ No lint errors
□ Documentation updated (if needed)
□ EXECUTION_LOG.md updated
□ No uncommitted changes
1. Verify completion
→ Run tests, build, lint
→ Check all tasks done
2. Assess the work
→ How many files changed?
→ Is review needed?
→ Is commit history clean?
3. Choose option
→ Use decision matrix
→ Default to PR if unsure
4. Execute
→ Run appropriate commands
→ Verify success
5. Cleanup
→ Delete local branch
→ Delete remote branch (if not PR)
| Excuse | Reality | |--------|---------| | "PR is overkill" | PR provides audit trail. Use it. | | "I'll review my own code" | Self-review misses issues. Get another pair of eyes. | | "History doesn't matter" | History helps debugging. Keep it clean. | | "Just merge it" | Verify first. Merge second. |
This skill is used in /flow-release to decide branch handling:
/flow-release execution:
1. Verify all gates pass
2. Load this skill
3. Present options to user
4. Execute chosen option
5. Update status
[PROTOCOL]: 变更时更新此头部,然后检查 CLAUDE.md
development
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
tools
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
testing
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
tools
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.