A Chinese-language set of Go coding rules based on Google's Go Style Guide. Go is a programming language, and the rules cover formatting, naming, errors, comments, control flow, dependencies, and project structure.
A required workflow for changing code files. It checks the requirements and project specifications, organizes the work into tasks, loads coding rules, and guides implementation and review.
A workflow for creating unit, integration, and performance tests from a specification or existing code. TDD, or test-driven development, is a style of working where tests help define the expected behavior before implementation.
Implements code changes in an isolated context. Use for all implementation work — each task from tasks.md gets dispatched to an implementer. Independent tasks can run in parallel across multiple implementers.
Read-only codebase exploration. Use when you need to investigate code architecture, trace call chains, analyze module dependencies, or gather context for planning and design. Returns summarized findings, not raw file contents.
Use for reviewing low-level systems diffs (storage engines, distributed protocols, lock/memory/transaction code, critical runtime paths) where a change adds or modifies control-flow branches — allow-paths, fallbacks, type guards, nullability checks, trust boundaries exported to other subsystems. Best when subtle…
Per-finding code-review validator. Dispatched in parallel (one per finding) after reviewers return. Reads the cited code fresh, attempts a concrete reproduction or cites an exact rule, and renders a verdict with a confidence score and an optional committable suggestion.
Collaborate with Claude (Anthropic Claude Code model) for cross-model review and parallel problem-solving. Supports two modes - review (Claude reviews your work) and parallel (both agents work independently then compare), with multi-round continuity by recording Claude's sessionid and resuming it.
Multi-agent code review aligned with ultrareview. Dispatches five specialist reviewers in parallel (perf, robustness, standards, spec, proof-obligations), then runs a per-finding validator pass that independently reproduces every finding before it reaches the report. Use when asked to perform a code review.
Collaborate with Codex (OpenAI GPT model) for cross-model review and parallel problem-solving. Supports two modes — review (Codex reviews your work) and parallel (both agents work independently then compare).
Use this skill BEFORE starting any software engineering task that will span more than one step. It creates .agent/ /plan.md with goal, success criteria, and stepwise plan; presents the plan for approval; and drives execution step by step. Invoke when starting or resuming a new feature, investigative bug fix…
Process review comments on an MR, a design doc, or a spec — validate each finding independently with parallel validator subagents, apply fixes for the ones that hold up, and produce a reply report designed to earn reviewer sign-off. The report explains exactly how each confirmed issue was fixed, and for anything not…
Capture lessons that would make a similar future task faster, more accurate, or less error-prone, and suggest where each lesson should live (rule, skill, or memory) for human approval. Use proactively when you catch yourself making a wrong assumption, get corrected, hit a failure, or notice something non-obvious that…
Creates and fills spec.md sections 1-3 (background, goals, requirements) for new features and significant changes. Invoke when the task warrants a design doc — typically new features, significant refactors, or cross-module changes. Also triggered when the user explicitly asks to write a spec or clarify requirements.
Fills spec.md sections 4+ (design, alternatives, test plan, observability). Invoke after sections 1-3 are approved at Gate: Requirements Understanding. The agent researches the codebase, drafts the design, and presents at Gate: Solution Design for approval.
Breaks a spec.md into an implementable task list (tasks.md) with dependencies, context, and acceptance criteria. Invoke after the design is approved at Gate: Solution Design, before starting implementation.