devteam-issue-new
npx machina-cli add skill michael-harris/devteam/devteam-issue-new --openclawRepository: !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 automaticallygh 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
Source
git clone https://github.com/michael-harris/devteam/blob/main/skills/devteam-issue-new/SKILL.mdView on GitHub Overview
Automates creating GitHub issues with proper formatting, labels, and codebase context. It analyzes the description to classify issue type and area, gathers related files and recent commits, then formats a structured body before creating the issue with gh issue create.
How This Skill Works
It parses the input to infer issue type and affected area using keyword rules, then searches the repository for related code and recent commits to gather context. It builds a structured issue body with sections like Description, Steps to Reproduce, Expected vs Actual Behavior, and Related Code. Finally it creates the issue via gh issue create using the chosen title, body, and labels.
When to Use It
- When a bug or unexpected behavior is reported, e.g., login button not working on mobile
- When a feature request or enhancement is needed, e.g., add dark mode support
- When a security issue is detected, e.g., SQL injection in user search
- When performance problems are observed, e.g., slow page loads or timeouts
- When documentation or onboarding gaps are found, e.g., missing usage guide
Quick Start
- Step 1: Run the command with a description, e.g., /devteam:issue-new "Login button not working on mobile"
- Step 2: Optionally attach labels, e.g., --label bug --label frontend
- Step 3: The tool reports the created issue number and link; view with gh issue view <number>
Best Practices
- Keep the description clear and include exact keywords to trigger correct labels
- Use --label, --assignee, --project, and --milestone to attach context
- Search for related code and any existing issues to avoid duplicates
- Provide Steps to Reproduce for bugs and a Proposed Solution for enhancements
- Review and adjust labels after creation to ensure accuracy
Example Use Cases
- /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
- /devteam:issue-new "App crashes on startup"
- /devteam:issue-new "Update API docs for new endpoints" --label documentation
