Receber por email
← Voltar para o catálogo

devteam-issue-new

Create a new GitHub issue with proper formatting, labels, and context from the codebase.

16estrelas
Atualizado há 8 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add michael-harris/devteam

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/devteam-issue-new/svg)](https://www.skillteca.com.br/skills/devteam-issue-new)

Skills relacionadas

Ver todas de Desenvolvimento →

Alerta por categoria

Receba novas skills de Desenvolvimento toda segunda

1 email curto, só com as skills novas de Desenvolvimento. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Repository: !gh repo view --json nameWithOwner -q .nameWithOwner 2>/dev/null || echo "No GitHub repo detected" Recent issues: !gh issue list --limit 5 --json number,title,labels -q '.[] | "#\(.number) \(.title) [\(.labels | map(.name) | join(", "))]"' 2>/dev/null || echo "No issues found"

DevTeam Issue New Command

Command: /devteam:issue-new "<description>"

Create a new GitHub issue with proper formatting and labels.

Usage

/devteam:issue-new "Login button not working on mobile"
/devteam:issue-new "Add dark mode support" --label enhancement
/devteam:issue-new "Critical: SQL injection in user search" --label security

Your Process

Step 1: Analyze Description

Parse the issue description from $ARGUMENTS to determine:

Issue type (from keywords):

  • "not working", "broken", "error" -> bug
  • "add", "implement", "feature" -> enhancement
  • "slow", "timeout", "performance" -> performance
  • "security", "vulnerability", "injection" -> security, priority: high
  • "critical", "urgent" -> add priority: high

Affected area (if detectable):

  • "login", "auth", "user" -> area: authentication
  • "API", "endpoint", "request" -> area: backend
  • "UI", "button", "page", "mobile" -> area: frontend
  • "database", "query", "data" -> area: database

Step 2: Gather Additional Context

Search codebase for related files and check for similar existing issues:

# Search for related code
grep -r "keyword" --include="*.py" --include="*.ts" -l

# Check for similar issues
gh issue list --search "description keywords"

# Check recent commits in related area
git log --oneline -10 -- related/paths/

Step 3: Format Issue

Create well-structured issue body with:

  • Description
  • Steps to Reproduce (for bugs)
  • Expected vs Actual Behavior (for bugs)
  • Proposed Solution (for enhancements)
  • Related Code (files found in Step 2)

Step 4: Create Issue

gh issue create \
  --title "${title}" \
  --body "${body}" \
  --label "${labels}"

Step 5: Report to User

Show created issue number, URL, labels, and suggest next steps:

  • /devteam:issue <number> to fix automatically
  • gh issue view <number> to view on GitHub

Labels Applied Automatically

| Detected Keywords | Labels Applied | |------------------|----------------| | bug, error, broken, not working | bug | | add, feature, implement | enhancement | | slow, performance, timeout | performance | | security, vulnerability, injection | security, priority: high | | critical, urgent | priority: high | | docs, documentation | documentation |

Options

  • --label <label>: Add specific label
  • --assignee <user>: Assign to user
  • --project <name>: Add to project
  • --milestone <name>: Add to milestone

See Also

  • /devteam:issue - Fix an existing issue automatically
  • /devteam:bug - Diagnose and fix bugs with Bug Council
Compartilhar X LinkedIn