菜单
Review code for quality, run linters, check test coverage, fix issues, and enforce gates. Save the final report to ./specs/issues/003-code-review-pi/PROMPT.md. Use before committing changes.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
| name | code-review-pi |
| description | Review code for quality, run linters, check test coverage, fix issues, and enforce gates. Save the final report to ./specs/issues/003-code-review-pi/PROMPT.md. Use before committing changes. |
Review code for quality, test coverage, and fix problems found.
The canonical output artifact for this skill is ./specs/issues/003-code-review-pi/PROMPT.md.
Only report success after writing the final review summary there.
Identify scope: Run git diff --name-only to find modified files. If there are changes, review only modified packages. If no uncommitted changes, review all packages (./...).
Run linters: Execute linters on target packages:
go vet ./...golangci-lint run --new-from-rev=HEAD~1 ./... (if available)Run tests and check coverage:
go test -race -count=1 -coverprofile=coverage.out ./...go tool cover -func=coverage.outReview code quality: Read target files and check for:
Fix issues in parallel using subagents: For each package needing coverage fixes, spawn a subagent to work on it concurrently:
agent tool to spawn one subagent per package that needs test coverage improvementgo test -race ./<pkg>/... to verify. NEVER delete existing tests."Verify gates: All gates must pass before reporting success:
go build ./... — zero errorsgo vet ./... — zero warningsgo test -race ./... — all tests passgo test -cover ./... — >= 80% per packageReport: Write the final summary to ./specs/issues/003-code-review-pi/PROMPT.md and present:
All gates are mandatory. Do not report success unless every gate passes.
| Gate | Command | Requirement |
|---|---|---|
| Build | go build ./... | Zero errors |
| Vet | go vet ./... | Zero warnings |
| Test | go test -race ./... | All pass |
| Coverage | go test -cover ./... | >= 80% per package |
/code-review — Full review: lint, test, coverage, parallel fix, verify gates基于 SOC 职业分类
Index a folder's contents into the MemPalace semantic memory for search and retrieval. Use this skill whenever the user asks to "index a folder", "index a directory", "index memory", "mine a project into memory", "make a folder searchable", "embed a folder", "ingest code into the palace", or "index this directory for semantic search". Covers the full flow: model download, mempalace.yaml room configuration, mining, and verification via search. Also trigger when the user says "memory index", "index memory of folder", or asks how to make a project's code semantically searchable with pi-go's MemPalace.
Lazy senior dev mode — always pick the simplest solution that works. Use this skill whenever writing, refactoring, or reviewing code to keep changes minimal: prefer the standard library, native platform features, and already-installed dependencies over new code or dependencies. Trigger when the user says "ponytail", "keep it simple", "simplest thing that works", "don't over-engineer", "lazy mode", or asks to avoid unnecessary abstractions, boilerplate, or premature complexity. The best code is the code never written.
Before any commit, run linters, vet, tests, and build verification; do not commit until checks pass
Go 1.24–1.26 coding guidelines for the dimetron/pi-go AI agent runtime. Use this skill whenever writing, reviewing, or refactoring ANY Go code in pi-go. This covers idiomatic style, error handling, concurrency, project layout, testing (table-driven, fuzz, benchmarks, synctest), new stdlib usage, golangci-lint v2 configuration, slog logging, and manual dependency injection with functional options. Always consult this skill before generating Go code for pi-go, even for small snippets, to ensure every output is idiomatic and modern.
Deep design review of Go codebase — naming, structure, consistency, interfaces, error handling. Scores each dimension and provides actionable fixes.
Mine project files or conversations into the MemPalace memory system. Indexes source code and conversation history as searchable palace drawers with semantic embeddings and room assignment.
