Relationships
#1105 Issue-filing skill should require ownership classification before submitting a bug
Opened by jeremy · 7/12/2026· Shipped 7/17/2026
Problem
After successfully filing one legitimate swamp-platform bug, an agent later hit a bug in the reporter's own actively-developed, unpublished extension -- and, without re-checking where the bug actually lived, filed three separate bug reports to swamp-club.com about that extension. The pattern generalized ("unexpected behavior -> file a swamp issue") from one correct use to three incorrect ones, without any step in between to re-classify where the fault actually was.
references/issue/guide.md documents --extension <name> for routing a
report to a third-party publisher's own repository, but never states
the more basic classification step that has to happen first: whose code
is this bug actually in?
Proposed solution
Add an explicit classification step near the top of references/issue/guide.md, before the "Commands" section:
"Before filing a bug report, classify where it lives:
- In swamp's own CLI/binary behavior -> file against swamp itself, no
--extensionflag. - In a third-party published extension you don't control -> file with
--extension <name>to route it to that extension's publisher. - In an extension you (or the human you're working with) are actively developing, in this repo's own source tree -> this is not a ticket. Fix the code yourself, or ask the human how they want it handled."
Alternatives considered
Trusting agents to infer this from context each time -- rejected because that's exactly what failed here: one correct filing established a pattern that then got over-applied without re-checking the premise each subsequent time.
Shipped
Click a lifecycle step above to view its details.