DevTeam Issue New Command banner
michael-harris michael-harris

DevTeam Issue New Command

Development community intermediate

Description

**Command:** `/devteam:issue-new "<description>"` Create a new GitHub issue with proper formatting and labels.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

Repository README

This is the README for michael-harris/devteam, shared by 20 entries in this directory. It describes the repository, not this entry specifically.

DevTeam Issue New Command

**Command:** `/devteam:issue-new ""`

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

Step 5: Report to User

╔══════════════════════════════════════════╗
║  📝 ISSUE CREATED                        ║
╚══════════════════════════════════════════╝

Issue #127: Login button not working on mobile

Labels: bug, area: frontend, priority: medium
URL: https://github.com/user/repo/issues/127

To fix this issue automatically:
  /devteam:issue 127

Examples

Bug Report

/devteam:issue-new "Users get 500 error when uploading large files"

Creates:

## Description

Users encounter a 500 Internal Server Error when attempting to upload large files.

## Steps to Reproduce

1. Navigate to the upload page
2. Select a file larger than [threshold]
3. Click upload
4. Observe 500 error

## Expected Behavior

File should upload successfully or show a helpful error message if too large.

## Actual Behavior

Server returns 500 error with no helpf