skills.rest
gmelli
gmelliCOMMUNITY
Explore all skills by this author →
Website𝕏@gmelliGitHub

aget-file-issue

Route governance-compliant issues to the correct repository with content sanitization.

1|Updated Oct 4, 2025
Search Tags:#automation#templates#routing#github#sanitization#governance#issue
One-click install
npx skills add https://github.com/gmelli/public-OpenAI-DeepResearch-aget --skill aget-file-issue-gmelli
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aget-file-issue
Source: https://github.com/gmelli/public-OpenAI-DeepResearch-aget/tree/main/.claude/skills/aget-file-issue
Command: npx skills add https://github.com/gmelli/public-OpenAI-DeepResearch-aget --skill aget-file-issue-gmelli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

File issues to the correct repositories with L520 governance compliance, routing, and content sanitization to prevent leakage of sensitive information.

Core Features & Use Cases

  • Automatic destination routing based on agent type (private vs public)
  • Content sanitization for public-facing issues with template selection (enhancement, bug, feature)
  • Validation of required fields (title, type, body) before filing
  • Transparent reporting of destination and sanitization status

Quick Start

Run /aget-file-issue <type> <title> to file a governance-compliant issue to the appropriate repository.

Frequently Asked Questions about aget-file-issue

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

FAQPage Schema
How do I automatically route and file issues to the correct GitHub repository?▼

Automatically route and file issues by using a governance-compliant automation tool that determines the destination repository based on agent type, validates required fields, and submits the issue via the GitHub CLI.

How do I sanitize sensitive content before filing public-facing issues on GitHub?▼

Sanitize sensitive content before filing public-facing issues by applying an automated content sanitization process that scrubs private information and selects the appropriate issue template before submission.

Do I need the gh CLI installed and authenticated to file governance-compliant issues?▼

Yes, you need the gh CLI installed and authenticated to file governance-compliant issues, because the automation requires CLI access to validate title, type, and body before routing to the destination repository.

What is the best way to ensure L520 governance compliance when filing GitHub issues?▼

The best way to ensure L520 governance compliance when filing GitHub issues is to use an automation tool that validates required fields, sanitizes content, and transparently reports the destination and sanitization status.

Can I select different templates like enhancement or bug when filing issues through automation?▼

Yes, you can select different templates like enhancement, bug, or feature when filing issues through automation, which applies the correct template based on the issue type for public-facing repositories.

Why does my automated issue filing fail when the title, type, or body is missing?▼

Automated issue filing fails when the title, type, or body is missing because the governance validation process requires these fields to be present before it can sanitize content and route the issue to the correct repository.

Related Skills

Explore More Legal & Compliance Skills→
tneztnez

file-issue

File GitHub issues with formatted templates and labels via gh.

Community
Intermediate
aget-frameworkaget-framework
11

aget-file-issue

File GitHub issues with L520 governance compliance and content sanitization.

Official
Advanced
ductrung-nguyenductrung-nguyen

fetch-github-issue

Fetch GitHub issue details by ID and save them as structured markdown files.

Community
Intermediate
posit-devposit-dev
4.2k

positron-issue-creator

Drafts complete GitHub issue drafts for the Positron repository with duplicate checking.

Official
Basic