Git CD PR - Continuous Delivery

VerifiedCaution

This skill creates a Pull Request following a complete Continuous Delivery workflow. It runs intelligent QA, applies version labels (major/minor/patch) and feature flags, and triggers automatic code review if the plugin is installed.

Sby Skills Guide Bot
DevelopmentIntermediate
6/2/2026
Claude Code
#git#pull-request#continuous-delivery#qa#labels

Recommended for

Automated summary

Automatically creates a Pull Request with a full Continuous Delivery workflow including QA, version and feature flag labels, and automated code review.

Strengths

  • Fully automates the PR creation process with validation and verification steps.
  • Integrates intelligent QA and change analysis to ensure quality.
  • Handles version labels (major/minor/patch) and feature flags directly from the PR.

Limitations

  • Requires specific shell and Python scripts in the project's scripts directory.
  • Depends on external plugins for automatic code review.
  • The workflow is lengthy (15 steps) and may be slow on complex projects.
When to use it

Use when you want to standardize and automate Pull Request creation with a robust Continuous Delivery pipeline.

When not to use it

Avoid for small, fast changes that don't require QA or version management, or if the project lacks the prerequisite scripts.

Security analysis

Caution
Quality score85/100

The skill uses Bash and git operations extensively, which are powerful and could cause harm if misused, but the described actions are legitimate for a CI/CD workflow. There is no instruction to execute arbitrary code or exfiltrate data. The main risk is reliance on external configuration and scripts, but it does not appear to bypass safety mechanisms intentionally.

Findings
  • •Executes external Bash scripts and git commands that interact with remote repositories, posing a risk if misconfigured or if the scripts themselves contain vulnerabilities.
  • •Reads environment variables from .env.claude file; while it only parses KEY=VALUE pairs, an attacker-controlled file could influence branch names and other parameters used in git operations.
  • •The skill does not validate the contents of .env.claude, potentially allowing injection of unexpected values into commands like git push.
How this analysis is made

Examples

Create a CD PR to develop branch with milestone
/git:pr --cd develop v2.0
Create a CD PR without interaction and delete local branch
/git:pr --cd main --no-interaction --delete

name: git-cd-pr description: > Crée une Pull Request en mode Continuous Delivery avec workflow complet : QA, labels version (major/minor/patch), feature flags, code review automatique. allowed-tools: [Bash, Read, Write, TaskCreate, TaskUpdate, TaskList, AskUserQuestion] model: sonnet

Git CD PR Skill (Continuous Delivery)

Instructions à Exécuter

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

Usage

/git:pr --cd [branche-base] [milestone] [projet] [--no-interaction] [--delete] [--no-review]

Configuration

CORE_SCRIPTS="${CLAUDE_PLUGIN_ROOT}/skills/git-pr-core/scripts"
SCRIPTS_DIR="${CLAUDE_PLUGIN_ROOT}/skills/git-cd-pr/scripts"
PR_TEMPLATE_PATH=".github/PULL_REQUEST_TEMPLATE/cd_pull_request_template.md"
ENV_FILE_PATH=".env.claude"

Workflow

Initialisation

Créer les tâches du workflow :

Utiliser TaskCreate pour chaque étape :

TaskCreate #1: Charger config .env.claude
TaskCreate #2: Confirmation initiale (si --no-interaction absent)
TaskCreate #3: Vérifier scopes GitHub
TaskCreate #4: Vérifier template PR CD
TaskCreate #5: Lancer QA intelligente
TaskCreate #6: Analyser changements git
TaskCreate #7: Confirmer branche de base
TaskCreate #8: Générer description PR
TaskCreate #9: Push et créer PR
TaskCreate #10: Copier labels depuis issue liée
TaskCreate #11: Appliquer labels CD (version + feature flag)
TaskCreate #12: Assigner milestone
TaskCreate #13: Assigner projet GitHub
TaskCreate #14: Code review automatique (si plugin installé)
TaskCreate #15: Nettoyage branche locale

Important :

  • Utiliser activeForm (ex: "Chargeant config", "Appliquant labels CD")
  • Ne créer la tâche #14 que si plugin review installé ET --no-review absent
  • Chaque tâche doit être marquée in_progress puis completed

Pattern d'exécution pour chaque étape :

  1. TaskUpdate → tâche en in_progress
  2. Exécuter l'étape
  3. TaskUpdate → tâche en completed

Étapes

  1. Charger configuration depuis .env.claude :

    • Vérifier si le fichier .env.claude existe à la racine du projet
    • Si oui, parser les variables (format KEY=VALUE) :
      • MAIN_BRANCH : branche de base par défaut
      • PROJECT : projet GitHub par défaut
    • Pour chaque paramètre manquant dans les arguments :
      • Utiliser la variable d'env correspondante si elle existe
    • Ignorer .env.claude si absent (comportement standard)
  2. Confirmation initiale :

    • Si flag --no-interaction présent :
      • Passer toutes les confirmations
      • Utiliser les valeurs pré-remplies (arguments + .env.claude) sans validation
      • Continuer directement à l'étape 3
    • Sinon :
      • Confirmer à l'utilisateur que la skill git:cd-pr est lancée
      • Résumer tous les paramètres reçus :
        • Mode : Continuous Delivery (--cd)
        • Branche de base (si fournie)
        • Milestone (si fourni)
        • Projet (si fourni)
        • Flags : --delete, --no-review (si présents)
      • Demander confirmation explicite avant de continuer
  3. Vérifier scopes GitHub ($CORE_SCRIPTS/check_scopes.sh)

  4. Vérifier template PR CD ($CORE_SCRIPTS/verify_pr_template.sh)

  5. Lancer QA intelligente ($CORE_SCRIPTS/smart_qa.sh)

  6. Analyser changements git ($CORE_SCRIPTS/analyze_changes.sh)

  7. Confirmer branche de base (ou AskUserQuestion)

  8. Générer description PR intelligente

  9. Push et créer PR avec titre Conventional Commits (scripts/create_pr.sh)

  10. Copier labels depuis issue liée (scripts/copy_issue_labels.sh)

  11. Appliquer labels CD (scripts/apply_cd_labels.sh)

  12. Assigner milestone ($CORE_SCRIPTS/assign_milestone.py - voir git-pr-core/SKILL.md pour usage)

  13. Assigner projet GitHub ($CORE_SCRIPTS/assign_project.py - voir git-pr-core/SKILL.md pour usage)

  14. Code review automatique (si plugin review installé)

  15. Nettoyage branche locale ($CORE_SCRIPTS/cleanup_branch.sh - branche remote préservée)

Labels CD (Continuous Delivery)

Ordre de détection du type de version :

  1. BREAKING CHANGE ou !: dans commits → version:major
  2. Labels de l'issue liée (insensible casse, ignore emojis) :
    • Patterns minor : enhancement, feature, feat, nouvelle, new
    • Patterns patch : bug, fix, bugfix, correction, patch
  3. Nom de branche : feat/*, feature/* → minor / fix/*, hotfix/* → patch
  4. Premier commit de la branche : feat: → minor / fix: → patch
  5. Si indéterminé → AskUserQuestion :

    "Cette PR est une nouvelle fonctionnalité (minor) ou une correction (patch) ?"

Feature flag :

  • Détecté si fichiers .twig modifiés contiennent Feature:Flag ou Feature/Flag
  • Applique le label 🚩 Feature flag

Création labels : Si labels absents, ils sont créés automatiquement avec couleurs appropriées.

Code Review

Si plugin review installé, lance 4 agents en parallèle :

  • code-reviewer - Conformité CLAUDE.md
  • silent-failure-hunter - Erreurs silencieuses
  • test-analyzer - Couverture tests
  • git-history-reviewer - Contexte historique

Agrège résultats (score >= 80) dans commentaire PR.

Options

| Flag | Description | |------|-------------| | --no-interaction | Mode automatique : passer confirmations, utiliser defaults | | --delete | Supprimer branche LOCALE uniquement après création PR (JAMAIS la branche remote) | | --no-review | Désactiver code review automatique |

References

Task Management

Progression du workflow :

  • 15 tâches créées à l'initialisation (ou 14 si --no-review ou pas de plugin review)
  • Chaque étape suit le pattern : in_progress → exécution → completed
  • Utiliser TaskList pour voir la progression globale
  • Les tâches permettent à l'utilisateur de suivre l'avancement de la création de PR CD

Règles critiques

⚠️ INTERDICTION ABSOLUE :

  • Ne JAMAIS exécuter git push origin --delete <branche> ou git push -d origin <branche>
  • Ne JAMAIS supprimer la branche remote (fermerait automatiquement la PR)
  • Le flag --delete ne concerne QUE la branche locale

Error Handling

  • Template absent → ARRÊT
  • QA échouée → ARRÊT
  • Version non déterminée → AskUserQuestion (non bloquant)
  • Milestone/projet non trouvé → WARNING (non bloquant)

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/git-cd-pr-continuous-delivery-mm78no25/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/git-cd-pr-continuous-delivery-mm78no25' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/git-cd-pr-continuous-delivery-mm78no25/download' --output '.skill-downloads/git-cd-pr-continuous-delivery-mm78no25/SKILL.md.part' && mv '.skill-downloads/git-cd-pr-continuous-delivery-mm78no25/SKILL.md.part' '.skill-downloads/git-cd-pr-continuous-delivery-mm78no25/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/git-cd-pr-continuous-delivery-mm78no25/SKILL.md' && test -s '.skill-downloads/git-cd-pr-continuous-delivery-mm78no25/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/git-cd-pr' && cp -R '.skill-downloads/git-cd-pr-continuous-delivery-mm78no25' '.claude/skills/git-cd-pr'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/git-cd-pr-continuous-delivery-mm78no25'

openskills read 'git-cd-pr-continuous-delivery-mm78no25'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/git-cd-pr-continuous-delivery-mm78no25/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills