dev:auto:fetch-issue
Récupérer le contenu d'une issue GitHub - Mode AUTO (Phase 0)
What this skill does
# Objectif
## Instructions à Exécuter
**IMPORTANT : Exécute ce workflow étape par étape :**
Phase 0 (Initialisation) du workflow automatisé : récupérer la specification depuis une issue GitHub.
Exécuté au démarrage du workflow avant Phase 1.
# Instructions
## 1. Valider le paramètre
- Vérifier que l'argument est un numéro valide
- Exit avec erreur si pas un numéro
```bash
issue_number=$ARGUMENTS
if ! [[ "$issue_number" =~ ^[0-9]+$ ]]; then
echo "❌ Erreur : l'argument doit être un numéro d'issue GitHub"
echo "Usage: /dev:auto:feature 123"
exit 1
fi
```
## 2. Récupérer l'issue
Utiliser `gh issue view` pour récupérer le contenu :
```bash
issue_data=$(gh issue view "$issue_number" --json title,body,labels,state)
issue_exists=$?
if [ $issue_exists -ne 0 ]; then
echo "❌ Issue #$issue_number non trouvée"
echo "Vérifie que :"
echo " 1. Le numéro est correct"
echo " 2. Tu es authentifié sur GitHub (gh auth login)"
echo " 3. L'issue existe dans le repo courant"
exit 1
fi
```
## 3. Parser les données
Extraire les champs nécessaires :
```bash
# Utiliser jq pour parser
issue_title=$(echo "$issue_data" | jq -r '.title')
issue_body=$(echo "$issue_data" | jq -r '.body')
issue_state=$(echo "$issue_data" | jq -r '.state')
issue_labels=$(echo "$issue_data" | jq -r '.labels | map(.name) | join(", ")')
```
## 4. Valider l'issue
- Vérifier que l'issue est en state "OPEN"
- Vérifier que la description n'est pas vide
```bash
if [ "$issue_state" != "OPEN" ]; then
echo "❌ Issue #$issue_number n'est pas ouverte (state: $issue_state)"
exit 1
fi
if [ -z "$issue_body" ] || [ "$issue_body" == "null" ]; then
echo "⚠️ Issue #$issue_number : description vide"
echo "Ajoute une description détaillée avant de relancer le workflow"
exit 1
fi
```
## 5. Afficher les infos
```
🔗 Issue GitHub récupérée
#$issue_number : $issue_title
État : $issue_state
Labels : $issue_labels
Description :
───────────────────────────────
$issue_body
───────────────────────────────
```
## 6. Sauvegarder dans le workflow state
Déterminer le chemin :
```bash
issue_number=$ARGUMENTS
workflow_state_file=".claude/data/workflows/issue-${issue_number}-dev-workflow-state.json"
mkdir -p ".claude/data/workflows"
```
Créer le fichier `.dev-workflow-state.json` :
```json
{
"mode": "auto",
"issue": {
"number": $issue_number,
"title": "$issue_title",
"description": "$issue_body",
"labels": "$issue_labels",
"state": "$issue_state",
"fetchedAt": "{ISO timestamp}"
},
"feature": "$issue_title",
"status": "in_progress",
"startedAt": "{ISO timestamp}",
"currentPhase": 0,
"phases": {
"0": {
"status": "completed",
"completedAt": "{ISO timestamp}",
"durationMs": {durée}
}
}
}
```
## 7. Transférer à Phase 1
Passer la spec de l'issue à `discover.md` en paramètre :
```bash
spec="Issue #$issue_number: $issue_title\n\n$issue_body"
# Cette spec sera utilisée dans Phase 1 (Discover)
```
# Règles
- ✅ **Valider le numéro** (doit être entier)
- ✅ **Vérifier que l'issue existe** (gh auth required)
- ✅ **Vérifier que l'issue est OPEN**
- ✅ **Vérifier que la description n'est pas vide**
- ✅ **Sauvegarder dans workflow state** avec issue metadata
- ✅ **Afficher les infos** pour transparence
- ❌ **Ne pas modifier l'issue** (read-only)
- ❌ **Ne pas continuer si l'issue est invalide** (exit 1)
# Cas d'erreur
## Issue non trouvée
```
❌ Issue #123 non trouvée
Vérifie que :
1. Le numéro est correct
2. Tu es authentifié sur GitHub (gh auth login)
3. L'issue existe dans le repo courant
```
## Issue fermée
```
❌ Issue #123 n'est pas ouverte (state: CLOSED)
```
## Description vide
```
⚠️ Issue #123 : description vide
Ajoute une description détaillée avant de relancer le workflow
```
# Dépendances
- `gh` CLI installé et authentifié (`gh auth login`)
- Exécuté depuis le repo contenant l'issue
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce 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).
relationship-science-coach
IncludedUse 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.
building-sf-integrations
IncludedSalesforce 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).
venue-templates
IncludedAccess 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.
let-fate-decide
IncludedDraws 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.
net-ops
IncludedCross-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.