file-issue

File GitHub issues with formatted templates and labels via gh.

Updated Oct 11, 2025
One-click install
npx skills add https://github.com/tnez/docent --skill file-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: file-issue
Source: https://github.com/tnez/docent/tree/main/skills/github/file-issue
Command: npx skills add https://github.com/tnez/docent --skill file-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh cli, git cli.

What problem does it solve?

Manually creating GitHub issues can be inconsistent, often missing critical information or proper labels. This Skill automates the process of filing bug reports, feature requests, questions, or documentation issues, ensuring they are well-formatted, complete, and correctly categorized, saving you time and improving communication.

Core Features & Use Cases

  • Type-Specific Templates: Generates structured issue bodies for bugs, features, questions, and documentation issues.
  • Automated Labeling: Applies appropriate labels (e.g., bug, enhancement, documentation) based on issue type.
  • Project Configuration: Integrates with .docent/config.yaml to target the correct repository and apply default labels.
  • Use Case: You discover a bug and want to report it. Instead of manually filling out a form, use this Skill to tell your agent "File a bug: Bootstrap fails on Windows with permission error" and it will automatically create a well-structured issue with all necessary details and labels.

Quick Start

File a bug report: "Bootstrap fails on Windows with permission error"

Frequently Asked Questions about file-issue

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

FAQPage Schema
How do I automate filing GitHub issues with consistent formatting?

Automate filing GitHub issues by configuring this Skill with your repository in .docent/config.yaml. It generates properly formatted issue bodies, applies relevant labels automatically, and creates issues via gh CLI—eliminating manual form-filling and ensuring consistency across bug reports, feature requests, and documentation issues.

Can I file different types of GitHub issues with templates?

Yes. This Skill generates type-specific templates for bugs, features, questions, and documentation issues. Each template captures the relevant details for that issue type, applies appropriate labels like bug or enhancement, and formats the issue body automatically based on the type you specify.

What do I need to set up before filing issues with this Skill?

You need gh CLI installed and authenticated to your GitHub account, a repository configured in .docent/config.yaml, and network access to GitHub. The Skill handles the rest—formatting and creating properly labeled issues directly in your project repository.

How does this Skill organize issues with labels?

This Skill automatically applies labels based on issue type: bug, enhancement, documentation, or question. Labels are determined by the issue type you provide and any default labels defined in your .docent/config.yaml project configuration, keeping your repository organized without manual categorization.

Can I use this Skill with multiple repositories?

Yes. This Skill integrates with .docent/config.yaml, which supports multiple project configurations. Specify which project you're targeting when filing an issue, and the Skill will apply the correct repository, defaults, and labels for that project.