dd-file-issue

Route GitHub issues to the correct DataDog repository using gh CLI.

42|4|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/DataDog/datadog-api-claude-plugin --skill dd-file-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dd-file-issue
Source: https://github.com/DataDog/datadog-api-claude-plugin/tree/main/skills/dd-file-issue
Command: npx skills add https://github.com/DataDog/datadog-api-claude-plugin --skill dd-file-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Filing issues can be error-prone when users guess the right repository; this skill routes issues to the correct DataDog repositories (pup vs Claude plugin) to ensure timely triage.

Core Features & Use Cases

  • Repository auto-routing based on issue content to DataDog/pup or DataDog/datadog-api-claude-plugin.
  • Structured issue bodies with sections for Description, Expected Behavior, Actual Behavior, Steps to Reproduce, Environment, and Labels.
  • Workflow guidance with actionable templates and examples for both pup and plugin issues.

Quick Start

Provide a clear issue description and specify the target repository; the skill will generate a ready-to-file GitHub issue in the correct repository.

Frequently Asked Questions about dd-file-issue

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

FAQPage Schema
How do I route GitHub issues to the correct DataDog repository?

Routing GitHub issues to the correct DataDog repository is handled by this skill's decision logic, which analyzes issue content to direct bugs and features to either the pup or Claude plugin repository for accurate triage.

What is the best way to file a structured bug report for pup or the Claude plugin?

Filing a structured bug report is best done using the standardized issue template, which generates sections for Description, Expected Behavior, Actual Behavior, Steps to Reproduce, and Environment to ensure complete triage information.

Can I use the gh CLI workflow to create issues in the pup or plugin repositories?

Yes, you can use the gh CLI workflow to create issues, as this skill provides actionable templates and a command-line process for filing your standardized issue body directly into the target DataDog repository.

Do I need to specify the target repository when filing a feature request?

You do not strictly need to specify the target repository for a feature request, as the skill auto-routes issues based on content, but providing a clear description and target helps ensure accurate routing between pup and the Claude plugin.

Why does my GitHub issue end up in the wrong DataDog repository?

Your GitHub issue may end up in the wrong DataDog repository due to ambiguous content, but this skill solves that by applying decision logic to route issues correctly between the pup and datadog-api-claude-plugin repositories based on the issue details.