12 skills (repositories by linxule) · sorted by popularity
Run a read-only adversarial Kimi challenge review that questions assumptions, design choices, and tradeoffs. Use when the user wants pushback on whether the approach is right, not a defect-only review.
The English summary is being prepared. Showing the original description.
Return the stored rendered result for the latest or selected terminal Kimi job. Use when the user explicitly asks for a Kimi job result or artifact body.
The English summary is being prepared. Showing the original description.
Run an independent read-only Kimi review over the current working tree or a branch diff. Use when the user wants a second reviewer for defects, regressions, or implementation risks, not edits.
The English summary is being prepared. Showing the original description.
Show the latest or selected plugin-managed Kimi job for the current repository. Use when the user explicitly asks for Kimi job status or progress.
The English summary is being prepared. Showing the original description.
Ask Kimi a read-only free-form question about the current repository. Use for prose explanations, flow tracing, module comparisons, or conceptual reasoning where Codex should delegate the answer to local kimi-code rather than perform implementation.
The English summary is being prepared. Showing the original description.
Cancel an active plugin-managed Kimi job for the current repository. Use only when the user explicitly asks to cancel a Kimi run.
The English summary is being prepared. Showing the original description.
Run Kimi's autonomous goal mode for an explicitly requested hands-off multi-turn objective. This is write-capable and budget-bounded; use only when the user explicitly asks Kimi to pursue an objective autonomously.
The English summary is being prepared. Showing the original description.
Re-render a stored event log for a completed plugin-managed Kimi job. Use only when the user explicitly asks to replay a Kimi job.
The English summary is being prepared. Showing the original description.
Delegate a bounded write-capable investigation or implementation task to Kimi through the companion runtime. Use only when explicitly invoked or when the user clearly asks to hand off a substantial fix to Kimi.
The English summary is being prepared. Showing the original description.
List configured models, guide provider setup, verify local Kimi companion readiness, and manage the PreToolUse hook plus optional review gate. Use when asked about available models, subscription/API-key setup, default selection, or explicitly requested to install, check, enable, disable, or uninstall the integration. Codex and Claude Code share one ~/.kimi-code/config.toml but each own a host-scoped block, so $kimi-setup here does not disturb Claude Code's /kimi:setup (and vice-versa).
The English summary is being prepared. Showing the original description.
Run a write-capable Kimi swarm that edits many disjoint targets in a throwaway worktree and returns a reviewable patch. Use only for explicit parallel edit fan-out requests; the plugin never applies or commits the patch.
The English summary is being prepared. Showing the original description.
Run a read-only parallel Kimi review fan-out across many independent targets. Use only for explicit broad fan-out requests where one subagent per target is the point.
The English summary is being prepared. Showing the original description.