Menú
Use after all work on a feature branch is complete and verified. Pushes the branch and creates a PR targeting main.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Use at the start of a manual executor session to find and claim a ready bead. Do not invoke in planner sessions or inside swarm workers.
Use after implementation and verification are complete to close the bead, create follow-up beads, and commit the updated `.beads/` state. This is the final step of a manual executor session.
Break a discussed or approved problem into Beads epics and tasks with clear dependencies and validation work. Use when the user wants to turn a problem statement, planning discussion, or approved execution plan into a Beads structure instead of ad-hoc TODOs.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements, and design before implementation.
Use after implementing changes to run the exact verification commands from the current execution plan. This stage-1 version is intentionally generic and should be specialized per repo once the runtime workflow is clear.
Execute one assigned bead inside a swarm coordinated by swarm-epic. Use only when a coordinator has assigned the bead, file scope, and verification contract; the worker implements, verifies, and reports without mutating bead state.
| name | finishing-a-development-branch |
| description | Use after all work on a feature branch is complete and verified. Pushes the branch and creates a PR targeting main. |
Workflow position: Final step after all beads are closed and build-and-test passes. See BEADS_WORKFLOW.md.
Announce at start: "I'm using the finishing-a-development-branch skill to push and create a PR."
Before invoking this skill, ensure:
build-and-test passesgit status
git log --oneline main..HEAD
git push -u origin HEAD
If push fails (e.g., no remote, auth issues), report the error and stop.
gh pr create --base main --fill
--fill to auto-populate title and body from commits--title and --body insteadPR created: <url>
Branch: <branch-name>
gh is not available, push the branch and report the branch name for manual PR creation| Situation | Action |
|---|---|
| Uncommitted changes | Stop, ask user to commit |
| No commits ahead of main | Stop, nothing to PR |
| Push fails | Report error, stop |
gh not installed | Push branch, report for manual PR |
| PR creation fails | Report error, branch is pushed |
git status, confirm the current checkout still resolves the Beads database with bd where..beads state through Git during normal branch completion.bd where fails, stop and repair the checkout with bd bootstrap --yes before pushing or creating a PR.Called by:
executor-loop-epic — after all beads in the epic are closedPairs with:
build-and-test — must pass before invoking this skill