‹ 首页

team-routing

@wellapp-ai · 收录于 5 天前 · 上游提交 1 个月前

Detect domain from context and find appropriate team member

场景团队协作任务分派找人

适合你，如果你经常需要根据任务内容快速找到负责的同事。

/ 下载安装
https://github.com/wellapp-ai/well/tree/main/cursor-rules/skills/team-routing ↗
/ 通过 npx 安装 校验哈希
npx oh-my-skill add wellapp-ai/well/team-routing
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- wellapp-ai/well/team-routing
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify wellapp-ai/well/team-routing
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
340GitHub stars
~537上下文体积 · 单文件
索引托管

怎么用

商店整理自技能原文 · 版本 782601c · 表述以原文为准
它做什么

装上后，Claude 能从分支名或文件路径中提取关键词，查询 Notion 数据库找到对应领域，再分配一个可用的团队成员作为审查员，最后输出分配结果。

什么时候触发

当用户推送 PR（自动分配审查员）或初始化代码审查流程（显示领域上下文）时触发。

装好后可以这样说
Claude 分析分支名和文件，自动分配可用审查员。
Claude 从分支名提取关键词并查询领域数据库。
Claude 匹配文件路径模式并查询团队成员可用性。
技能原文 SKILL.md作者撰写 · MIT · 782601c

Team Routing Skill

Automatically detect domain from branch names or file paths and find the appropriate reviewer.

When to Use
  • Push PR mode: auto-assign reviewer
  • Init mode: show domain context
  • Any mode needing domain owner lookup
Phases
Phase 1: Extract Keywords

Extract domain keywords from context:

From branch name:

feature/tables-filter     → keywords: ["tables"]
fix/auth-token-expired    → keywords: ["auth"]
chore/settings-refactor   → keywords: ["settings"]

From changed files:

git diff --name-only origin/develop | head -20

Match file paths against known patterns:

  • apps/web/features/tables/ → "tables"
  • apps/api/routes/auth/ → "auth"
  • apps/web/features/settings/ → "settings"
Phase 2: Query Notion Domains Database
API-query-database: [Domains-DB-ID]
Filter: Keywords contains [extracted-keyword]
        OR Codebase_Paths contains [file-pattern]

Expected result:

  • Domain name
  • Topology type (stream-aligned, platform, enabling, complicated-subsystem)
  • Primary keywords
Phase 3: Query Team Capabilities
API-query-database: Team Capabilities
Filter: Primary_Domain matches [domain-name]
        AND Availability = "Available"
Sort: Open_PR_Count ASC

Expected result:

  • Person name
  • GitHub handle
  • Max Open PRs
  • Current Open PR count
Phase 4: Check Availability

For each candidate:

  1. Query current open PRs: ```bash gh pr list --state open --author [github_handle] --json number | jq length ```
  2. Compare against Max_Open_PRs threshold
  3. Skip if at or over capacity
Phase 5: Fallback Logic

If no available primary owner:

  1. Backup Owners: Query Skills table for overlapping skills
  2. Skills Match: Match changed file extensions to skill file patterns
  3. No Match: Return warning: "No available reviewer found for domain [X]"
Output

Present findings as:

## Domain Detection

**Branch:** [branch-name]
**Detected Domain:** [domain-name]
**Topology:** [stream-aligned | platform | enabling | complicated-subsystem]

### Reviewer Assignment

**Primary Owner:** @[github_handle] ([person_name])
**Availability:** [Available | At capacity (X/Y PRs)]
**Assignment:** [Assigned | Fallback to @backup | No available reviewer]
Integration

This skill is invoked by:

  • push-pr.mdc - Phase 1.2 (Find Reviewer)
  • init.mdc - Domain context display

Notion Databases Required:

  • Domains (keywords, codebase paths)
  • Team Capabilities (person, domain, availability, max PRs)
  • Skills (file patterns for fallback matching)
按 MIT 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。
…