Vance IngallsandClaude Opus 4.8 6a3da1f624 docs(skills): tell agents to file reproducible render bugs, not paraphrases ...

The `hyperframes feedback` convention only prompted for a free-text
`--comment` "with the failing composition pattern and what you tried".
Agents dutifully filed vague reports (blank CJK text, mid-run exit, 4K
timeout) with no error string, no failure-mode, and — critically — no
published composition, so none could be reproduced or root-caused.

Two additions to the CLI skill:
- Lead bug reports with `--file-issue` (+ `--dir`), which publishes a
  minimal repro of the project to a public URL. A comment alone almost
  never lets a maintainer reproduce; the composition is what does.
- Give the `--comment` a concrete bug checklist: exact error string
  verbatim + whether output was produced / fell back / hard-exited; the
  isolated trigger; exact command + HF_*/PRODUCER_* env; frame/timestamp +
  visual defect. Drop the "repeat env" ask (the CLI already attaches it).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-07-12 11:28:09 -07:00

..

references

docs(skills): tell agents to file reproducible render bugs, not paraphrases

2026-07-12 11:28:09 -07:00

SKILL.md

docs(skills): tell agents to file reproducible render bugs, not paraphrases

2026-07-12 11:28:09 -07:00