Loading...
Loading...
Found 6 Skills
Multi-perspective adversarial review. 4 Agents are spawned in parallel (full mode), each identifying issues from different perspectives, and the main thread makes a comprehensive ruling. Trigger methods: /story-review, /审查, "审查一下", "帮我审一下"
Review an implemented user story or task (via GitHub Pull Request) for completeness, test coverage, and code quality. Use this when asked to QA, review a PR, verify implementation, or as a follow-up to the user-story-implementer skill.
Review work after prose exists: editorial review, craft critique, continuity/voice review, copyediting, proofreading, and synthesis of reader-sim signal. Load when diagnosing a draft rather than rewriting it.
Multi-perspective adversarial review. Full/lean modes spawn in parallel when reviewer agents are deployed; automatically degrade to solo mode when agents are missing/abnormal or spawn fails; use built-in rubric fallback when reference files are unreadable. Trigger methods: /story-review, /审查, "审查一下", "帮我审一下"
Evaluate whether a development ticket (user story, feature request, bug report, etc.) is ready for development, and provide specific, actionable feedback if it is not. Use this skill whenever the user asks to triage, evaluate, assess, review, or check the readiness of a ticket, story, issue, or work item. The ticket can come from anywhere: pasted inline, read from a file, fetched from Jira or another tracker via MCP, or any other source. Also use this when a user asks "is this ticket ready?" or "what's wrong with this ticket?" or wants to improve a ticket's specification.
Get up to speed on the current branch's intent by analyzing commits, changes, and optionally a Linear ticket. Use when starting work on an existing branch.