菜单
Accept an implementation — gates first, then human judgment — deciding mergeability against the spec's acceptance criteria, and wrapping up with distillation and archiving. Use for review, checking a diff/PR, acceptance, or judging mergeability.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Guides the user through writing a Chinese document section by section — interviewing out real material, clarifying intent, co-defining an outline, drafting each part with every claim traced to material, restructuring when drafting exposes gaps, and cold-reading as the target reader — to produce diagram-rich, first-principles prose free of AI-flavored writing. Use when the user wants to write, draft, or co-author a Chinese article, blog post, essay, design doc, README, or long-form document with guidance instead of one-shot generation.
Project entropy control (gc) — reconcile docs against code, clear dead code and stale docs, archive specs, scan friction, and generate architecture-improvement proposals. Use to clean up a project, when docs have drifted from reality, to find refactor directions, after a large feature merges (scoped), or for periodic maintenance (global).
Initialize a repo into an AI-native project — lay down the harness (AGENTS.md, standard verbs, gates, spec directory), same entry point for new and existing repos. Use for project initialization, onboarding an agent working agreement, or migrating legacy setup artifacts.
Converge a vague idea into a spec with acceptance criteria. Use for requirement discussion, approach clarification, unclear boundaries/decisions/acceptance criteria, or when an approach must be settled before implementation.
Compress the current conversation and work progress into a handoff note. Use for handoff, handover, resuming, summarizing progress, or letting a later session continue.
Translates English documents into natural Simplified Chinese while preserving meaning, document structure, terminology consistency, and author intent. Use when the user asks to translate English text, Markdown, documents, articles, specs, manuals, emails, reports, or files into Chinese, especially when they want idiomatic Chinese instead of literal translation.
| name | review |
| description | Accept an implementation — gates first, then human judgment — deciding mergeability against the spec's acceptance criteria, and wrapping up with distillation and archiving. Use for review, checking a diff/PR, acceptance, or judging mergeability. |
Acceptance, not a line-by-line recheck. What a machine can check goes to the gates; this skill only makes the judgments the gates can't cover.
AGENTS.md first. Gates not green → reject immediately, no human review.AGENTS.md or no defined gates, substitute its existing test / lint / build commands; if there's no runnable verification at all, say so honestly and write "verification missing" into the findings itself.docs/specs/). With no requirement source, review by code quality and risk, and state clearly that requirement conformance can't be judged.Sorted by severity, only actionable issues:
- [P1] Title
File/location:
Problem / Impact / Suggestion:
P0 data loss, serious security, core flow unusable; P1 must fix before merge; P2 boundary issue, test gap; P3 minor, non-blocking.
One of three: mergeable / revise and re-review / needs re-shape. When there are no issues, say explicitly that no blocking issues were found.
done, move it into docs/specs/archive/.CONTEXT.md; long-term decisions go into an ADR, with any overturned old ADR marked superseded.gc over the changed area.