Turn a vague failure into a reviewable report. Nothing is submitted to GitHub, and your text is not saved between visits.

Your evidence

Do not paste tokens, private logs or personal data. Work stays in this browser tab. Review the text before sharing it elsewhere.

No report has been generated.

Describe one failure → Reduce the steps → Record exact versions → Compare the baseline
From a symptom to a reproducible report. Original explanatory illustration by Flock editorial, 2026. Based on the procedure below.

Describe one failure → Reduce the steps → Record exact versions → Compare the baseline.

Before sharing

Repeat the steps from a clean starting state and attach only the smallest reproduction you are allowed to share. Add the upstream issue link if one exists; a URL is useful context, not a substitute for your observed results.

The tool does not validate a claimed revision, execute a reproduction or decide whether a report belongs in Flock. Use the reporting procedure for that decision and the actual repository template when you are ready.

Sources & further reading

Find your next step

Browse the full sitemap