ship-finish-branch
Skill1 starsChanged 7 months agoMITView on GitHub
Complete a feature branch with merge/PR/keep/discard options. Verifies tests pass, cleans up worktree. Run after ship-test.
In this repository43 other files it gives its agents.
- accessibilitySkill
- agent-evalSkill
- agentic-engineeringSkill
- ai-regression-testingSkill
- api-designSkill
- atomic-planningSkill
- backend-patternsSkill
- coding-standards-eccSkill
- context-engineeringSkill
- frontend-patternsSkill
- git-worktreesSkill
- langchain-dependenciesSkill
- langchain-fundamentalsSkill
- langchain-middlewareSkill
- langchain-ragSkill
- langgraph-fundamentalsSkill
- langgraph-persistenceSkill
- minimalist-skillSkill
- output-skillSkill
- redesign-skillSkill
- security-scanSkill
- ship-architectSkill
- ship-autoSkill
- ship-bugfixSkill
- ship-deploySkill
- ship-discoverSkill
- ship-executeSkill
- ship-newSkill
- ship-planSkill
- ship-researchSkill
- ship-resumeSkill
- ship-reviewSkill
- ship-settingsSkill
- ship-specSkill
- ship-statusSkill
- ship-testSkill
- ship-worktreeSkill
- soft-skillSkill
- systematic-debuggingSkill
- taste-skillSkill
- test-driven-developmentSkill
- two-stage-reviewSkill
- verification-before-completionSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Verify all tests pass on the current feature branch.
- Very specific: line 19
Update progress.json with branch status.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Finish branch — Complete the feature
Process
- Verify all tests pass on the current feature branch.
- Present options:
- A. Merge to main (squash commits into one)
- B. Merge to main (keep individual commits)
- C. Open a Pull Request (for team review)
- D. Keep the branch (come back later)
- E. Discard (delete branch and worktree)
- Execute the chosen option.
- Clean up the git worktree after merge or discard.
- Update
progress.jsonwith branch status. - Output: "Run
/bayes-ship:ship-deployto deploy to production."
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.