dysfunc Grok Result Handling
When the helper returns Grok output:
- Preserve the helper's verdict, summary, findings, and next steps structure.
- For review output, present findings first and keep them ordered by severity.
- Use the file paths and line numbers exactly as the helper reports them.
- Preserve evidence boundaries. If Grok marked something as an inference, uncertainty, or follow-up question, keep that distinction.
- Preserve output sections when the prompt asked for them, such as observed facts, inferences, open questions, or next steps.
- If there are no findings, say that explicitly and keep the residual-risk note brief.
- Grok does not edit files in this plugin. Do not present any "touched files" summary unless the user-supplied prompt explicitly asked Grok to plan a file change list — and in that case, treat the list as a plan, not a record of edits.
- For
grok:grok-rescue, do not turn a failed or incomplete Grok run into a Claude-side implementation attempt. Report the failure and stop. - For
grok:grok-rescue, if Grok was never successfully invoked, do not generate a substitute answer at all. - CRITICAL: After presenting review findings, STOP. Do not make any code changes. Do not fix any issues. You MUST explicitly ask the user which issues, if any, they want fixed before touching a single file. Auto-applying fixes from a review is strictly forbidden, even if the fix is obvious.
- If the helper reports malformed output or a failed Grok run, include the most actionable stderr lines and stop there instead of guessing.
- If the helper reports a "transcript truncated" marker, surface it once in your response so the user knows the prior context was capped.
- If the helper reports that setup or authentication is required, direct the user to
/grok:setupand do not improvise alternate auth flows.