菜单
Use when a dev is new to the project, asks for an overview, or wants to get oriented quickly. Fills graph gaps then runs a guided codebase interview.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | onboard-dev-agent |
| description | Use when a dev is new to the project, asks for an overview, or wants to get oriented quickly. Fills graph gaps then runs a guided codebase interview. |
| license | MIT |
| metadata | {"author":"wednesday-solutions","version":"1.0"} |
| requires | ["brownfield-fix","brownfield-chat"] |
| permissions | {"allow":["Bash(wednesday-skills fill-gaps *)","Bash(wednesday-skills analyze *)","Bash(wednesday-skills chat *)","Bash(git log *)"]} |
brownfield-fix — Before answering anything, check for high-risk files with low graph coverage:
wednesday-skills fill-gaps --min-risk 60brownfield-chat — Run a structured onboarding interview using the graph:
Answer each of these in order, citing sources:
Finish with: "Which area would you like to explore first?"
Unified development and design standards. Enforces code quality (complexity < 8), strict naming conventions, and the mandatory use of approved UI component libraries.
Unified Git workflow. Manages the entire task lifecycle: branch creation (sprint), atomic commits (git-os), and PR opening (pr-create).
Unified codebase intelligence. Handles all questions about structure, logic, risk, and dependencies. Combines natural-language Q&A with deterministic lookups and pre-edit blast radius checks.
Use when asked to audit a module, check its health, or assess whether it should be refactored. Runs structural query, risk check, and test generation automatically.
Full PR review orchestrator. Use when asked to review a PR or check if it is ready to merge. Runs blast radius + drift check on changed files, then hands off to pr-review for comment triage and fixes. Do NOT use pr-review directly for full reviews — use this.
Enforces architecture boundaries defined in PLAN.md. Use when a PR crosses module/service boundaries, when the dev asks "are we following the architecture?", or as a scheduled architecture health check. Not for querying what a module does — use brownfield-chat for that.