domain-classification
Map changed files to technical domain categories for routing to the correct specialist reviewers.
- License 许可
- MIT
- 所属仓库
- aydabd/runspec
- 最近更新
- 2026-06-06
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- domain-classification
- license
- MIT
- description
- Map changed files to technical domain categories for routing to the correct specialist reviewers.
03 SKILL.md 正文
Domain mapping rules
| File pattern | Domain |
|---|---|
*.go, *.java, *.py, *.ts (non-test) |
backend |
*_test.*, *.spec.*, **/test/** |
tests |
*.tsx, *.jsx, *.css, *.scss |
frontend |
*.sql, **/migrations/** |
database + data |
**/terraform/**, *.tf, *.k8s.yaml |
infra |
.github/workflows/**, *.ci.yml |
ci-cd |
**/openapi*, **/proto/**, **/asyncapi* |
api-contract |
go.mod, package.json, requirements.txt |
dependency |
*.md, CHANGELOG*, README* |
docs-content |
Rules
- A file can belong to multiple domains.
- Test files belong to
tests; do not also classify them asbackend. - Overlap between
databaseanddatais intentional — both reviewers apply. - When uncertain, prefer including a domain over excluding it.
Output
Compact JSON with domains map and recommended_agents list.
04 同仓库更多 Skills
testing-strategy
Testing philosophy and strategy. Use this when deciding what to test, naming tests, or identifying corner cases.
testing-patterns
Test implementation patterns. Use this when writing tests — table-driven tests, mocking, fixtures, assertions, and parallel execution.
testing-integration
Integration and E2E testing design. Use this when writing integration tests, E2E tests, or deciding what belongs in each test layer.
test-review
Test review for missing coverage, weak assertions, flaky tests, isolation, fixtures, and regression risk.
test-impact-selection
Select the minimal useful tests to run based on changed files, impacted components, and repository conventions.
severity-classification
Classify review findings into blocking, non-blocking, or note with consistent merge-risk rules.