chengfeng-report-bug

Drafts, sanitizes, and submits confirmed bug reports as GitHub Issues.

3.0k|383|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/Agentchengfeng/chengfeng-videocut-skills --skill chengfeng-report-bug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chengfeng-report-bug
Source: https://github.com/Agentchengfeng/chengfeng-videocut-skills/tree/main/plugins/chengfeng-videocut/skills/chengfeng-report-bug
Command: npx skills add https://github.com/Agentchengfeng/chengfeng-videocut-skills --skill chengfeng-report-bug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Reporting bugs for the chengfeng-videocut product often leaks private data (API keys, local paths, project IDs) or creates duplicate, unconfirmed Issues. This Skill structures the report, automatically redacts sensitive information, requires explicit user confirmation, and files the Issue to the correct GitHub repository.

Core Features & Use Cases

  • Automatic Sanitization: Redacts tokens, API keys, JWTs, private keys, local usernames, volume names, and localhost URLs from report content before anything is published.
  • Confirmation-Gated Submission: Generates a draft with a time-limited confirmation token (30 minutes, single-use); submission is rejected if the draft changed, expired, or was already used.
  • Duplicate Detection & Preflight Checks: Verifies GitHub CLI authentication, repository access, the bug label, and searches for existing Issues with the same fingerprint before creating a new one.
  • Use Case: A user hits a rendering failure in the video-cutting Studio. The Skill collects minimal reproduction steps, shows a fully redacted draft targeting the correct repository, and only after the user approves creates the GitHub Issue and returns its URL.

Quick Start

Use the chengfeng-report-bug skill to turn the problem I just described into a sanitized draft and, after I confirm it, submit it as a GitHub Issue.

Frequently Asked Questions about chengfeng-report-bug

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

FAQPage Schema
How do I report a bug to GitHub without leaking private data?

This Skill builds a structured bug report, then automatically redacts API keys, tokens, JWTs, private keys, local usernames, volume paths, and localhost URLs before showing you the draft. Nothing is published until you explicitly confirm the exact sanitized content.

How does the bug report confirmation flow work?

The draft command issues a confirmation token and receipt valid for 30 minutes and a single submission. If the draft content changes, the token expires, or it was already used, submission is rejected and a fresh preview is required.

Does it check for duplicate GitHub Issues before submitting?

Yes. Before creating an Issue, the script computes a fingerprint from the component, reproduction steps, and actual result, then searches open Issues for that fingerprint. If a match exists, it returns the existing Issue URL instead of creating a duplicate.

Which GitHub repository does the bug report go to?

Reports target one of two fixed repositories: Agentchengfeng/chengfeng-videocut for Runtime, Studio, CLI, and rendering issues, or Agentchengfeng/chengfeng-videocut-skills for Skill, Marketplace, and installation issues. The target must be set explicitly and cannot be guessed from the current directory.

What happens if GitHub CLI authentication fails during submission?

The script checks gh auth status before submitting. If authentication fails, it returns a github_auth_required error, keeps the sanitized draft, and never claims the report was submitted; only a returned Issue URL counts as success.

When should I not use this bug reporting skill?

Do not use it for feature requests, general troubleshooting, code commits, or any report the user has not explicitly confirmed. It also never installs the Runtime, starts Studio, modifies projects, or uploads media to gather evidence.