issue-creation

Create and triage GitHub issues with repository-specific templates and labels.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/LuisAlbertoMK/gentleman-agent-gh --skill issue-creation-luisalbertomk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-creation
Source: https://github.com/LuisAlbertoMK/gentleman-agent-gh/tree/main/internal/assets/skills/issue-creation
Command: npx skills add https://github.com/LuisAlbertoMK/gentleman-agent-gh --skill issue-creation-luisalbertomk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh.

What problem does it solve?

This skill eliminates the friction of manual issue creation by automating repository discovery, template adherence, and privacy-conscious data sanitization.

Core Features & Use Cases

  • Policy-Aware Creation: Automatically detects repository-specific contribution guidelines, templates, and label requirements before drafting.
  • Privacy Sanitization: Mandatorily replaces environment-specific identifiers like usernames, paths, and tokens with safe placeholders to protect user data.
  • Use Case: When reporting a bug, the skill ensures you follow the project's specific issue template, apply the correct labels, and redact your local file paths before the issue is ever published.

Quick Start

Use the issue-creation skill to draft a new bug report for the current repository based on the provided error logs.

Frequently Asked Questions about issue-creation

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

FAQPage Schema
How do I automate GitHub issue creation while enforcing repository templates?

Automating GitHub issue creation enforces repository-specific contribution guidelines, templates, and label requirements before drafting. This ensures standardized bug reporting and feature requests by validating policies during the triage process.

Does the issue triage process sanitize local file paths and tokens for privacy?

Yes, the issue triage process mandatorily sanitizes local file paths, usernames, and tokens for privacy. It replaces environment-specific identifiers with safe placeholders before the issue is ever published to protect user data.

Do I need the GitHub CLI to draft and publish standardized bug reports?

Yes, you need the GitHub CLI (gh) to draft and publish standardized bug reports. The CLI performs authenticated repository discovery, label validation, and secure issue publication required for the automation workflow.

What is the best way to manage feature requests and apply correct labels automatically?

The best way to manage feature requests and apply correct labels automatically is through policy-aware creation. This detects repository-specific label requirements and contribution guidelines before drafting the issue.

Can I use this automated issue drafting for software development workflows outside bug reporting?

Yes, you can use automated issue drafting for software development workflows beyond bug reporting, including feature requests and general issue management. It applies standardized templates across various contribution types.

Why does automated issue creation replace usernames and environment paths with placeholders?

Automated issue creation replaces usernames and environment paths with placeholders to enforce privacy-conscious data sanitization. This protects sensitive user data by preventing environment-specific identifiers from being published.