risk-classification
Classify PR risk and select which specialist reviewers should run based on changed files, diff shape, and risk hints.
- License 许可
- MIT
- 所属仓库
- aydabd/cacad
- 最近更新
- 2026-11-08
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- risk-classification
- license
- MIT
- description
- Classify PR risk and select which specialist reviewers should run based on changed files, diff shape, and risk hints.
03 SKILL.md 正文
Risk levels
low: docs, tests, isolated refactor, no production path.medium: normal feature/fix, internal API change, moderate logic change.high: auth, money, PII, DB migration, public API/event contract, infra, deployment, concurrency.critical: secrets exposure, destructive migration, security boundary, production incident fix.
Output
{
"risk": "high",
"changed_domains": ["backend", "api-contract", "tests"],
"agents_to_run": [
"security-reviewer",
"api-contract-reviewer",
"test-reviewer",
"pr-review-auditor"
],
"reason": "Controller and OpenAPI schema changed."
}
04 同仓库更多 Skills
token-optimization
Use zero-install context minimization first, with optional local optimization tooling when available.
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.