← スキル一覧に戻る

code-investigation
by abyssparanoia
By using rapid-go you can quickly start developing a great API......
⭐ 18🍴 2📅 2026年1月20日
SKILL.md
name: code-investigation description: Efficient codebase investigation for rapid-go. Use when understanding existing code before modifications, tracing request flows from API to database, finding where functionality is implemented, or analyzing impact before changes. ALWAYS use before modifying existing code, fixing bugs, or adding features.
Code Investigation Guide
Quick Start
Proto (API contract) -> Handler -> Usecase -> Repository -> DB
Use this flow to trace any feature. Start from what you know.
Key Locations
| What | Where |
|---|---|
| API contracts | schema/proto/rapid/{admin_api,public_api,debug_api}/v1/ |
| Handlers | internal/infrastructure/grpc/internal/handler/{admin,public,debug}/ |
| Usecases | internal/usecase/*_impl.go |
| Domain models | internal/domain/model/ |
| Repository interfaces | internal/domain/repository/ |
| Repository implementations | internal/infrastructure/{mysql,postgresql,spanner}/repository/ |
| DI wiring | internal/infrastructure/dependency/dependency.go |
| Auth interceptors | internal/infrastructure/grpc/internal/interceptor/ |
Investigation Patterns
Find an API endpoint
# Find by HTTP path
grep "/admin/v1/tenants" schema/proto/rapid/
# Find by RPC name
grep "CreateTenant" internal/infrastructure/grpc/internal/handler/admin/
Trace request flow
- Find RPC in
schema/proto/rapid/**/api.proto - Find handler in
internal/infrastructure/grpc/internal/handler/{actor}/ - Find interactor in
internal/usecase/*_impl.go - Find repository in
internal/domain/repository/(interface) andinternal/infrastructure/*/repository/(impl)
Find all usages of a type
# Find usages of a domain model
grep "model.Staff" internal/
# Find usages of a repository method
grep "staffRepository.Get" internal/usecase/
Check authorization logic
- Session extraction:
internal/infrastructure/grpc/internal/interceptor/session_interceptor/ - Access control:
internal/infrastructure/grpc/internal/interceptor/authorization_interceptor/ - Role checks in usecase: look for
param.AdminRole.IsRoot()patterns
Impact analysis before changes
- Find interface definition in
internal/domain/repository/ - Find all implementations in
internal/infrastructure/*/repository/ - Find all callers in
internal/usecase/ - Check mock generation:
internal/domain/repository/mock/
Common Search Patterns
| Goal | Search |
|---|---|
| Find entity by name | grep "type Staff struct" internal/domain/model/ |
| Find error definition | grep "StaffNotFoundErr" internal/domain/errors/ |
| Find input validation | grep "type AdminCreateStaff" internal/usecase/input/ |
| Find marshaller | grep "StaffToModel|StaffToPb" internal/ |
| Find DI registration | grep "AdminStaffInteractor" internal/infrastructure/dependency/ |
Tips
- Start from proto for API-related investigation
- Start from domain model for business logic investigation
- Check
dependency.goto understand how components are wired - Marshallers exist in two places: repository (DB<->domain) and handler (domain<->proto)
スコア
総合スコア
50/100
リポジトリの品質指標に基づく評価
✓SKILL.md
SKILL.mdファイルが含まれている
+20
○LICENSE
ライセンスが設定されている
0/10
○説明文
100文字以上の説明がある
0/10
○人気
GitHub Stars 100以上
0/15
○最近の活動
3ヶ月以内に更新がある
0/10
○フォーク
10回以上フォークされている
0/5
✓Issue管理
オープンIssueが50未満
+5
✓言語
プログラミング言語が設定されている
+5
○タグ
1つ以上のタグが設定されている
0/5
レビュー
💬
レビュー機能は近日公開予定です