Report a Bug
This is the support entry for chengfeng-videocut, not a third clipping workflow. By default, it only generates a draft public Issue; external submission must go through sanitization preview and user confirmation.
Problem Description
|
v
Minimal Read-Only Diagnostics -> Anonymization -> Show Repository / Title / Body
|
User Explicit Confirmation
|
v
Authentication + Label Check + Duplicate Detection
|
v
Create GitHub Issue
1. Confirm This Is a Reproducible Bug
First, distinguish:
- Bug: Actual behavior deviates from existing contract, interface, version capabilities, or deterministic results.
- Feature Request: The product never promised this capability; do not disguise as a Bug.
- Usage Question: Answer or diagnose first, do not auto-report.
Collect only the minimal facts needed to reproduce. Do not install Runtime, start Studio, modify projects, re-edit clips, or upload media to "gather evidence." If Runtime exists, you may execute node scripts/ensure-runtime.cjs --json from the plugin root for read-only probing, keeping only state / kind / version / healthy / error.code; do not attach full doctor output. kind=desktop-managed only indicates the installation source is the desktop App, it does not authorize this Skill to start the App, service, or reinstall. If absent, write "not detected."
2. Select the Fixed Repository
The workspace root is not necessarily a Git repository; do not guess the remote from the current directory:
| Component Area | 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, prefer the repository that first violates the contract, and note the other component in the body; if unsure, ask the user first.
3. Generate Structured Input
Write the candidate to a JSON file in the current task's temporary directory with umask 077. Do not write 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 clipping view",
"summary": "One-sentence description of impact",
"steps": ["Step one", "Step two"],
"expected": "Expected behavior",
"actual": "Actual behavior",
"environment": {
"Runtime": "0.1.1",
"OS": "macOS"
},
"evidence": ["Only minimal, publishable diagnostics"],
"acceptance": ["Verifiable fix criteria"]
}
Forbidden:
- API Keys, Tokens, Cookies,
.env; - Videos, audio, screenshots, full logs, or transcribed text;
- Customer names, original video names, real
projectIds, user absolute paths; - Private repository content without user permission.
4. Generate and Show Sanitized Draft First
Locate the script from the current SKILL.md:
First, locate the plugin root per the "Readiness Check" step 1 of Check for Updates (go up two levels from this Skill's actual source file path; do not run codex plugin list or search other caches; substitute <plugin_root> with that literal path). This Skill only uses it to locate scripts, not to 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
target must be explicitly product or skills; missing or misspelled values should stop, do not silently redirect to another repository. The script will clean common secrets, local usernames, volume names, path remnants, and localhost query parameters; automatic anonymization cannot recognize arbitrary customer names, so manual review is still required. Show the user:
repo
label=bug
title
full sanitized body
Save the returned confirmationReceipt, and show the user the confirmationToken and expiration time. Stop if the user has not explicitly confirmed this public content; merely detecting an error does not equal consent to submit. The token is bound only to the draft content and does not itself prove user agreement; the Agent must still wait for an explicit response. Confirmation is only valid for the immediately following submission in the current task, expires in 30 minutes, and cannot be reused across tasks or repeated.
5. Submit After Confirmation
Submit only the draft that was just shown and whose content has not changed:
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, target repository Issues, and thebuglabel; keep the draft on failure. - If an Issue with the same component, reproduction steps, and actual behavior fingerprint already exists, return the original Issue URL; do not impersonate a duplicate with a broad title.
- If the body changed after confirmation, return
confirmation_mismatch; re-preview is required. - If the confirmation credential expired or was already used, return
confirmation_expired / confirmation_replayed; re-preview is required. - If the creation result does not have an explicit Issue URL, do not auto-retry; it may have already been created.
- Only when a GitHub Issue URL is obtained can you say "submitted."
Failure Handling
github_auth_required: Note that the draft is complete but not submitted; do not claim 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.- Target repository lacks permissions or is invisible: Do not redirect to any arbitrary repository; let the user decide whether to switch to the public Skills repository.