16-phase feature orchestration workflow. Runs in the main thread as Kernel Mode. Coordinates the Lead→Developer→Reviewer→TestLead→Tester assembly line.
日本語の概要は準備中です。原文の説明を表示しています。
789 件 ・ 関連度順
概要と使いどころ
16-phase feature orchestration workflow. Runs in the main thread as Kernel Mode. Coordinates the Lead→Developer→Reviewer→TestLead→Tester assembly line.
日本語の概要は準備中です。原文の説明を表示しています。
当用户希望对内部 AI 用例、AI 产品功能、LLM 工作流或第三方 AI 供应商进行 AI 治理、法律风险、隐私、合规、采购或供应商风险审查时,使用本技能。当事实或证据缺失时,技能首先提出受理和澄清问题,识别所需的文件和缺失的证据,将用例映射到 AI 治理框架和适用的法律领域,并产出带记分卡、发现、责任方、补救行动和后续问题的初步或最终治理审查。
日本語の概要は準備中です。原文の説明を表示しています。
Triages reviewer comments on a GitHub PR: verifies each against the codebase, then accepts/pushes back/clarifies, replies in-thread. NOT for reviewing (mk:review-pr); NOT for fixes (mk:fix).
日本語の概要は準備中です。原文の説明を表示しています。
Triage reviewer comments on a GitHub PR with receiving-code-review discipline — verify each against the codebase, then accept/push-back/clarify, and optionally reply in-thread. Use when responding to received PR feedback. NOT for giving a review (see mk:review-pr); NOT for implementing the fixes (hand off to mk:fix).
日本語の概要は準備中です。原文の説明を表示しています。
Reviews public source notes and produces a bounded summary.
日本語の概要は準備中です。原文の説明を表示しています。
Generates comprehensive, context-aware code review checklists tailored to the specific codebase, programming language, and team standards. Analyzes PR diffs and suggests what reviewers should focus on.
日本語の概要は準備中です。原文の説明を表示しています。
Constructs and validates polygenic risk scores using LDpred2-auto, SBayesRC, MegaPRS, PRS-CS, PROSPER, MUSSEL, BridgePRS, JointPRS, PRSmix, or PGS Catalog Calculator with ancestry-aware reference panels (HapMap3, UKB-LD), ancestry-conditional calibration, and PRS-RS reporting standards. Use when computing PRS for cohorts, applying absolute-risk transformation, assessing cross-ancestry portability (Martin 2017 / Ding 2023 continuous ancestry), or auditing PRS manuscripts against the 22-item PRS-RS reviewer checklist.
日本語の概要は準備中です。原文の説明を表示しています。
Extract every PlantUML block from docs/specs/<slug>.md and render each to SVG under docs/specs/_rendered/<slug>/, with an index.md listing them in order. Run this before /approve-direction so the reviewer sees pictures instead of raw PlantUML.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive REST API design review with automated linting, breaking-change detection, and design scorecards. Catches inconsistent conventions, missing versioning, and design smells before APIs ship. Use when reviewing a PR that adds or changes API endpoints, auditing an existing API for v2 migration, or establishing API standards for a team.
日本語の概要は準備中です。原文の説明を表示しています。
Create or update a GitHub pull request following Medox conventions (author spicode-bot, reviewer spideystreet). Invoke manually with /pr — do NOT trigger automatically.
日本語の概要は準備中です。原文の説明を表示しています。
Draft a pull request description from the current branch diff plus rolling-wave project context. Use when the user wants PR body text, changes, potential risks, or reviewer notes for a branch, especially after completing a rolling-wave slice. Defaults to the Git Town parent branch when no base branch is named.
日本語の概要は準備中です。原文の説明を表示しています。
Prepare and risk-check the next rolling-wave slice for implementation. Use when the user wants to continue a rolling-wave project, draft one bounded slice in the main context by default, use a fresh planning author only when context or discovery cost warrants it, use a fresh preparation reviewer when semantic risk or uncertainty warrants independent pressure-testing, decompose parallel implementation chunks where appropriate, identify agent, human, either, or hybrid execution fit, write or update docs/rolling-wave/{project}/slices/NNN-slug.md, and mark that slice ready even when other slices are active.
日本語の概要は準備中です。原文の説明を表示しています。
Subagent flow for deep-reading GitHub issues + their linked/closing PRs to the bottom. Captures CURRENT state, maintainer status updates, reporter repro, blocking reviewer concerns, hidden second bugs, cross-repo duplicates. Invoked by weekly-report orchestrator; runs as a general-purpose subagent so the orchestrator's context stays small.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrator for agent-flow. Runs one issue or task through Implementer, Reviewer and QA as separate processes, with mechanical risk classification, a review-round cap and escalation to Needs Me, ending in a PR. Use for /implement <issue> or when asked to take an issue end to end ("have an agent take issue
日本語の概要は準備中です。原文の説明を表示しています。
Pursue an agreed goal to a working outcome without waiting: decompose it, re-prioritise as evidence arrives, branch, gate, get an independent review (a different model or a fresh reviewer subagent — the writer never approves), merge, prune, and bank the operator's decisions in STATUS.md instead of blocking on them. Trigger on "get it done", "don't wait for me", "proceed autonomously", or when an epic or roadmap objective is handed over. Not a close-out: this work set is expected to grow.
日本語の概要は準備中です。原文の説明を表示しています。
Review gate for correctness, reuse, and simplification. Produces a structured verdict with actionable findings. Trigger on any PR before merge, or on any agent-generated code before it is committed.
日本語の概要は準備中です。原文の説明を表示しています。
学术论文审稿意见回复信。输入是审稿人意见全文、reviewer comments、major/minor revision letter、或既有的 rebuttal 草稿时使用。功能包括:意见拆解 + ID 分配 + 行动映射(classify)、起草 point-by-point 回复(draft)、润色既有草稿(polish)、防御性与真实性审查(audit)、起草给编辑的 cover letter(cover)。覆盖期刊与会议 rebuttal、4 种困难场景(矛盾意见、不可能实验、缺关键证据、minor revision)。不适用于:正文段落写作(用 academic-writing)、图表生成(用 academic-figure)、参考文献格式(用 academic-citation)。
日本語の概要は準備中です。原文の説明を表示しています。
Use when reviewing, auditing, or optimizing skills — validates against the 7 Skill Killers checklist and produces fix recommendations.
日本語の概要は準備中です。原文の説明を表示しています。
Use when preparing a PR description, suggesting reviewers, or flagging risk — produces owner-mapped roles plus historical bug-pattern matches from project-local YAML.
日本語の概要は準備中です。原文の説明を表示しています。
Use when reviewing a README for accuracy, usability, and alignment with the actual repository. Detects invented content, broken setup steps, and structural issues.
日本語の概要は準備中です。原文の説明を表示しています。
Use when creating or editing a persona in src/agent-src/personas/ — voice / focus / unique questions / output expectations — even when the user just says 'add a reviewer voice for X'.
日本語の概要は準備中です。原文の説明を表示しています。
Role-based collaboration pattern (Drafter, Reviewer, Breaker). Assigns roles to available agents via prompt parameters. Use when starting multi-agent dev work.
日本語の概要は準備中です。原文の説明を表示しています。
Boot a four-agent visible-terminal team, get all four to "Ready to Rock!", lock live session names to roles, and launch a Lead/Reviewer/Breaker/Verifier sprint without mandate drift.
日本語の概要は準備中です。原文の説明を表示しています。
Habilidade abrangente de revisão de código para TypeScript, JavaScript, Python, Swift, Kotlin, Go. Inclui análise automatizada de código, verificação de boas práticas, scanning de segurança e geração de checklist de revisão. Use ao revisar pull requests, fornecer feedback de código, identificar problemas ou garantir padrões de qualidade de código.
日本語の概要は準備中です。原文の説明を表示しています。