Report a Bug
This is the support entry point for chengfeng-videocut, not a third editing workflow. By default, only a public Issue draft is generated; external submissions must go through sanitization preview and user confirmation.
Problem description
|
v
Minimal read-only diagnostics -> Sanitize -> Show repo / title / body
|
User explicit confirmation
|
v
Authentication + label check + duplicate check
|
v
Create GitHub Issue
1. Confirm This Is a Reproducible Bug
First, distinguish:
- Bug: Actual behavior deviates from existing contract, UI, version capability, or deterministic result.
- Feature suggestion: The product never promised this capability; do not disguise as a bug.
- Usage question: Answer or diagnose first, do not auto-submit.
Collect only the minimum facts needed for reproduction. Do not install Runtime, start Studio, modify projects, re-edit videos, or upload media to "gather evidence." If Runtime exists, you may run node scripts/ensure-runtime.cjs --json from the plugin root for read-only detection, keeping only state / kind / version / healthy / error.code; do not include the full doctor output. kind=desktop-managed only indicates the installation source is the desktop App, it does not authorize this Skill to launch the App, service, or reinstall. If it doesn't exist, write "not detected."
2. Select the Fixed Repository
The workspace root directory is not necessarily a Git repository; do not guess the remote from the current directory:
| Issue Component | target | GitHub Repository |
|---|---|---|
| Runtime, Studio, UI, CLI, API, Timeline, Rendering | product | Agentchengfeng/chengfeng-videocut |
| Skill, Marketplace, Installation Orchestration, MCP App, Workflow Documentation | skills | Agentchengfeng/chengfeng-videocut-skills |
For cross-component issues, prioritize reporting to the repository that first violated the contract, and mention the other component in the body; if uncertain, ask the user first.
3. Generate Structured Input
Write the candidate as a JSON to the current task's temporary directory with umask 077, not to product specification files; delete the temporary JSON and Markdown after submission:
{
"schemaVersion": 1,
"target": "product",
"component": "Studio",
"title": "Runtime 0.1.1 cannot open HyperFrames top-level video trim view",
"summary": "One-sentence impact description",
"steps": ["Step one", "Step two"],
"expected": "Expected behavior",
"actual": "Actual behavior",
"environment": {
"Runtime": "0.1.1",
"OS": "macOS"
},
"evidence": ["Only minimal, public diagnostics"],
"acceptance": ["Verifiable fix criteria"]
}
Prohibited content:
- API Key, Token, Cookie,
.env; - Videos, audio, screenshots, full logs, or transcript bodies;
- Client names, original video names, real
projectId, user absolute paths; - Private repository content without user permission.
4. First Generate and Display the Sanitized Draft
Locate the script from the current SKILL.md:
First, locate the plugin root following the "Readiness Check" first step of Check for Updates
(from the actual source file path of this Skill, two levels up; do not run codex plugin list or search other
caches; substitute <plugin-root> below with that literal path). This Skill only uses it for script location,
does not install Runtime or start services:
node "<plugin-root>/skills/chengfeng-report-bug/scripts/report-bug.cjs" draft --input "<report JSON file>" --output "<draft output file>" --json
The target must be explicitly product or skills; missing or misspelled values should stop, not silently redirect to another repository. The script cleans common secrets, local usernames, volume names, path fragments, and localhost query parameters; automatic sanitization cannot identify arbitrary client names, so manual review is still required. Display to the user:
repo
label=bug
title
Full sanitized body
Also save the returned confirmationReceipt, and show the user the confirmationToken and expiration time. Stop if the user does not explicitly confirm this public content; detecting an error does not equal consent to submit. The token is bound only to the draft content and does not itself prove user consent; the Agent must still wait for an explicit reply. Confirmation is valid only for the immediately following submission in the current task, expires in 30 minutes, and cannot be reused across tasks or sessions.
5. Submit After Confirmation
Submit only the draft just presented with unchanged content:
node "<plugin-root>/skills/chengfeng-report-bug/scripts/report-bug.cjs" submit --input "<report JSON file>" --target "<target repository>" --confirmed --confirm-token "<confirmation token>" --receipt "<confirmation receipt file>" --json
Fixed rules:
- Before submission, the script checks
gh auth status, the target repository's Issues, and thebuglabel; keep the draft on failure. - If a fingerprint matching the same component, reproduction steps, and actual results already exists, return the original Issue URL; do not impersonate a duplicate with a generic title.
- If the body changes after confirmation, return
confirmation_mismatch; must re-preview. - If the confirmation credential has expired or been used, return
confirmation_expired / confirmation_replayed; must re-preview. - If the creation result has no explicit Issue URL, do not auto-retry; it may have already been created.
- Only when you have the GitHub Issue URL can you say "the bug has been reported."
Failure Handling
github_auth_required: Indicates the draft is complete but not submitted; disallow claiming success.github_issue_create_failed: Keep the draft and manual entry point; do not loop retry.confirmation_required/confirmation_mismatch: Re-display the exact public content.- No permissions or visibility for the target repository: Do not revert to another repository; let the user decide whether to report to the public Skills repository instead.