report-issue

Form 2 because publishing on a public repository is a side effect the model must not trigger on its own — axis 2 of the design interview: the user types /report-issue, nothing chains it. The closest rejected form was keeping sonar-lessons' own publish step and writing a second one here; two publishers would hold two copies of the privacy rule and the duplicate search, and the first to change would leave the other filing the old way (invariant 2). Record: @.claude/decisions/0103-issue-filing-and-skeptical-triage.md.

Runs on opus: deciding which form a free description fits, what evidence it lacks, and what in it identifies the project is the judgment this skill exists for.

• A path under docs/lessons-learned/ → read the whole file. A sonar-NNN.md written by
• Free text → that is the description.
• Nothing → ask for one of the two, once, and stop without an answer.

1. Target — the slug from source.git_url in .claude/schemas/extensions.json
2. Version — .claude/.arch-provenance.json gives ref, commit and blueprint. No
3. Behind? — git ls-remote --tags --sort=-v:refname <git_url> and take the first tag.

Fetch the form the repository owns: curl -sS https://raw.githubusercontent.com/<owner>/<repo>/HEAD/.github/ISSUE_TEMPLATE/<form>.yml.

Ambiguous between bug and feature → ask, naming what tips each way. The form is the single owner of the title prefix (title:), labels (labels:), the sections and what each may carry — read all four from it, never from this file. No answer from the fetch → stop: no issue is written from memory of a form.

What a maintainer needs to verify the report, by form:

Read each item from the input first; for a bug, java .claude/hooks/ArchHook.java doctor fills the form's doctor field and often names the file at fault. Ask for every missing item in one AskUserQuestion. Still missing after the answer → stop, write nothing, and say which item would let the issue be verified. A guess written in the user's place is the claim the maintainer refutes first.

docs/lessons-learned/<name>.issue.md, where <name> is the input file's base name (sonar-NNN → sonar-NNN.issue.md), or issue-NNN for a description — NNN the highest existing issue-*.issue.md plus one, 001 when there is none.

One ### <label> heading per form field, in the form's order, filled from the input under that field's description — the same shape the web form produces. A markdown element has no label and is skipped; a checkboxes field is rendered as - [X] <option>, and only once the statement is true — the preflight boxes included: tick *I searched the existing issues* only after step 6's search ran. The Source version field, or the Environment field when the form has no version field, carries ref (short commit) · blueprint from step 2.

Then apply the privacy rule to every line, and re-read the file for src/, the project's base package, its group id, the project key, and any URL that is not github.com or a public documentation site. A hit is rewritten to the .claude/ owner or removed, and named in the question of step 6.

1. gh auth status. Not authenticated → stop: the body file is the deliverable, and the
2. gh issue list -R <slug> --state open --search "<terms>" with the form's label, for the
3. Ask — the body file's path and its sections, the duplicates found, the version warning

On the first option only: gh issue create -R <slug> --title "<form title prefix><summary>" --label <form label> --body-file docs/lessons-learned/<name>.issue.md. A failure naming the label (no triage permission on that repository) → the same command once without --label.

When the input was a lessons-learned file, write the outcome in the ## Issue line at its end — the URL, *declined*, *left for a manual edit* (with the command), or *not created — <reason>*. Every path out of steps 3, 4, 6 and 7 writes it: the file is what a later reader, or the next /sonar-lessons run, checks to know whether the lesson reached the meta-repository.

No provenance stamp: `` ❌ .claude/.arch-provenance.json not found — this project was not generated or adopted from Nerviz, so there is no version to report against. Nothing written. ``

Form not reachable: `` ❌ https://raw.githubusercontent.com/<slug>/HEAD/.github/ISSUE_TEMPLATE/<form>.yml did not answer. No issue is written from memory of a form. Nothing written. ``

Evidence missing after asking: `` ❌ Not filed: the report has no <literal output | file in .claude/ that promises the behavior | steps to reproduce>. The maintainer verifies every claim before acting on it; without this one the issue can only be closed as "needs evidence". Nothing written. ``

gh not authenticated: `` ⚠️ docs/lessons-learned/<name>.issue.md written. Issue not created: gh is not authenticated — run gh auth login, then: gh issue create -R <slug> --title "<title>" --label <form label> --body-file docs/lessons-learned/<name>.issue.md ``

✅ Report issue — <form> · <source version> <· behind <latest tag>>

Body ........ docs/lessons-learned/<name>.issue.md
Duplicates .. <#N title | none open>
Issue ....... <URL | not created — <reason> | declined | left for a manual edit: <command>>