issue-assessment

# `issue-assessment` — triage a gflow-cli issue honestly Read-only conductor. Verify the reporter's claim against the code, tests, docs, `KNOWN_ISSUES.md`, and auto-memory; classify it; judge whether it can be verified end-to-end *in the current environment*; and draft a reply. The output is a standard artifact a human or the `issue-resolve` skill can act on. **Core principle:** never assert more than the evidence supports. A claim is `CONFIRMED` only with line-level code evidence or a reproduction; a fix is "verified" only after running it on the **affected surface**. Honest "can't verify here" beats a false green check — a bounced fix costs more trust than an accurate "not yet." --- ## When to invoke - A new or updated GitHub issue needs a verdict before anyone spends effort. - An autonomous run (hermes-ops) reacts to an issue labelled for triage. - You're about to "just fix" a reported bug — assess first; the scope decision (reply-only vs hand to `issue-resolve`) depends on this. Skip for: issues that are obviously feature requests routed elsewhere, or already-triaged issues entering implementation. --- ## Invocation ``` /gflow:issue-assessment <issue number or URL> ``` This repo's `skills/*/SKILL.md` are plain Markdown — invoke by **reading** the file (via the `.claude/commands/gflow/*` wrapper), never `Skill(skill=...)`. --- ## Protocol ### 1. Ingest `gh issue view <N> --json title,body,comments,labels,author,state`. Extract: the claimed symptom, environme...