devteam-issue-new

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 to determine:

Issue type:

• Keywords like "not working", "broken", "error" → bug
• Keywords like "add", "implement", "feature" → enhancement
• Keywords like "slow", "timeout", "performance" → performance
• Keywords like "security", "vulnerability", "injection" → security
• Keywords like "critical", "urgent", "ASAP" → 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

If needed, investigate the codebase to add context:

// Search for related code
const relatedFiles = await grep(description.keywords)

// Check for similar issues
const similarIssues = await gh('issue list --search "${description}"')

// Check recent commits in related area
const recentChanges = await git('log --oneline -10 -- ${relatedPaths}')

Step 3: Format Issue

Create well-structured issue body:

## Description

[Clear description of the issue]

## Steps to Reproduce

1. [Step 1]
2. [Step 2]
3. [Step 3]

## Expected Behavior

[What should happen]

## Actual Behavior

[What actually happens]

## Environment

- OS: [if relevant]
- Browser: [if relevant]
- Version: [if relevant]

## Additional Context

[Any additional information, screenshots, logs]

## Related Code

[Files that might be related]

---
*Created via DevTeam*

Step 4: Create Issue

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