git-push-and-tag

Included with Lifetime

$97 forever

Final-phase skill that stages beads, commits, pushes to the remote branch, and labels the GitHub issue as "Ready". Invoked by issue-to-beads as the last step after all beads have been filed, reviewed, and synced. Can also be used standalone when you have synced beads on an issue branch that need to be committed and pushed.

General

What this skill does

# Git Push and Tag

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.

## Prerequisites

- Must be on an issue branch (pattern: `<issue-number>-<slug>`)
- Beads must already be synced (`bd sync` has been run or will be run here)
- The `gh` CLI must be authenticated for the target GitHub repo
- The `bd` CLI must be available on PATH
- The `.beads/` directory must exist with filed beads

## Workflow

### Step 1: Pull latest changes

```bash
git pull --rebase
```

If this fails due to conflicts, stop and ask the user how to resolve them.

### Step 2: Sync beads

```bash
bd sync
```

This ensures the JSONL index is up to date with the beads on disk.

### Step 3: Stage the beads directory

```bash
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.

### Step 4: Commit

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`).

```bash
# 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).

### Step 5: Push

```bash
git push -u origin <branch-name>
```

If the push fails (e.g., due to remote changes), try:

```bash
git pull --rebase
git push -u origin <branch-name>
```

If it still fails, stop and ask the user for help.

### Step 6: Label the GitHub issue

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:

```bash
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.

### Step 7: Verify

```bash
git status
```

This must show the branch is up to date with the remote. If it doesn't, diagnose and fix before declaring success.

## Error Handling

- **Push fails**: Suggest `git pull --rebase` and retry once. If still failing, ask the user.
- **Label fails**: Show the error message. Common causes: label doesn't exist, insufficient permissions, wrong issue number. Suggest manual labeling as a fallback.
- **Commit fails (nothing to commit)**: Run `git status` to diagnose. The beads may already be committed, or `bd sync` may not have produced changes. Ask the user how to proceed.
- **Branch name doesn't match pattern**: Ask the user to provide the issue number manually.

Files: 1

Size: 3.2 KB

Complexity: 13/100

Category: General

Source: https://github.com/jbdamask/john-claude-skills/tree/main/plugins/beads-planner/skills/git-push-and-tag

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts