
writing-defect-reports
Establish a finding before you publish it and correct it after - headlines that overstate what reproduces at the layer a user sees, reporting code no entry point reaches, guards that only match the fixture written beside them, caveats the project's own records already answered, prior notes re-verified against the tree rather than against the note, the narrowest injection point that reproduces a failure, probe output a harness swallows, red gates described as pre-existing, and withdrawing a published claim in the thread where it was published
- GitHub stars
- 108
Install
/plugin install writing-defect-reports@dev-skillsRun it inside Claude Code after adding the marketplace with /plugin marketplace add wdm0006/python-skills.
Sponsors
Details
- Marketplace
- wdm0006/python-skills
- Source
- Category
- community
More from wdm0006/python-skills
All 28- browser-extensions
- calibrating-thresholds-and-baselines
- deferring-heavy-dependencies
- go-projects
- guarding-destructive-operations
- merging-concurrent-branches
- normalizing-text-for-measurement
- permissioning-ci-workflows
- python-library-complete
- python-library-distribution
- python-library-foundations
- python-library-quality
- python-llm-features
- python-mcp-servers
- python-web-app
- reporting-derived-metrics
- reproducing-ci-locally
- resumable-sync-jobs
- rust-crates
- scala-projects
- shipping-across-surfaces
- shipping-build-artifacts
- shipping-swift-apps
- swift-apps