aget-file-issue

File GitHub issues with L520 governance compliance and content sanitization.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of filing issues to GitHub repositories, ensuring compliance with L520 governance standards by handling routing and content sanitization.

Core Features & Use Cases

  • Automated Routing: Intelligently determines the correct repository for filing issues based on agent type (private vs. public).
  • Content Sanitization: Redacts sensitive information before filing issues to public repositories, preventing data leaks.
  • Template Selection: Supports filing for enhancements, bugs, and new features using predefined templates.
  • Use Case: A private agent needs to report a bug found during internal testing. This Skill will automatically file the bug report to the correct internal repository, sanitizing any sensitive details before filing.

Quick Start

Use the aget-file-issue skill to file a bug report with the title "Fix login loop".

Frequently Asked Questions about aget-file-issue

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

FAQPage Schema
How do I automate filing GitHub issues while ensuring governance compliance?

Automating GitHub issue filing with governance compliance involves routing issues to the correct repository based on agent type and sanitizing content to prevent data leaks. This ensures adherence to L520 standards when filing bugs, enhancements, or feature requests.

How does content sanitization work when filing issues to public repositories?

Content sanitization for public repositories redacts sensitive information, such as private agent names and internal repo references, before filing issues. This prevents data leaks and maintains L520 governance compliance for public GitHub issue reports.

Can I use automated routing to file bug reports for private agents?

Yes, automated routing determines the correct repository for filing bug reports based on whether the agent is private or public. Private agent bug reports are routed to internal repositories, while public agent reports are sanitized and routed to public repositories.

What types of GitHub issue templates are supported for governance-compliant filing?

Governance-compliant GitHub issue filing supports predefined templates for enhancement, bug, and feature request types. These templates ensure standardized reporting while automatically applying content sanitization and destination routing for L520 compliance.

Are there limitations on what information can be included in public GitHub issues?

Yes, L520 governance compliance constraints prohibit including private agent names or internal repository references in public GitHub issues. Content sanitization automatically redacts these sensitive details before filing to prevent governance violations and data leaks.