Menu
Draft a paste-ready Steward review reply. Use when the user asks for steward reply or wants a concise maintainer response.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | reply |
| description | Draft a paste-ready Steward review reply. Use when the user asks for steward reply or wants a concise maintainer response. |
Use this skill to draft a concise Steward review reply.
Read ../../shared/protocol.md before acting. Treat it as the source of truth for reply behavior and output.
Run only the reply gate.
Use the protocol output contract and include Reply:
Verdict: <short sentence>
Why: <short paragraph>
Missing evidence: <short list or "None">
Next action: <one concrete next step>
Case file: <absolute path>
Reply: <paste-ready sentence or short paragraph>
Route the Steward maintainer workflow in Codex. Use when the user invokes steward directly, asks for an ambiguous gate, or wants the umbrella workflow entrypoint.
Dispatch a bug or task report into conflict-aware PR-sized worktrees with `gmc wt add` and write LLM-ready `todo.md` files in each worktree. Use when the user explicitly asks to dispatch bugs from a report, split a bug or task report into PRs, create worktrees from a report, or hand off fixes into separate worktrees. Typical input is the output of `critical-bug-finder` or any structured bug report with identifiable files, problems, and fix goals. Do not use for generic bug finding, generic issue triage, or normal project planning without a report file.
Generate a concise Chinese evaluation prompt for DevOps CLI / command-line tool projects based on clig.onev.dev guidelines, with weights, thresholds, and hard gates. Use when a user asks to create or store a reusable CLI review prompt, a scoring rubric, an evaluation checklist, or wants to evaluate a command-line interface, terminal tool, or CLI best practices against design guidelines.
Generate a deep, code-first project wiki and VitePress documentation site (DeepWiki-style) for a repository. Use when asked to create a complete wiki/manual for a new codebase, build a code-first documentation site, or generate a `codewiki/` folder with structured Markdown, diagrams, and navigation based on the source code (not existing docs).
Read, write, and sync project memory stored as Markdown under `~/.agents/memories/{project-name}/`. Use when starting work and needing project context, when the user asks to read or update memory, or when ending a session and preserving stable learnings. Triggers: "read memory", "load memory", "write memory", "save memory", "update memory", "sync memory", "refresh memory", "读取记忆", "加载记忆", "写入记忆", "保存记忆", "更新记忆", "同步记忆".
Find critical implementation bugs that can crash production, corrupt data, bypass security, deadlock, race, or break core logic. Use for explicit fatal bug hunts such as "find critical bugs", "audit for fatal bugs", "security vulnerability audit", "race condition audit", "find crash or data loss bugs", or reliability incident reviews. Do not use for general code review, refactoring, style feedback, or routine performance analysis.