Documentation
README
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
This is the opening of the README. Read the full README on GitHub.