new
Create a GitHub issue (or local issue with --local)
What this skill does
# New Issue - Create GitHub Issue
Create a GitHub issue via `gh issue create`. **You do the work directly.**
Use `--local` for offline/private work in `.devloop/issues/`.
## Step 1: Parse Arguments and Check GitHub
Check `$ARGUMENTS` for title/description and `--local` flag.
```bash
"${CLAUDE_PLUGIN_ROOT}/scripts/check-gh-setup.sh"
```
**If `preferred_method` is "none":**
- `gh_installed: false`: Display install instructions, fall back to `--local`
- `gh_authenticated: false`: Prompt `gh auth login`, fall back to `--local`
**If "gh" or "curl":** Continue to GitHub Mode (unless `--local` specified).
---
## Step 2: GitHub Mode
### 2.1 Collect Info
```yaml
AskUserQuestion:
questions:
- question: "What type of issue?"
header: "Type"
multiSelect: false
options:
- label: "Bug"
description: "Something isn't working correctly"
- label: "Feature"
description: "New functionality or enhancement"
- label: "Task"
description: "General work item or chore"
- question: "Add labels?"
header: "Labels"
multiSelect: true
options:
- label: "bug"
description: "Bug fix"
- label: "enhancement"
description: "New feature or improvement"
- label: "devloop"
description: "Related to devloop plugin"
- label: "documentation"
description: "Documentation update"
```
Auto-add type label: Bug → "bug", Feature → "enhancement".
### 2.2 Title and Body
If no title in arguments, prompt for it. Then ask for description (what, why, context, acceptance criteria).
### 2.3 Create Issue
```bash
gh issue create \
--title "${title}" \
--body "${body}" \
--label "${labels_comma_separated}" \
--repo $(git remote get-url origin | sed 's/.*[:/]\([^/]*\/[^/]*\)\.git/\1/')
```
Parse issue URL and number from output.
### 2.4 Next Actions
```yaml
AskUserQuestion:
questions:
- question: "Issue #N created. What next?"
header: "Next"
multiSelect: false
options:
- label: "Start work"
description: "Create plan from this issue"
- label: "Create more"
description: "Create another issue"
- label: "View issues"
description: "List all open issues"
- label: "Done"
description: "Return to conversation"
```
Route: Start → `/devloop:plan --from-issue N`, More → loop, View → `/devloop:issues`, Done → exit.
---
## Step 3: Local Mode
**Only if `--local` specified or GitHub unavailable.**
### 3.1 Collect Info
```yaml
AskUserQuestion:
questions:
- question: "What type of issue?"
header: "Type"
multiSelect: false
options:
- label: "Bug"
description: "Something isn't working"
- label: "Feature"
description: "New functionality"
- label: "Task"
description: "General work item"
- label: "Spike"
description: "Research or investigation"
- question: "Priority?"
header: "Priority"
multiSelect: false
options:
- label: "High"
description: "Urgent"
- label: "Medium (Recommended)"
description: "Normal priority"
- label: "Low"
description: "Nice to have"
- question: "Labels?"
header: "Labels"
multiSelect: true
options:
- label: "devloop"
description: "Related to devloop"
- label: "commands"
description: "Related to commands"
- label: "agents"
description: "Related to agents"
- label: "ux"
description: "User experience"
```
### 3.2 Type-Specific Details
**Bug:** Severity (Critical/Major/Minor/Cosmetic)
**Feature/Task:** Size estimate (XS/S/M/L)
**Spike:** Depth (Quick/Standard/Deep)
### 3.3 Title and Description
If no title, prompt. Then ask for description.
### 3.4 Generate Issue ID
```bash
ls .devloop/issues/${TYPE}-*.md 2>/dev/null | wc -l
```
Format: `{TYPE}-{NUMBER}` (e.g., FEAT-003).
### 3.5 Create Issue File
Write to `.devloop/issues/${TYPE}-${NUMBER}.md`:
```markdown
---
id: ${TYPE}-${NUMBER}
type: ${type}
title: ${title}
status: open
priority: ${priority}
created: ${ISO_DATE}
labels: [${labels}]
---
# ${TYPE}-${NUMBER}: ${title}
## Description
${description}
## Acceptance Criteria
- [ ] ${auto_criteria}
## Technical Notes
<!-- Implementation notes -->
## Resolution
<!-- Filled when done -->
```
### 3.6 Update Index
Add to `.devloop/issues/index.md` (create if needed).
### 3.7 Next Actions
Same as GitHub mode but for local issues.
---
## Quick Mode
If `$ARGUMENTS` has 5+ words, enable quick mode:
1. Auto-detect type: "bug", "fix", "broken" → Bug; "add", "new", "feature" → Feature; else → Task
2. Extract title from arguments
**GitHub:** Prompt confirmation only, then create.
**Local:** Create immediately.
---
## Examples
```bash
/devloop:new # Interactive GitHub
/devloop:new Fix login button not responding # Quick mode GitHub
/devloop:new Add dark mode support # Quick mode GitHub
/devloop:new --local Private refactoring notes # Local issue
/devloop:new --local # Interactive local
```
## Migration
- **Default**: GitHub issues (was local)
- **Local**: Use `--local` flag
- **.devloop/issues/**: Still supported for `--local`
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.