git-branch-core

Included with Lifetime

$97 forever

Skill interne fournissant les scripts communs pour la création de branches. Ne pas appeler directement - utilisé par git:branch et git:worktree.

Generalscripts

What this skill does


# Git Branch Core (Internal)

## Instructions à Exécuter

**IMPORTANT : Exécute ce workflow étape par étape :**


Ce skill fournit les scripts partagés pour la résolution de noms de branches. Il ne doit pas être appelé directement.

## Scripts disponibles

| Script | Description | Usage |
|--------|-------------|-------|
| `resolve-branch-name.sh` | Résout un nom de branche depuis un numéro d'issue ou du texte | `bash "$CORE_SCRIPTS/resolve-branch-name.sh" <issue-or-text>` |
| `validate-source-branch.sh` | Valide qu'une branche source existe localement | `bash "$CORE_SCRIPTS/validate-source-branch.sh" <source-branch>` |
| `check-branch-exists.sh` | Vérifie qu'une branche n'existe pas déjà | `bash "$CORE_SCRIPTS/check-branch-exists.sh" <branch-name>` |

## Usage par les skills enfants

```bash
CORE_SCRIPTS="${CLAUDE_PLUGIN_ROOT}/skills/branch-core/scripts"

# Valider la branche source
bash "$CORE_SCRIPTS/validate-source-branch.sh" "$SOURCE_BRANCH"

# Résoudre le nom de branche
eval "$(bash "$CORE_SCRIPTS/resolve-branch-name.sh" "$ISSUE_OR_TEXT")"
# Variables disponibles après eval :
#   $BRANCH_NAME      - Nom complet (ex: feature/42-login-fix)
#   $PREFIX           - Préfixe (ex: feature/)
#   $PREFIX_SOURCE    - Source (label/description/title/default/text)
#   $ISSUE_NUMBER     - Numéro d'issue (vide si texte)
#   $WORKTREE_DIRNAME - Nom répertoire worktree (ex: feature-42-login-fix)

# Vérifier que la branche n'existe pas
bash "$CORE_SCRIPTS/check-branch-exists.sh" "$BRANCH_NAME"
```

## Détection du préfixe

### Par numéro d'issue (priorité décroissante)

1. **Labels de l'issue** :
   - `bug`, `fix`, `bugfix` → `fix/`
   - `hotfix`, `critical`, `urgent` → `hotfix/`
   - `feature`, `enhancement`, `new-feature` → `feature/`
   - `chore`, `maintenance`, `refactor` → `chore/`
   - `documentation`, `docs` → `docs/`
   - `test`, `tests` → `test/`

2. **Description de l'issue** (mots-clés)

3. **Titre de l'issue** (mots-clés)

4. **Défaut** : `feature/`

### Par texte descriptif

- Analyse le premier mot du texte (`fix`, `hotfix`, `chore`, `docs`, `test`, etc.)
- Défaut : `feature/`

## Désambiguisation des arguments

Les skills enfants (`git:branch`, `git:worktree`) partagent la même logique de parsing des arguments.

SOURCE_BRANCH est **optionnel** et défaut à `MAIN_BRANCH` de `.env.claude`.

**Règle de désambiguisation (quand 1 seul argument) :**

| Argument | Type détecté | SOURCE_BRANCH | ISSUE_OR_TEXT |
|----------|-------------|---------------|---------------|
| `42` | Entier | MAIN_BRANCH (.env.claude) | `42` (issue) |
| `develop` | Branche locale existante | `develop` | Non fourni (demander) |
| `"fix login bug"` | Texte | MAIN_BRANCH (.env.claude) | `"fix login bug"` |

**Cascade de résolution de SOURCE_BRANCH :**
1. Argument explicite (premier de deux arguments, ou unique argument si branche existante)
2. `MAIN_BRANCH` de `.env.claude`
3. AskUserQuestion en dernier recours

Files: 4

Size: 9.3 KB

Complexity: 36/100

Category: General

Source: https://github.com/atournayre/claude-marketplace/tree/main/git/skills/branch-core

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