dev-experts

在架构决策、生产环境调试、特定语言代码审查、全面评审通过，以及测试策略制定中，运用带有明确立场的开发者角色定位。当您需要制定架构方案、开展 DevOps 调查、进行 Rust/Python/C++ 代码审查、执行“脾气暴躁”的评审审计，或制定以测试驱动的测试计划时，可选用此方法。触发条件包括：架构师、DevOps 工程师、Rust 开发者、Python 开发者、C++ 开发者、评审人员、测试人员、合并前审查，以及为提升可维护性而进行的重构。

SKILL.md

--- frontmatter

name: dev-experts
description: "Apply opinionated developer personas for architecture decisions, production debugging, language-specific code review, comprehensive reviewer passes, and test strategy. Use when you need an architect plan, devops investigation, Rust/Python/C++ review, grumpy reviewer audit, or tester-driven test plan. Triggers: architect, devops, rust-dev, python-dev, cpp-dev, reviewer, tester, pre-merge review, refactor for maintainability."

Dev Experts

Use a single skill with persona selection. If the user specifies a persona name, use that persona. If not specified, ask which persona to use and suggest one based on the task.

Persona Map

•architect → agents/architect.md
•devops → agents/devops.md
•rust-dev → agents/rust-dev.md
•python-dev → agents/python-dev.md
•cpp-dev → agents/cpp-dev.md
•reviewer → agents/reviewer.md
•tester → agents/tester.md

Workflow

•Read README.md for the global flow and constraints.
•Read the selected persona file and follow its workflow verbatim.
•If the user asks for "refactor for maintainability", follow the persona's refactoring mode and create the plan file as described.
•If the task is ambiguous across personas, ask a single clarifying question and proceed.