Operations & Process Management
Writing Defect Reports
Establish a finding before you publish it, and correct it after — headlines that overstate what actually reproduces at the layer a user sees, reporting code that no entry point can reach or that is already dead, filing a caveat the project's own records already answered, re-verifying your prior notes against the tree instead of against the note, choosing the narrowest injection point that reproduces a failure without breaking the run first, capturing probe output a harness swallows, and withdrawing a published claim in the thread where you published it. Use when filing an issue, writing the body of a PR or code review that asserts a defect, triaging someone else's report, or deciding whether a suspicious observation is reportable at all.
- Publisher / source
- kajisho5/ffmpeg-skill (found on GitHub top repositories)
- Upstream record
- kajisho5/ffmpeg-skill
- Version
- Version 1
- Published
- Publication review
- Approved for publication
- Content fingerprint
774bb1a56a01efbcb6ba8e2c925fc416ac3477d8167a974a40d794054359b720