Turn Bug Reports into Clean GitHub Issues with chengfeng-report-bug

Where this fits

A developer is building an AI agent that helps video editors using chengfeng-videocut. When a user says "this cut has a rendering glitch, tell the developers," the agent needs to convert that vague feedback into a structured, de-identified GitHub issue—without leaking sensitive project data or triggering unintended actions. This skill handles exactly that: it collects minimal facts, sanitizes them, and creates a bug report only after explicit user confirmation.

Why agents benefit

• Structured triage: The skill distinguishes real bugs from feature requests or usage questions, preventing false issue creation.
• Privacy-first sanitization: It strips sensitive details from logs and diagnostics, showing only safe fields like state, kind, and version before any external write.
• Guarded execution: It never auto-submits without user approval—agents must preview the repo, title, and body first, avoiding accidental public posts.
• Duplicate prevention: Before creating an issue, it checks existing GitHub issues, reducing noise for maintainers.
• Read-only diagnostics: Agents can run a lightweight runtime check (if present) without touching projects or launching apps, keeping the workflow safe.

Practical scenarios

User reports a timeline glitch

The agent asks one clarifying question, runs the read-only probe, and presents a draft issue with the exact component (e.g., product), a minimal reproduction description, and sanitized environment info. The user approves, and the issue lands in the correct repository.

User wants to continue a previous draft

If a draft was generated but not submitted, the skill lets the agent resume from that preview, re-verify the details, and ask for confirmation again—no need to start from scratch.

User asks for a feature suggestion

The agent recognizes it's not a bug and instead asks if they'd like to post a feature request elsewhere, keeping the bug tracker clean and focused.

Add it to your agent workflow

Install the skill via npx:

npx skills add Agentchengfeng/chengfeng-videocut-skills --skill chengfeng-report-bug

Then invoke it when the user expresses a bug report intent. For example, your agent might say: "I'll prepare a sanitized issue draft for that rendering problem. Please review before I submit." The skill handles the rest—from validation to GitHub API calls.

Compare before adopting

Before integrating, evaluate:

• Quality signals: Check the repository's issue hygiene, commit history, and whether the skill is actively maintained (stars, recent releases).
• Alternatives: Compare with generic GitHub issue tools—do they offer the same level of context-aware sanitization and duplicate checking?
• Workflow fit: Does your agent already have a bug-reporting pipeline? This skill is specific to chengfeng-videocut, so it's only useful if your users work with that tool.

Also consider the skill's safety model: it requires explicit user confirmation, which might add friction but prevents costly mistakes.

Why it is worth tracking

With 2,962 stars and a clear, focused scope, this skill demonstrates strong community trust. Its design—minimal read-only diagnostics, strict confirmation gates, and duplicate checks—sets a good pattern for any agent that needs to interact with external APIs responsibly. Track it if you build agents for video editing workflows or want a reference implementation for safe issue submission. See more details at OpenAgentSkill to evaluate its fit for your stack.