dd-file-issue

Creates GitHub issues in the DataDog/pup repository using the gh CLI.

5|2|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/lauhon/pi --skill dd-file-issue-lauhon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dd-file-issue
Source: https://github.com/lauhon/pi/tree/main/skills/dd-file-issue
Command: npx skills add https://github.com/lauhon/pi --skill dd-file-issue-lauhon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Filing well-structured bug reports and feature requests is tedious, and users often file issues in the wrong repository or omit critical details like environment info and reproduction steps. This Skill standardizes issue creation for the pup CLI ecosystem so every report lands in DataDog/pup with the right labels and complete context. ## Core Features & Use Cases - Guided Issue Intake: Walks through gathering what went wrong, expected behavior, reproduction steps, and environment details before filing. - Duplicate Detection: Searches existing issues in DataDog/pup with gh issue list to avoid filing duplicates. - Structured Issue Creation: Uses gh issue create with a consistent body template and appropriate labels (bug, enhancement, documentation, agent, skill, question). - Use Case: A user reports that pup logs search times out after 30 seconds. The Skill searches for existing timeout issues, then files a labeled bug report including OS, pup version, the exact command, and the error message. ## Quick Start Ask the assistant to file a bug report describing the pup command that failed, the error message you saw, and your environment details.

Frequently Asked Questions about dd-file-issue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I file a GitHub issue for a pup CLI bug?

Describe what you were trying to do, what went wrong, and any error messages. The Skill searches DataDog/pup for duplicates, then runs gh issue create with a structured body covering reproduction steps, environment, and logs.

Which repository should pup CLI issues be filed against?

All issues go to DataDog/pup, regardless of whether they concern the CLI, agents, skills, or documentation. There is no separate repository decision to make.

How do I avoid filing duplicate GitHub issues?

Search the target repository first with gh issue list --repo DataDog/pup --search followed by relevant keywords. If a matching issue exists, comment on it instead of creating a new one.

What labels should I use when creating a GitHub issue?

Use bug for broken behavior, enhancement for feature requests, documentation for doc improvements, agent or skill for those specific areas, and question when requesting information. Multiple labels can be combined.

What should I do if gh issue create fails?

Check network connectivity, verify authentication with gh auth status, and confirm repository permissions. If creation still fails, save the issue title and body so the report can be filed manually.