[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M751BYSDYA8NK5XK7XVP20XG":3,"skill-same:01M751BYSDYA8NK5XK7XVP20XG":56},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":49},"01M751BYSDYA8NK5XK7XVP20XG","x-review-grpc",null,"Validates gRPC service definitions, proto3 conventions, implementation patterns, and operational readiness.","review-bench\u002Federcnj_ia-dev-environment","review-bench","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F286778065?v=4","01M7517F9NTEPDZDAXJBR30FWT","ReviewBench","01M7517FAC9F4P7TGWCNJ8VYVW",0,"MIT","https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Fmain\u002Fresources\u002Ftargets\u002Fclaude\u002Fskills\u002Fconditional\u002Freview\u002Fx-review-grpc\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: x-review-grpc\ndescription: \"Validates gRPC service definitions, proto3 conventions, implementation patterns, and operational readiness.\"\nuser-invocable: true\nallowed-tools: Read, Grep, Glob, Bash\nargument-hint: \"[service-name or proto-file]\"\nrequires-capabilities: []\n---\n\n## Global Output Policy\n\n- **Language**: English ONLY.\n- **Tone**: Technical, Direct, and Concise.\n- **Efficiency**: Remove all conversational fillers and greetings to save tokens.\n\n# Skill: gRPC Service Review\n\n## Purpose\n\nReview gRPC service definitions, implementation patterns, and operational readiness for compliance with proto3 conventions, error handling standards, and observability requirements.\n\n## Activation Condition\n\nInclude this skill when the project uses gRPC protocol (`interfaces` contains `type: grpc`).\n\n## Triggers\n\n- `\u002Fx-review-grpc TransactionService` -- review a specific service\n- `\u002Fx-review-grpc proto\u002Ftransaction.proto` -- review a specific proto file\n- `\u002Fx-review-grpc` -- review all gRPC services and proto files\n\n## Parameters\n\n| Parameter | Type | Required | Default | Description |\n|-----------|------|----------|---------|-------------|\n| `target` | String | No | (all) | Service name or proto file path |\n\n## Knowledge Pack References\n\n| Pack | Files | Purpose |\n|------|-------|---------|\n| protocols | `skills\u002Fprotocols\u002Freferences\u002Fgrpc-conventions.md` | Proto3 style guide, naming, streaming patterns, error codes, health checks |\n\n## Prerequisites\n\n- Proto files (`*.proto`) exist in the codebase\n- gRPC framework dependency is configured\n- gRPC code generation plugin is configured in build tool\n\n## Workflow\n\n### Step 1 — Discover Proto Files\n\nScan for `*.proto` in project:\n- List all proto files with their package declarations\n- Identify service definitions and message types\n\n### Step 2 — Discover Service Implementations\n\nScan for classes implementing generated stubs:\n- Identify server-side service implementations\n- Identify client-side stub usage\n\n### Step 3 — Validate Proto File Conventions\n\nCheck each proto file:\n- Package naming follows reverse domain with version suffix\n- Service, message, and field naming conventions\n- Enum design with UNSPECIFIED=0\n- Versioning and compatibility rules\n\n### Step 4 — Validate Implementation Patterns\n\nCheck server and client code:\n- Deadline\u002Ftimeout propagation\n- Error model usage\n- Health checks and graceful shutdown\n- Interceptor usage for cross-cutting concerns\n\n### Step 5 — Validate Operational Readiness\n\nCheck observability:\n- OpenTelemetry trace propagation\n- Metrics per method\n- Structured logging\n- Sensitive data exclusion\n\n### Step 6 — Generate Report\n\nSummarize findings as checklist:\n- List compliant items\n- List violations with file paths and line numbers\n- Suggest fixes for each violation\n\n## Proto3 Style Checklist (12 points)\n\n### Package & Naming (1-4)\n1. Package follows reverse domain convention with version suffix (`com.company.service.v1`)\n2. Service names are PascalCase and end with `Service` (`TransactionService`)\n3. Message names are PascalCase (`CreateTransactionRequest`, `TransactionResponse`)\n4. Field names are snake_case (`transaction_id`, `created_at`)\n\n### Message Design (5-10)\n5. Every enum has `UNSPECIFIED = 0` as first value (proto3 default value safety)\n6. Request\u002FResponse messages are method-specific (no generic `Request` reuse)\n7. `oneof` used for mutually exclusive fields (not separate booleans)\n8. `repeated` fields have bounded size expectations documented in comments\n9. `google.protobuf.Timestamp` used for datetime (not string or int64)\n10. `google.protobuf.FieldMask` used for partial updates\n\n### Versioning & Compatibility (11-12)\n11. Breaking changes go in new package version (`v1` -> `v2`), never modify existing\n12. Deprecated fields use `reserved` statement (field number AND name)\n\n## Implementation Checklist (12 points)\n\n### Server-Side (13-18)\n13. Deadline\u002Ftimeout propagation: server reads deadline from context, propagates to downstream calls\n14. Error model uses `google.rpc.Status` with details (not plain `StatusRuntimeException` without context)\n15. Server reflection enabled for development\u002Fstaging (disabled in production if security requires)\n16. Health check protocol implemented (`grpc.health.v1.Health`)\n17. Graceful shutdown drains in-flight RPCs before terminating\n18. Interceptors used for cross-cutting concerns (auth, logging, tracing, metrics)\n\n### Client-Side (19-22)\n19. Deadlines always set on client calls (never unlimited timeout)\n20. Retry policy configured with exponential backoff\n21. Channel management: reuse channels, don't create per-call\n22. Client-side load balancing configured (round-robin or pick-first)\n\n### Streaming (23-24)\n23. Server streaming: flow control implemented (backpressure)\n24. Bidirectional streaming: error handling covers both directions independently\n\n## Observability Checklist (4 points)\n\n25. gRPC interceptor for OpenTelemetry trace propagation (W3C context)\n26. Metrics: `grpc.server.duration`, `grpc.server.request.count`, `grpc.server.response.count` per method\n27. Structured logging includes: method name, status code, duration, trace_id\n28. No sensitive data in metadata, logs, or traces\n\n## Output Format\n\n```\n## gRPC Review — [Service\u002FChange Description]\n\n### Proto Compliance: HIGH \u002F MEDIUM \u002F LOW\n### Implementation Quality: HIGH \u002F MEDIUM \u002F LOW\n\n### Proto Findings\n1. [Finding with file, line, issue, fix]\n\n### Implementation Findings\n1. [Finding with file, line, issue, fix]\n\n### Breaking Changes\n- [Any backward-incompatible changes identified]\n\n### Checklist Results\n[Items that passed \u002F failed \u002F not applicable]\n\n### Verdict: APPROVE \u002F REQUEST CHANGES\n```\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| No proto files found | Report INFO: no gRPC definitions discovered |\n| Enum missing UNSPECIFIED=0 | REQUEST CHANGES with proto3 convention reference |\n| Breaking change in existing version | REQUEST CHANGES with versioning guidance |\n\n## Rules\n\n- REQUEST CHANGES if enum missing UNSPECIFIED=0\n- REQUEST CHANGES if breaking change in existing proto version\n- REQUEST CHANGES if no deadline set on client calls\n- REQUEST CHANGES if sensitive data in metadata or logs\n- Verify all new proto messages have field documentation comments\n","## Global Output Policy\n\n- **Language**: English ONLY.\n- **Tone**: Technical, Direct, and Concise.\n- **Efficiency**: Remove all conversational fillers and greetings to save tokens.\n\n# Skill: gRPC Service Review\n\n## Purpose\n\nReview gRPC service definitions, implementation patterns, and operational readiness for compliance with proto3 conventions, error handling standards, and observability requirements.\n\n## Activation Condition\n\nInclude this skill when the project uses gRPC protocol (`interfaces` contains `type: grpc`).\n\n## Triggers\n\n- `\u002Fx-review-grpc TransactionService` -- review a specific service\n- `\u002Fx-review-grpc proto\u002Ftransaction.proto` -- review a specific proto file\n- `\u002Fx-review-grpc` -- review all gRPC services and proto files\n\n## Parameters\n\n| Parameter | Type | Required | Default | Description |\n|-----------|------|----------|---------|-------------|\n| `target` | String | No | (all) | Service name or proto file path |\n\n## Knowledge Pack References\n\n| Pack | Files | Purpose |\n|------|-------|---------|\n| protocols | `skills\u002Fprotocols\u002Freferences\u002Fgrpc-conventions.md` | Proto3 style guide, naming, streaming patterns, error codes, health checks |\n\n## Prerequisites\n\n- Proto files (`*.proto`) exist in the codebase\n- gRPC framework dependency is configured\n- gRPC code generation plugin is configured in build tool\n\n## Workflow\n\n### Step 1 — Discover Proto Files\n\nScan for `*.proto` in project:\n- List all proto files with their package declarations\n- Identify service definitions and message types\n\n### Step 2 — Discover Service Implementations\n\nScan for classes implementing generated stubs:\n- Identify server-side service implementations\n- Identify client-side stub usage\n\n### Step 3 — Validate Proto File Conventions\n\nCheck each proto file:\n- Package naming follows reverse domain with version suffix\n- Service, message, and field naming conventions\n- Enum design with UNSPECIFIED=0\n- Versioning and compatibility rules\n\n### Step 4 — Validate Implementation Patterns\n\nCheck server and client code:\n- Deadline\u002Ftimeout propagation\n- Error model usage\n- Health checks and graceful shutdown\n- Interceptor usage for cross-cutting concerns\n\n### Step 5 — Validate Operational Readiness\n\nCheck observability:\n- OpenTelemetry trace propagation\n- Metrics per method\n- Structured logging\n- Sensitive data exclusion\n\n### Step 6 — Generate Report\n\nSummarize findings as checklist:\n- List compliant items\n- List violations with file paths and line numbers\n- Suggest fixes for each violation\n\n## Proto3 Style Checklist (12 points)\n\n### Package & Naming (1-4)\n1. Package follows reverse domain convention with version suffix (`com.company.service.v1`)\n2. Service names are PascalCase and end with `Service` (`TransactionService`)\n3. Message names are PascalCase (`CreateTransactionRequest`, `TransactionResponse`)\n4. Field names are snake_case (`transaction_id`, `created_at`)\n\n### Message Design (5-10)\n5. Every enum has `UNSPECIFIED = 0` as first value (proto3 default value safety)\n6. Request\u002FResponse messages are method-specific (no generic `Request` reuse)\n7. `oneof` used for mutually exclusive fields (not separate booleans)\n8. `repeated` fields have bounded size expectations documented in comments\n9. `google.protobuf.Timestamp` used for datetime (not string or int64)\n10. `google.protobuf.FieldMask` used for partial updates\n\n### Versioning & Compatibility (11-12)\n11. Breaking changes go in new package version (`v1` -> `v2`), never modify existing\n12. Deprecated fields use `reserved` statement (field number AND name)\n\n## Implementation Checklist (12 points)\n\n### Server-Side (13-18)\n13. Deadline\u002Ftimeout propagation: server reads deadline from context, propagates to downstream calls\n14. Error model uses `google.rpc.Status` with details (not plain `StatusRuntimeException` without context)\n15. Server reflection enabled for development\u002Fstaging (disabled in production if security requires)\n16. Health check protocol implemented (`grpc.health.v1.Health`)\n17. Graceful shutdown drains in-flight RPCs before terminating\n18. Interceptors used for cross-cutting concerns (auth, logging, tracing, metrics)\n\n### Client-Side (19-22)\n19. Deadlines always set on client calls (never unlimited timeout)\n20. Retry policy configured with exponential backoff\n21. Channel management: reuse channels, don't create per-call\n22. Client-side load balancing configured (round-robin or pick-first)\n\n### Streaming (23-24)\n23. Server streaming: flow control implemented (backpressure)\n24. Bidirectional streaming: error handling covers both directions independently\n\n## Observability Checklist (4 points)\n\n25. gRPC interceptor for OpenTelemetry trace propagation (W3C context)\n26. Metrics: `grpc.server.duration`, `grpc.server.request.count`, `grpc.server.response.count` per method\n27. Structured logging includes: method name, status code, duration, trace_id\n28. No sensitive data in metadata, logs, or traces\n\n## Output Format\n\n```\n## gRPC Review — [Service\u002FChange Description]\n\n### Proto Compliance: HIGH \u002F MEDIUM \u002F LOW\n### Implementation Quality: HIGH \u002F MEDIUM \u002F LOW\n\n### Proto Findings\n1. [Finding with file, line, issue, fix]\n\n### Implementation Findings\n1. [Finding with file, line, issue, fix]\n\n### Breaking Changes\n- [Any backward-incompatible changes identified]\n\n### Checklist Results\n[Items that passed \u002F failed \u002F not applicable]\n\n### Verdict: APPROVE \u002F REQUEST CHANGES\n```\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| No proto files found | Report INFO: no gRPC definitions discovered |\n| Enum missing UNSPECIFIED=0 | REQUEST CHANGES with proto3 convention reference |\n| Breaking change in existing version | REQUEST CHANGES with versioning guidance |\n\n## Rules\n\n- REQUEST CHANGES if enum missing UNSPECIFIED=0\n- REQUEST CHANGES if breaking change in existing proto version\n- REQUEST CHANGES if no deadline set on client calls\n- REQUEST CHANGES if sensitive data in metadata or logs\n- Verify all new proto messages have field documentation comments\n",{"name":5,"description":7,"allowed-tools":24,"argument-hint":25,"user-invocable":26,"requires-capabilities":27},"Read, Grep, Glob, Bash","[service-name or proto-file]",true,[],"main","952a630c6f38d193a349d86fa18db1de8843e837","src\u002Fmain\u002Fresources\u002Ftargets\u002Fclaude\u002Fskills\u002Fconditional\u002Freview\u002Fx-review-grpc",1,"https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment","https:\u002F\u002Fgithub.com\u002Freview-bench","https:\u002F\u002Freview-bench.ai","An open benchmark for AI code review.","2026-10-27 06:56:37",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":26},[39,42,45],{"tool":40,"command":41},"npx","npx skills add review-bench\u002Federcnj_ia-dev-environment --skill x-review-grpc",{"tool":43,"command":44},"bunx","bunx skills add review-bench\u002Federcnj_ia-dev-environment --skill x-review-grpc",{"tool":46,"command":47},"pnpm","pnpm dlx skills add review-bench\u002Federcnj_ia-dev-environment --skill x-review-grpc","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Fmain\u002Fresources\u002Ftargets\u002Fclaude\u002Fskills\u002Fconditional\u002Freview\u002Fx-review-grpc\u002FSKILL.md",[50],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"README.md","REFERENCE","参考文档",1304,"https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Fmain\u002Fresources\u002Ftargets\u002Fclaude\u002Fskills\u002Fconditional\u002Freview\u002Fx-review-grpc\u002FREADME.md",[57,64,71,78,85,92],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M757M8J48TQ1Y3X25GSJBXAS","x-parallel-eval","Detects and classifies file-collision risks between work units (tasks, stories, or epic phases) before parallel execution. Reads ## File Footprint blocks produced by x-task-plan \u002F x-story-plan, applies the parallelism-heuristics knowledge pack (hard \u002F regen \u002F soft categories + hotspot overrides), and emits a collision matrix + serialization recommendation in Markdown (default) or JSON.","https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fx-parallel-eval\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M757M57XMR9546S69466HDWT","parallelism-heuristics","Canonical catalog of file-collision heuristics for parallel task, story, and epic execution. Defines the File Footprint block format, the three Conflict Categories (hard \u002F regen \u002F soft), a hotspot list of high-contention paths, and the degrade-with-warning policy. Consumed by x-task-plan, x-story-plan, x-epic-map, x-parallel-eval, and x-dev-*-implement.","https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fparallelism-heuristics\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M757M11SZ8P1VCQABT08QVYA","x-watch-pr-ci","Polls a PR's CI checks and Copilot review status, blocking until checks complete or timeout. Returns one of 8 stable exit codes (SUCCESS=0, CI_PENDING_PROCEED=10, CI_FAILED=20, TIMEOUT=30, PR_ALREADY_MERGED=40, NO_CI_CONFIGURED=50, PR_CLOSED=60, PR_NOT_FOUND=70). Writes a versioned state-file for session resume.","https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring\u002Fplatform-claude-code\u002F.claude\u002Fskills\u002Fx-watch-pr-ci\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M757KW53K8KFPGADFB4PH949","x-validate-docs","Documentation freshness gate: validates 6 dimensions (readme, api-specs, grpc-proto, adr, skill-docs, system-architecture) against code changes in a PR. Stack-aware — only validates targets declared\u002Fauto-detected from ProjectConfig.documentation.targets. Returns exit non-zero on staleness; produces structured report.","https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring\u002Fplatform-claude-code\u002F.claude\u002Fskills\u002Fx-validate-docs\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M757KQZHSA10MKC0CR571D60","x-update-system-architecture","Incrementally updates docs\u002Farchitecture\u002Fsystem.md after an epic completes. Appends new entries to the Decision Log (§11) using x-internal-write-report --append (dedup by ## ID: marker) and surgically inserts component\u002Fintegration changes into sections 1-10 via Edit. Idempotent: re-running with the same epic produces a byte-identical system.md.","https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring\u002Fplatform-claude-code\u002F.claude\u002Fskills\u002Fx-update-system-architecture\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M757KKBT5Q1SVF8DMJBVF46M","x-update-architecture","Incrementally updates the service architecture document with changes from architecture plans. Adds new components, integrations, flows, and ADR references without rewriting existing content. Use after implementation to keep architecture documentation current.","https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring\u002Fplatform-claude-code\u002F.claude\u002Fskills\u002Fx-update-architecture\u002FSKILL.md",[],[]]