backend-review
Backend review for handlers, services, validation, errors, transactions, dependency boundaries, and service contracts.
- License 许可
- MIT
- 所属仓库
- aydabd/cacad
- 最近更新
- 2026-11-08
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- backend-review
- license
- MIT
- description
- Backend review for handlers, services, validation, errors, transactions, dependency boundaries, and service contracts.
03 SKILL.md 正文
Purpose
Backend review for handlers, services, validation, errors, transactions, dependency boundaries, and service contracts.
Review focus
- missing validation
- wrong status code
- transaction issue
- exception leak
- service boundary violation
- unsafe default
Method
- Inspect changed files and diff hunks relevant to this skill.
- Use repository-native tools when available.
- Prefer exact evidence from changed code.
- Emit findings using the shared JSONL finding contract.
- Avoid style-only comments unless they create maintainability or correctness risk.
Tooling hints
- Use
grepor editor search before opening files. - Use
git,grep, andghCLI. These are universally available and sufficient for all review tasks. - Do not depend on tools beyond
git,grep,cat,head,wc, andgh.
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.