From pup
Files GitHub issues to correct DataDog repo: pup CLI for tool/API bugs or Claude plugin for agent/docs issues. Determines repo via decision logic and checks duplicates.
npx claudepluginhub datadog-labs/pup --plugin pupThis skill uses the workspace's default tool permissions.
This skill helps you file GitHub issues to the correct repository - either the `pup` CLI tool or the Claude plugin, depending on the nature of the issue.
Creates GitHub issues in WaterplanAI/agentic-config repo for bugs and feature requests using GitHub CLI. Handles templates, explicit args, or extracts from conversation context. Invoke via /ac-issue.
Gathers structured bug details, reproduction steps, errors, and environment info for spec-first plugin issues, then formats a GitHub issue. Use for agent, command, skill, or MCP problems.
Creates GitHub or GitLab issues with code references, media attachments, labels, and session context. Auto-detects repo from git remote for bug reports or feature requests.
Share bugs, ideas, or general feedback.
This skill helps you file GitHub issues to the correct repository - either the pup CLI tool or the Claude plugin, depending on the nature of the issue.
Invocation: /dd-file-issue
DataDog/pup RepositoryIssues related to the pup CLI tool itself:
Example Issues for pup:
DataDog/datadog-api-claude-plugin RepositoryIssues related to the Claude plugin and its agents:
Example Issues for plugin:
If unclear which repository the issue belongs to:
Gather Information
Determine Repository
Check for Existing Issues
Collect Issue Details
Select Issue Type
Create Issue
gh issue create to file the issueAsk clarifying questions:
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? (→ pup repo)
- An agent giving bad guidance? (→ plugin repo)
- Documentation being wrong/unclear? (→ plugin repo)
For pup repository:
gh issue list \
--repo DataDog/pup \
--search "your search terms" \
--limit 10
For plugin repository:
gh issue list \
--repo DataDog/datadog-api-claude-plugin \
--search "your search terms" \
--limit 10
For pup repository:
gh issue create \
--repo DataDog/pup \
--title "Clear, concise title" \
--body "Detailed description" \
--label "bug" # or "enhancement", "documentation"
For plugin repository:
gh issue create \
--repo DataDog/datadog-api-claude-plugin \
--title "Clear, concise title" \
--body "Detailed description" \
--label "bug" # or "enhancement", "documentation", "agent"
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 documentationquestion - Further information is requestedFor plugin 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 plugin issue (documentation)
Steps:
gh issue list --repo DataDog/datadog-api-claude-plugin --search "TypeScript"gh issue create \
--repo DataDog/datadog-api-claude-plugin \
--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 plugin enhancement (new agent)
gh issue create \
--repo DataDog/datadog-api-claude-plugin \
--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/[repo-name]
**Issue**: #123
**URL**: https://github.com/DataDog/[repo-name]/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