| name | dd-file-issue |
| description | File GitHub issues to the right repository (pup CLI or plugin) |
| trigger | Use this skill when the user wants to: - Report a bug - Request a feature - File an issue - Submit a problem report - Report something not working - Suggest an improvement |
| examples | ["This isn't working, file an issue","Can you create a bug report for this?","I want to request a new feature","Report this error to the team"] |
This skill helps you file GitHub issues to the correct repository. All issues — whether related to the pup CLI, skills, agents, or documentation — are tracked in DataDog/pup.
Invocation: /dd-file-issue
DataDog/pup RepositoryAll issues are filed here, including:
Example Issues:
Gather Information
Determine Repository
DataDog/pupCheck for Existing Issues
Collect Issue Details
Select Issue Type
Create Issue
gh issue create to file the issueAll issues are filed against DataDog/pup. Ask clarifying questions to gather detail:
To file this issue correctly, I need to understand:
1. What were you trying to do?
2. What went wrong?
3. Was this a problem with:
- A pup command not working?
- An agent giving bad guidance?
- Documentation being wrong/unclear?
gh issue list \
--repo DataDog/pup \
--search "your search terms" \
--limit 10
gh issue create \
--repo DataDog/pup \
--title "Clear, concise title" \
--body "Detailed description" \
--label "bug" # or "enhancement", "documentation"
Use this template for comprehensive issue reports:
## Description
[Clear description of the issue]
## Expected Behavior
[What should happen]
## Actual Behavior
[What actually happened]
## Steps to Reproduce
1. [First step]
2. [Second step]
3. [...]
## Environment
- OS: [e.g., macOS 14.1, Ubuntu 22.04]
- Pup version: [run `pup --version`]
- Plugin version: [from plugin.json]
- Claude Code version: [if relevant]
## Error Messages / Logs
[Paste any error messages or relevant logs]
## Additional Context
[Any other relevant information]
## Suggested Fix (Optional)
[If you have ideas for how to fix this]
✅ Good:
❌ Bad:
For pup repository:
bug - Something isn't workingenhancement - New feature or requestdocumentation - Improvements or additions to documentationagent - Related to specific agent behaviorskill - Related to skillsquestion - Further information is requestedUser: "The pup logs search command times out after 30 seconds"
Analysis: This is a pup CLI issue (command behavior)
Steps:
gh issue list --repo DataDog/pup --search "timeout"gh issue create \
--repo DataDog/pup \
--title "pup logs search: command times out after 30 seconds" \
--body "## Description
The \`pup logs search\` command times out after 30 seconds when searching large time ranges.
## Expected Behavior
Should either complete the query or allow configurable timeout.
## Actual Behavior
Command fails with timeout error after 30 seconds.
## Steps to Reproduce
1. Run: \`pup logs search --query='*' --from='7d' --to='now'\`
2. Wait 30 seconds
3. See timeout error
## Environment
- OS: macOS 14.1
- Pup version: 1.2.3
- DD_SITE: datadoghq.com
## Error Message
\`\`\`
Error: request timeout after 30000ms
\`\`\`
" \
--label "bug"
User: "The logs agent documentation shows TypeScript examples instead of pup commands"
Analysis: This is a documentation issue
Steps:
gh issue list --repo DataDog/pup --search "TypeScript"gh issue create \
--repo DataDog/pup \
--title "logs agent: outdated TypeScript examples in documentation" \
--body "## Description
The logs agent documentation still shows TypeScript/Node.js examples instead of pup CLI commands.
## Location
\`agents/logs.md\` lines 150-200
## Expected
Should show pup CLI command examples like:
\`\`\`bash
pup logs search --query='*' --from='1h'
\`\`\`
## Actual
Shows TypeScript code with imports and API clients
## Impact
Confusing for users who expect pup CLI commands
## Files Affected
- agents/logs.md
- Possibly other agent files (need audit)
" \
--label "documentation" \
--label "agent"
User: "Can we add an agent for Datadog SLO reporting?"
Analysis: This is a pup enhancement (new agent)
gh issue create \
--repo DataDog/pup \
--title "enhancement: add SLO reporting agent" \
--body "## Feature Request
### Description
Add a new agent focused on SLO reporting and analysis, separate from the SLO management agent.
### Use Cases
- Generate SLO reports for stakeholders
- Analyze SLO trends over time
- Compare SLOs across services
### Proposed Agent Capabilities
- Query SLO history
- Generate formatted reports
- Calculate SLO burn rates
- Identify at-risk SLOs
### Related Agents
- Current \`slos.md\` focuses on SLO CRUD operations
- New agent would focus on analytics and reporting
### Priority
Medium - would improve SLO workflow
" \
--label "enhancement" \
--label "agent"
If issue creation fails:
gh auth statusAfter successfully filing an issue:
✅ Issue created successfully!
**Repository**: DataDog/pup
**Issue**: #123
**URL**: https://github.com/DataDog/pup/issues/123
**Title**: [issue title]
The team will review your issue and respond soon. You can:
- Track the issue at the URL above
- Add more details by commenting on the issue
- Subscribe to notifications for updates
Datadog API CLI with 49 command groups, 300+ subcommands. Skills and domain agents for monitoring, logs, APM, security, and infrastructure.
Load when investigating a specific flaky test. Gets history, failure pattern, and category, then recommends fix, quarantine, or escalate.
Load when investigating a failing PR CI pipeline or checking PR health. Attributes each CI failure as flaky, infra, or regression, proposes a targeted action, and reports code coverage.
Log management - search, pipelines, archives, and cost control.
Monitor management - create, update, mute, and alerting best practices.
Live Debugger - inspect runtime argument/variable values in production by placing log probes on methods. Use when asked what values a function receives, what parameters look like at runtime, or to capture live data from running services without redeploying.