[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M754D6V4JE1KY8WDMHS6450M":3,"skill-same:01M754D6V4JE1KY8WDMHS6450M":61},{"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":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":39,"ownerDescription":40,"updatedAt":41,"install":42,"resources":54},"01M754D6V4JE1KY8WDMHS6450M","x-review-events",null,"Validates event schemas, producer\u002Fconsumer patterns, error handling, dead letter topics, and operational readiness for event-driven architectures.","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\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring-event-driven\u002F.claude\u002Fskills\u002Fx-review-events\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: x-review-events\ndescription: \"Validates event schemas, producer\u002Fconsumer patterns, error handling, dead letter topics, and operational readiness for event-driven architectures.\"\nuser-invocable: true\nallowed-tools: Read, Grep, Glob, Bash\nargument-hint: \"[event-name or consumer\u002Fproducer class]\"\ncontext-budget: medium\nrequires-capabilities: []\nfragment-slot: { slot: review-specialist, fragment-id: events, fragment-order: 60 }\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: Event-Driven Review\n\n## Purpose\n\nReviews event-driven patterns: event schema design, producer\u002Fconsumer implementation, error handling, dead letter topics, and operational readiness. Covers CloudEvents envelope, schema registry integration, and saga patterns.\n\n## Activation Condition\n\nInclude this skill when the project uses event-driven interfaces (`interfaces` contains `type: event-consumer` or `type: event-producer`).\n\n## Triggers\n\n- `\u002Fx-review-events OrderCreated` -- review a specific event\n- `\u002Fx-review-events PaymentConsumer` -- review a consumer class\n- `\u002Fx-review-events` -- review all event-driven patterns\n\n## Parameters\n\n| Parameter | Type | Required | Default | Description |\n|-----------|------|----------|---------|-------------|\n| `target` | String | No | (all) | Event name, consumer\u002Fproducer class name |\n\n## Knowledge Pack References\n\n| Pack | Files | Purpose |\n|------|-------|---------|\n| protocols | `skills\u002Fprotocols\u002Freferences\u002Fevent-driven-conventions.md` | CloudEvents envelope, event naming, schema registry, ordering guarantees, broker patterns |\n\n## Prerequisites\n\n- Event definitions exist (event classes, Avro\u002FProtobuf schemas, or JSON Schema)\n- Message broker dependency configured (Kafka, RabbitMQ, SQS, etc.)\n- Producer and\u002For consumer implementations exist\n\n## Workflow\n\n### Step 1 — Discover Event Definitions\n\nScan for event classes, schemas, Avro\u002FProtobuf definitions:\n- List all event types with their schemas\n- Identify event envelope structure\n\n### Step 2 — Discover Producers\n\nScan for classes publishing events:\n- Map producers to topics and event types\n- Identify publishing patterns (outbox, direct)\n\n### Step 3 — Discover Consumers\n\nScan for classes consuming events:\n- Map consumers to topics and consumer groups\n- Identify idempotency mechanisms\n\n### Step 4 — Validate Event Design\n\nCheck naming, envelope, versioning:\n- Past tense event names\n- CloudEvents spec compliance\n- Schema registry integration\n- Data minimization\n\n### Step 5 — Validate Producer Patterns\n\nCheck reliability:\n- Outbox or at-least-once delivery\n- Acknowledgment levels\n- Error handling and retry\n\n### Step 6 — Validate Consumer Patterns\n\nCheck processing:\n- Idempotency implementation\n- Offset commit strategy\n- Dead letter topic configuration\n- Graceful shutdown\n\n### Step 7 — Validate Operational Readiness\n\nCheck monitoring:\n- Consumer lag monitoring\n- Dead letter topic alerts\n- Schema registry health\n\n### Step 8 — 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## Event Design Checklist (10 points)\n\n### Schema & Naming (1-4)\n1. Event names use past tense (`OrderCreated`, `PaymentProcessed`, `InventoryReserved`)\n2. Event envelope follows CloudEvents spec or project-standard envelope (type, source, id, time, data)\n3. Schema registered in schema registry (Avro, Protobuf, or JSON Schema)\n4. Event versioning strategy defined: additive-only changes in same version, new event type for breaking changes\n\n### Data Design (5-7)\n5. Events contain only necessary data (data minimization, no full entity dump)\n6. Correlation ID present for distributed tracing\n7. No sensitive data in event payload (or encrypted if absolutely required)\n\n### Topic\u002FQueue Design (8-10)\n8. Topic naming follows convention: `{domain}.{entity}.{event}` (e.g., `payment.transaction.created`)\n9. Partition key chosen for ordering guarantees (e.g., entity ID for per-entity ordering)\n10. Message retention and compaction policy documented\n\n## Producer Checklist (8 points)\n\n11. Transactional outbox pattern used for reliable publishing (database + event in same transaction)\n12. OR: at-least-once delivery with consumer idempotency (if outbox not used, document why)\n13. Producer acknowledgment level appropriate (all replicas for critical events)\n14. Serialization uses registered schema (not ad-hoc JSON serialization)\n15. Error handling: failed publishes logged, retried with backoff, dead-lettered after max retries\n16. Idempotency key on producer if exactly-once semantics required\n17. Event published AFTER successful business operation (not before)\n18. Trace context propagated in event headers (W3C Trace Context)\n\n## Consumer Checklist (10 points)\n\n19. Consumer is idempotent (processing same event twice produces same result)\n20. Idempotency key stored and checked (event ID + consumer group, or business key)\n21. Consumer group ID follows convention: `{service}.{purpose}` (e.g., `billing.invoice-generator`)\n22. Offset commit strategy: commit after successful processing (not auto-commit)\n23. Error handling: failed processing -> retry with backoff -> dead letter topic after N retries\n24. Dead letter topic monitored with alerts\n25. Consumer lag monitored (alert if lag exceeds threshold)\n26. Deserialization errors handled gracefully (poison pill protection)\n27. Processing timeout configured (prevent infinite blocking)\n28. Graceful shutdown: stop consuming, finish in-flight, commit offsets, then exit\n\n## Saga Pattern Checklist (conditional -- if multi-step workflows)\n\n29. Saga orchestrator or choreography pattern documented\n30. Compensation actions defined for each saga step\n31. Saga state persisted (recoverable after crash)\n32. Timeout on saga completion (trigger compensation if exceeded)\n\n## Output Format\n\n```\n## Event-Driven Review — [Event\u002FChange Description]\n\n### Event Design: HIGH \u002F MEDIUM \u002F LOW\n### Producer Quality: HIGH \u002F MEDIUM \u002F LOW\n### Consumer Quality: HIGH \u002F MEDIUM \u002F LOW\n\n### Event Design Findings\n1. [Finding with file, line, issue, fix]\n\n### Producer Findings\n1. [Finding with file, line, issue, fix]\n\n### Consumer Findings\n1. [Finding with file, line, issue, fix]\n\n### Operational Readiness\n- Dead Letter Topic: [configured \u002F missing]\n- Consumer Lag Monitoring: [configured \u002F missing]\n- Schema Registry: [configured \u002F missing]\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 event definitions found | Report INFO: no event-driven code discovered |\n| Missing schema registry | REQUEST CHANGES with remediation guidance |\n| Consumer not idempotent | REQUEST CHANGES with idempotency pattern example |\n\n## Rules\n\n- REQUEST CHANGES if consumer is not idempotent\n- REQUEST CHANGES if no dead letter topic configured\n- REQUEST CHANGES if sensitive data in event payload\n- REQUEST CHANGES if no schema validation\u002Fregistry\n- REQUEST CHANGES if event published before business operation completes\n- Flag missing outbox pattern (suggest it, don't block if documented alternative exists)\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: Event-Driven Review\n\n## Purpose\n\nReviews event-driven patterns: event schema design, producer\u002Fconsumer implementation, error handling, dead letter topics, and operational readiness. Covers CloudEvents envelope, schema registry integration, and saga patterns.\n\n## Activation Condition\n\nInclude this skill when the project uses event-driven interfaces (`interfaces` contains `type: event-consumer` or `type: event-producer`).\n\n## Triggers\n\n- `\u002Fx-review-events OrderCreated` -- review a specific event\n- `\u002Fx-review-events PaymentConsumer` -- review a consumer class\n- `\u002Fx-review-events` -- review all event-driven patterns\n\n## Parameters\n\n| Parameter | Type | Required | Default | Description |\n|-----------|------|----------|---------|-------------|\n| `target` | String | No | (all) | Event name, consumer\u002Fproducer class name |\n\n## Knowledge Pack References\n\n| Pack | Files | Purpose |\n|------|-------|---------|\n| protocols | `skills\u002Fprotocols\u002Freferences\u002Fevent-driven-conventions.md` | CloudEvents envelope, event naming, schema registry, ordering guarantees, broker patterns |\n\n## Prerequisites\n\n- Event definitions exist (event classes, Avro\u002FProtobuf schemas, or JSON Schema)\n- Message broker dependency configured (Kafka, RabbitMQ, SQS, etc.)\n- Producer and\u002For consumer implementations exist\n\n## Workflow\n\n### Step 1 — Discover Event Definitions\n\nScan for event classes, schemas, Avro\u002FProtobuf definitions:\n- List all event types with their schemas\n- Identify event envelope structure\n\n### Step 2 — Discover Producers\n\nScan for classes publishing events:\n- Map producers to topics and event types\n- Identify publishing patterns (outbox, direct)\n\n### Step 3 — Discover Consumers\n\nScan for classes consuming events:\n- Map consumers to topics and consumer groups\n- Identify idempotency mechanisms\n\n### Step 4 — Validate Event Design\n\nCheck naming, envelope, versioning:\n- Past tense event names\n- CloudEvents spec compliance\n- Schema registry integration\n- Data minimization\n\n### Step 5 — Validate Producer Patterns\n\nCheck reliability:\n- Outbox or at-least-once delivery\n- Acknowledgment levels\n- Error handling and retry\n\n### Step 6 — Validate Consumer Patterns\n\nCheck processing:\n- Idempotency implementation\n- Offset commit strategy\n- Dead letter topic configuration\n- Graceful shutdown\n\n### Step 7 — Validate Operational Readiness\n\nCheck monitoring:\n- Consumer lag monitoring\n- Dead letter topic alerts\n- Schema registry health\n\n### Step 8 — 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## Event Design Checklist (10 points)\n\n### Schema & Naming (1-4)\n1. Event names use past tense (`OrderCreated`, `PaymentProcessed`, `InventoryReserved`)\n2. Event envelope follows CloudEvents spec or project-standard envelope (type, source, id, time, data)\n3. Schema registered in schema registry (Avro, Protobuf, or JSON Schema)\n4. Event versioning strategy defined: additive-only changes in same version, new event type for breaking changes\n\n### Data Design (5-7)\n5. Events contain only necessary data (data minimization, no full entity dump)\n6. Correlation ID present for distributed tracing\n7. No sensitive data in event payload (or encrypted if absolutely required)\n\n### Topic\u002FQueue Design (8-10)\n8. Topic naming follows convention: `{domain}.{entity}.{event}` (e.g., `payment.transaction.created`)\n9. Partition key chosen for ordering guarantees (e.g., entity ID for per-entity ordering)\n10. Message retention and compaction policy documented\n\n## Producer Checklist (8 points)\n\n11. Transactional outbox pattern used for reliable publishing (database + event in same transaction)\n12. OR: at-least-once delivery with consumer idempotency (if outbox not used, document why)\n13. Producer acknowledgment level appropriate (all replicas for critical events)\n14. Serialization uses registered schema (not ad-hoc JSON serialization)\n15. Error handling: failed publishes logged, retried with backoff, dead-lettered after max retries\n16. Idempotency key on producer if exactly-once semantics required\n17. Event published AFTER successful business operation (not before)\n18. Trace context propagated in event headers (W3C Trace Context)\n\n## Consumer Checklist (10 points)\n\n19. Consumer is idempotent (processing same event twice produces same result)\n20. Idempotency key stored and checked (event ID + consumer group, or business key)\n21. Consumer group ID follows convention: `{service}.{purpose}` (e.g., `billing.invoice-generator`)\n22. Offset commit strategy: commit after successful processing (not auto-commit)\n23. Error handling: failed processing -> retry with backoff -> dead letter topic after N retries\n24. Dead letter topic monitored with alerts\n25. Consumer lag monitored (alert if lag exceeds threshold)\n26. Deserialization errors handled gracefully (poison pill protection)\n27. Processing timeout configured (prevent infinite blocking)\n28. Graceful shutdown: stop consuming, finish in-flight, commit offsets, then exit\n\n## Saga Pattern Checklist (conditional -- if multi-step workflows)\n\n29. Saga orchestrator or choreography pattern documented\n30. Compensation actions defined for each saga step\n31. Saga state persisted (recoverable after crash)\n32. Timeout on saga completion (trigger compensation if exceeded)\n\n## Output Format\n\n```\n## Event-Driven Review — [Event\u002FChange Description]\n\n### Event Design: HIGH \u002F MEDIUM \u002F LOW\n### Producer Quality: HIGH \u002F MEDIUM \u002F LOW\n### Consumer Quality: HIGH \u002F MEDIUM \u002F LOW\n\n### Event Design Findings\n1. [Finding with file, line, issue, fix]\n\n### Producer Findings\n1. [Finding with file, line, issue, fix]\n\n### Consumer Findings\n1. [Finding with file, line, issue, fix]\n\n### Operational Readiness\n- Dead Letter Topic: [configured \u002F missing]\n- Consumer Lag Monitoring: [configured \u002F missing]\n- Schema Registry: [configured \u002F missing]\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 event definitions found | Report INFO: no event-driven code discovered |\n| Missing schema registry | REQUEST CHANGES with remediation guidance |\n| Consumer not idempotent | REQUEST CHANGES with idempotency pattern example |\n\n## Rules\n\n- REQUEST CHANGES if consumer is not idempotent\n- REQUEST CHANGES if no dead letter topic configured\n- REQUEST CHANGES if sensitive data in event payload\n- REQUEST CHANGES if no schema validation\u002Fregistry\n- REQUEST CHANGES if event published before business operation completes\n- Flag missing outbox pattern (suggest it, don't block if documented alternative exists)\n",{"name":5,"description":7,"allowed-tools":24,"argument-hint":25,"fragment-slot":26,"context-budget":30,"user-invocable":31,"requires-capabilities":32},"Read, Grep, Glob, Bash","[event-name or consumer\u002Fproducer class]",{"slot":27,"fragment-id":28,"fragment-order":29},"review-specialist","events",60,"medium",true,[],"main","952a630c6f38d193a349d86fa18db1de8843e837","src\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring-event-driven\u002F.claude\u002Fskills\u002Fx-review-events",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":43,"prompt":53,"zipAvailable":31},[44,47,50],{"tool":45,"command":46},"npx","npx skills add review-bench\u002Federcnj_ia-dev-environment --skill x-review-events",{"tool":48,"command":49},"bunx","bunx skills add review-bench\u002Federcnj_ia-dev-environment --skill x-review-events",{"tool":51,"command":52},"pnpm","pnpm dlx skills add review-bench\u002Federcnj_ia-dev-environment --skill x-review-events","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring-event-driven\u002F.claude\u002Fskills\u002Fx-review-events\u002FSKILL.md",[55],{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"README.md","REFERENCE","参考文档",1477,"https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring-event-driven\u002F.claude\u002Fskills\u002Fx-review-events\u002FREADME.md",[62,69,76,83,90,97],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"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":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"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":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"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":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"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":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"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":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"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",[],[]]