link-review
Compatibility entry point for an explicitly requested independent link review. Uses the pi-servitors reviewer and callback contract.
- License 许可
- GPL-3.0
- 所属仓库
- Artawower/kaizen
- 最近更新
- 2026-11-10
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- link-review
- description
- Compatibility entry point for an explicitly requested independent link review. Uses the pi-servitors reviewer and callback contract.
03 SKILL.md 正文
Link Review
Load the pi-servitors skill and provision its reviewer role. Supply the original
goal, acceptance criteria, exact diff scope and relevant check results using the
returned worker destination and Lead reply identity.
Use the normal asynchronous task packet and callback contract. Do not poll for a result or assume worker names.
The Lead verifies findings against the actual diff and arbitrates disagreements. Do not defer automatically to the reviewer or modify files during a review-only request. Apply fixes only when authorized, following the shared correction policy.
04 同仓库更多 Skills
yt-analyze
Fetch YouTrack task + comments via MCP, critically analyze relevance and requirements, produce concise summary of what to implement, and build an implementation plan mapped to codebase. Trigger - YouTrack issue ID or request to "analyze task", "plan task", "break down YT issue".
youtrack-task
Analyzes a YouTrack issue, reviews comments and attachments, and proposes or creates actionable subtasks. Use when the user gives a YouTrack issue ID and wants synthesis, decomposition, or follow-up tasks.
youtrack-search
Searches YouTrack from natural language or native query syntax and returns a concise report with the most relevant issues. Use when the user wants to find issues, triage work, or translate a plain-language query into YouTrack search.
writing-for-agents
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
write-a-prd
Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.
vitest
Plan and write Vitest tests for changed code. Analyses git diff, checks existing tests, produces a concrete test plan using flat test structure (no describe/it blocks). Use when adding tests for new/changed code, improving Vitest coverage, or asking what to test after a change.