From beads-planner
Stages .beads/ and .plan/, commits changes on issue branch, pushes to remote, and labels GitHub issue 'Ready'. Use as final step after syncing beads or standalone.
npx claudepluginhub jbdamask/john-claude-skills --plugin beads-plannerThis skill uses the workspace's default tool permissions.
Stages the `.beads/` directory, commits, pushes the branch, and labels the corresponding GitHub issue as "Ready". This is the final step in the issue-to-beads workflow.
Creates fix/feature branches from upstream/main for beads/gastown forks: selects bead via bd, implements changes, submits upstream PR, cherry-picks to fork.
Stages all changes, creates a conventional commit with Claude footer, and pushes to remote branch using bash script. Activates on explicit push requests, saving to remote, or feature completion.
Pushes local Git commits to remote repositories, handling branch tracking, upstream setup, safe push patterns like force-with-lease, and verification. Useful after local commits when syncing to remote.
Share bugs, ideas, or general feedback.
Stages the .beads/ directory, commits, pushes the branch, and labels the corresponding GitHub issue as "Ready". This is the final step in the issue-to-beads workflow.
<issue-number>-<slug>)bd sync has been run or will be run here)gh CLI must be authenticated for the target GitHub repobd CLI must be available on PATH.beads/ directory must exist with filed beadsgit pull --rebase
If this fails due to conflicts, stop and ask the user how to resolve them.
bd sync
This ensures the JSONL index is up to date with the beads on disk.
git add .beads/
git add .plan/
Stage .beads/ (the filed beads) and .plan/ (the approved plan artifact). Do not stage unrelated changes. If there are other files that should be committed, ask the user before staging them.
Infer the issue number and title from the current branch name. The branch follows the pattern <issue-number>-<slug> (e.g., 42-add-user-authentication).
# Get branch name
git rev-parse --abbrev-ref HEAD
# Commit with descriptive message
git commit -m "Add beads for issue #<number>: <title-from-slug>"
Replace <number> with the issue number extracted from the branch name, and <title-from-slug> with the slug portion converted back to readable text (hyphens to spaces).
git push -u origin <branch-name>
If the push fails (e.g., due to remote changes), try:
git pull --rebase
git push -u origin <branch-name>
If it still fails, stop and ask the user for help.
Confirm the issue number with the user before labeling:
I inferred issue #<number> from branch
<branch-name>. Should I add the "Ready" label to this issue?
After confirmation:
gh issue edit <number> --add-label "Ready"
If the label doesn't exist on the repo, show the error and suggest the user create it manually or pick a different label.
git status
This must show the branch is up to date with the remote. If it doesn't, diagnose and fix before declaring success.
git pull --rebase and retry once. If still failing, ask the user.git status to diagnose. The beads may already be committed, or bd sync may not have produced changes. Ask the user how to proceed.