How this command is triggered — by the user, by Claude, or both
Slash command
/kimi:result [job-id]This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
Run: Present the full result verbatim. Preserve the original structure: - verdict/summary/findings/next-steps if it was a review - full response text if it was a task or ask If the job has findings, present them ordered by severity. Do NOT auto-fix any issues. Ask the user which issues to address.
Run:
node "${CLAUDE_PLUGIN_ROOT}/scripts/kimi-companion.mjs" result "$ARGUMENTS" --json
Present the full result verbatim. Preserve the original structure:
If the job has findings, present them ordered by severity. Do NOT auto-fix any issues. Ask the user which issues to address.
npx claudepluginhub bbingz/kimi-plugin-cc --plugin kimi/resultDisplays the full verbatim output of a finished Codex job by [job-id], including status, verdict, summary, findings, details, artifacts, next steps, errors, and follow-ups.
/resultManages background council jobs: lists active jobs, cancels a job by ID, or fetches the result of a completed job.
/resultRetrieves and displays the complete stored output from a finished multi-CLI job, preserving all details including verdict, findings, artifacts, and follow-up commands.
/resultDisplays the full final output of a finished Gemini job in the repository by job ID, preserving all details like verdict, summary, findings, artifacts, errors, and follow-up commands.
/resultRetrieves and displays the stored final output for a completed Pi job, including verdict, findings, artifacts, and next steps. Preserves all details without summarization.