Grok result handling
Skill dysfunc/ai-plugins-cc/dist/plugins/grok/skills/grok-result-handling
Use Codex, Gemini and Grok from Claude Code to review code or delegate tasks
npx -y skills add dysfunc/ai-plugins-cc --skill grok-result-handlingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Internal guidance for presenting Grok helper output back to the user
SKILL.md
1.9 KB, as published. Nobody here has run it
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.