[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M754EP7TW3DNADSPW9PP1NAX":3,"skill-same:01M754EP7TW3DNADSPW9PP1NAX":57},{"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":29,"commitSha":30,"skillDirectory":31,"forksCount":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":35,"ownerDescription":36,"updatedAt":37,"install":38,"resources":50},"01M754EP7TW3DNADSPW9PP1NAX","x-update-architecture",null,"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.","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-update-architecture\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: x-update-architecture\ndescription: \"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.\"\nuser-invocable: true\nallowed-tools: Read, Write, Edit, Bash, Grep, Glob\nargument-hint: \"[STORY-ID or architecture-plan-path]\"\ncontext-budget: light\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: Service Architecture Document Updater\n\n## Purpose\n\nIncrementally updates the service architecture document (`steering\u002Fservice-architecture.md`) with changes from architecture plans. Adds new components, integrations, flows, and ADR references without rewriting existing content.\n\n## Triggers\n\n- `\u002Fx-update-architecture [STORY-ID]` — update architecture doc from the architecture plan for the given story\n- `\u002Fx-update-architecture [architecture-plan-path]` — update architecture doc from the specified plan file\n- After a feature is implemented and an architecture plan exists\n- When Phase 3 (Documentation) of `x-implement-story` is executing\n- SKIP when no architecture plan exists for the feature\n\n## Parameters\n\n| Parameter | Type | Required | Description |\n|-----------|------|----------|-------------|\n| `STORY-ID` | String | Yes (or path) | Story identifier to locate the architecture plan |\n| `architecture-plan-path` | String | Yes (or ID) | Direct path to the architecture plan file |\n\n## Workflow\n\n### Step 1 — Read Inputs\n\n1. Read the architecture plan at the path provided as argument\n2. Read the current service architecture doc at `steering\u002Fservice-architecture.md`\n3. If `service-architecture.md` does NOT exist, read the template from `resources\u002Ftemplates\u002F_TEMPLATE-SERVICE-ARCHITECTURE.md` and create the initial document by replacing `{{ placeholders }}` with project identity values\n\n### Step 2 — Identify Changes\n\n1. Compare the architecture plan sections against the current service architecture doc\n2. For each section, identify: new components, new integrations, new flows, new ADRs, changed NFRs, new observability or resilience configurations\n3. Build a diff list of changes per section\n\n### Step 3 — Apply Incremental Updates (RULE-008 — Content Preservation)\n\nFor each changed section, INSERT new content at the appropriate location. NEVER remove or rewrite existing content.\n\n| # | Section Heading | Update Action |\n|---|-----------------|---------------|\n| 1 | 1. Overview | Append new interfaces or technology changes |\n| 2 | 2. C4 Diagrams | Add new nodes and edges to existing Mermaid diagrams |\n| 3 | 3. Integrations | Append new rows to the integration table |\n| 4 | 4. Data Model | Add new entities and relationships to the ER diagram |\n| 5 | 5. Critical Flows | Add new sequence diagrams as new subsections |\n| 6 | 6. NFRs | Update targets only if changed; never remove rows |\n| 7 | 7. Architectural Decisions | Append new ADR references to the table |\n| 8 | 8. Observability | Add new metrics, alerts, or dashboard entries |\n| 9 | 9. Resilience | Add new circuit breaker, retry, or fallback configurations |\n| 10 | 10. Change History | Append a new changelog entry with date, story ID, and summary |\n\n#### Content Preservation Rules\n\n- NEVER remove existing content from any section\n- NEVER rewrite a section — only insert or append\n- If a component was refactored: mark old as deprecated, add new\n- If a flow changed: add new version, mark previous as \"v1\"\n- Merge conflicts: preserve both versions\n\n#### Change History Entry Format\n\n| Date | Author | Description |\n|------|--------|-------------|\n| YYYY-MM-DD | AI (story-XXXX-YYYY) | Sections affected: [list]. Summary: [brief description] |\n\n### Step 4 — Update Change History\n\nALWAYS append a new row to Section 10 (Change History). Include: today's date, story ID, list of sections modified, brief summary.\n\n### Step 5 — Save\n\n1. Write the updated document to `steering\u002Fservice-architecture.md`\n2. Report: sections updated, changes applied, new entries added\n\n## Document Creation from Scratch\n\nIf `steering\u002Fservice-architecture.md` does NOT exist:\n\n1. Read the template from `resources\u002Ftemplates\u002F_TEMPLATE-SERVICE-ARCHITECTURE.md`\n2. Replace `{{ placeholders }}` with project identity values\n3. Populate sections from the architecture plan data\n4. Add an initial Change History entry\n\n## Template Fallback\n\nIf `resources\u002Ftemplates\u002F_TEMPLATE-SERVICE-ARCHITECTURE.md` is not found, create a minimal service architecture document with 10 numbered sections and populate from the architecture plan. Log a warning: `\"Template not found; using inline fallback structure.\"`\n\n## Subagent Prompt\n\nLaunch a **single** `general-purpose` subagent:\n\n> You are a **Documentation Engineer** performing an incremental update of the\n> service architecture document for {{PROJECT_NAME}}.\n>\n> **Step 1 — Read inputs:**\n> - Read the architecture plan at the path provided as argument\n> - Read the current service architecture doc at `steering\u002Fservice-architecture.md`\n> - If `service-architecture.md` does NOT exist, read the template from\n>   `resources\u002Ftemplates\u002F_TEMPLATE-SERVICE-ARCHITECTURE.md` and create the initial document\n>   by replacing `{{ placeholders }}` with project identity values\n>\n> **Step 2 — Identify changes:**\n> - Compare the architecture plan sections against the current service architecture doc\n> - For each section, identify: new components, new integrations, new flows, new ADRs,\n>   changed NFRs, new observability or resilience configurations\n> - Build a diff list of changes per section\n>\n> **Step 3 — Apply incremental updates (RULE-008):**\n> - For each changed section, INSERT new content at the appropriate location\n> - NEVER remove or rewrite existing content\n> - For C4 diagrams: add new Mermaid nodes and edges within existing graph blocks\n> - For tables: append new rows\n> - For sequence diagrams: add new subsections with new diagrams\n> - For ADR references: append new rows to the ADR table\n>\n> **Step 4 — Update Change History:**\n> - ALWAYS append a new row to Section 10 (Change History)\n> - Include: today's date, story ID, list of sections modified, brief summary\n>\n> **Step 5 — Save:**\n> - Write the updated document to `steering\u002Fservice-architecture.md`\n> - Report: sections updated, changes applied, new entries added\n>\n> **Conventions:**\n> - All content in English (RULE-012)\n> - Mermaid syntax for all diagrams\n> - Incremental updates only — never full rewrite (RULE-008)\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| Architecture plan not found | Skip with log: \"No architecture plan found; skipping architecture doc update\" |\n| Service architecture doc not found | Create from template (see Document Creation from Scratch) |\n| Template not found | Use inline fallback structure, log warning |\n| Section heading mismatch | Match by numeric prefix, warn if heading text differs |\n| Merge conflict in Mermaid diagram | Preserve both versions, add comment marking conflict |\n\n## Integration Notes\n\n| Skill | Relationship | Context |\n|-------|-------------|---------|\n| `x-implement-story` | called-by | Invoked during Phase 3 (Documentation) to update architecture doc |\n| `x-plan-architecture` | reads | Generates the input architecture plans consumed by this skill |\n| `x-generate-adr` | calls | May trigger ADR generation for new architectural decisions |\n| `architecture` | reads | References architecture principles and patterns KP |\n\n## Knowledge Pack References\n\n| Pack | Files | Purpose |\n|------|-------|---------|\n| architecture | `knowledge\u002Farchitecture.md` | Architecture principles and patterns |\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: Service Architecture Document Updater\n\n## Purpose\n\nIncrementally updates the service architecture document (`steering\u002Fservice-architecture.md`) with changes from architecture plans. Adds new components, integrations, flows, and ADR references without rewriting existing content.\n\n## Triggers\n\n- `\u002Fx-update-architecture [STORY-ID]` — update architecture doc from the architecture plan for the given story\n- `\u002Fx-update-architecture [architecture-plan-path]` — update architecture doc from the specified plan file\n- After a feature is implemented and an architecture plan exists\n- When Phase 3 (Documentation) of `x-implement-story` is executing\n- SKIP when no architecture plan exists for the feature\n\n## Parameters\n\n| Parameter | Type | Required | Description |\n|-----------|------|----------|-------------|\n| `STORY-ID` | String | Yes (or path) | Story identifier to locate the architecture plan |\n| `architecture-plan-path` | String | Yes (or ID) | Direct path to the architecture plan file |\n\n## Workflow\n\n### Step 1 — Read Inputs\n\n1. Read the architecture plan at the path provided as argument\n2. Read the current service architecture doc at `steering\u002Fservice-architecture.md`\n3. If `service-architecture.md` does NOT exist, read the template from `resources\u002Ftemplates\u002F_TEMPLATE-SERVICE-ARCHITECTURE.md` and create the initial document by replacing `{{ placeholders }}` with project identity values\n\n### Step 2 — Identify Changes\n\n1. Compare the architecture plan sections against the current service architecture doc\n2. For each section, identify: new components, new integrations, new flows, new ADRs, changed NFRs, new observability or resilience configurations\n3. Build a diff list of changes per section\n\n### Step 3 — Apply Incremental Updates (RULE-008 — Content Preservation)\n\nFor each changed section, INSERT new content at the appropriate location. NEVER remove or rewrite existing content.\n\n| # | Section Heading | Update Action |\n|---|-----------------|---------------|\n| 1 | 1. Overview | Append new interfaces or technology changes |\n| 2 | 2. C4 Diagrams | Add new nodes and edges to existing Mermaid diagrams |\n| 3 | 3. Integrations | Append new rows to the integration table |\n| 4 | 4. Data Model | Add new entities and relationships to the ER diagram |\n| 5 | 5. Critical Flows | Add new sequence diagrams as new subsections |\n| 6 | 6. NFRs | Update targets only if changed; never remove rows |\n| 7 | 7. Architectural Decisions | Append new ADR references to the table |\n| 8 | 8. Observability | Add new metrics, alerts, or dashboard entries |\n| 9 | 9. Resilience | Add new circuit breaker, retry, or fallback configurations |\n| 10 | 10. Change History | Append a new changelog entry with date, story ID, and summary |\n\n#### Content Preservation Rules\n\n- NEVER remove existing content from any section\n- NEVER rewrite a section — only insert or append\n- If a component was refactored: mark old as deprecated, add new\n- If a flow changed: add new version, mark previous as \"v1\"\n- Merge conflicts: preserve both versions\n\n#### Change History Entry Format\n\n| Date | Author | Description |\n|------|--------|-------------|\n| YYYY-MM-DD | AI (story-XXXX-YYYY) | Sections affected: [list]. Summary: [brief description] |\n\n### Step 4 — Update Change History\n\nALWAYS append a new row to Section 10 (Change History). Include: today's date, story ID, list of sections modified, brief summary.\n\n### Step 5 — Save\n\n1. Write the updated document to `steering\u002Fservice-architecture.md`\n2. Report: sections updated, changes applied, new entries added\n\n## Document Creation from Scratch\n\nIf `steering\u002Fservice-architecture.md` does NOT exist:\n\n1. Read the template from `resources\u002Ftemplates\u002F_TEMPLATE-SERVICE-ARCHITECTURE.md`\n2. Replace `{{ placeholders }}` with project identity values\n3. Populate sections from the architecture plan data\n4. Add an initial Change History entry\n\n## Template Fallback\n\nIf `resources\u002Ftemplates\u002F_TEMPLATE-SERVICE-ARCHITECTURE.md` is not found, create a minimal service architecture document with 10 numbered sections and populate from the architecture plan. Log a warning: `\"Template not found; using inline fallback structure.\"`\n\n## Subagent Prompt\n\nLaunch a **single** `general-purpose` subagent:\n\n> You are a **Documentation Engineer** performing an incremental update of the\n> service architecture document for {{PROJECT_NAME}}.\n>\n> **Step 1 — Read inputs:**\n> - Read the architecture plan at the path provided as argument\n> - Read the current service architecture doc at `steering\u002Fservice-architecture.md`\n> - If `service-architecture.md` does NOT exist, read the template from\n>   `resources\u002Ftemplates\u002F_TEMPLATE-SERVICE-ARCHITECTURE.md` and create the initial document\n>   by replacing `{{ placeholders }}` with project identity values\n>\n> **Step 2 — Identify changes:**\n> - Compare the architecture plan sections against the current service architecture doc\n> - For each section, identify: new components, new integrations, new flows, new ADRs,\n>   changed NFRs, new observability or resilience configurations\n> - Build a diff list of changes per section\n>\n> **Step 3 — Apply incremental updates (RULE-008):**\n> - For each changed section, INSERT new content at the appropriate location\n> - NEVER remove or rewrite existing content\n> - For C4 diagrams: add new Mermaid nodes and edges within existing graph blocks\n> - For tables: append new rows\n> - For sequence diagrams: add new subsections with new diagrams\n> - For ADR references: append new rows to the ADR table\n>\n> **Step 4 — Update Change History:**\n> - ALWAYS append a new row to Section 10 (Change History)\n> - Include: today's date, story ID, list of sections modified, brief summary\n>\n> **Step 5 — Save:**\n> - Write the updated document to `steering\u002Fservice-architecture.md`\n> - Report: sections updated, changes applied, new entries added\n>\n> **Conventions:**\n> - All content in English (RULE-012)\n> - Mermaid syntax for all diagrams\n> - Incremental updates only — never full rewrite (RULE-008)\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| Architecture plan not found | Skip with log: \"No architecture plan found; skipping architecture doc update\" |\n| Service architecture doc not found | Create from template (see Document Creation from Scratch) |\n| Template not found | Use inline fallback structure, log warning |\n| Section heading mismatch | Match by numeric prefix, warn if heading text differs |\n| Merge conflict in Mermaid diagram | Preserve both versions, add comment marking conflict |\n\n## Integration Notes\n\n| Skill | Relationship | Context |\n|-------|-------------|---------|\n| `x-implement-story` | called-by | Invoked during Phase 3 (Documentation) to update architecture doc |\n| `x-plan-architecture` | reads | Generates the input architecture plans consumed by this skill |\n| `x-generate-adr` | calls | May trigger ADR generation for new architectural decisions |\n| `architecture` | reads | References architecture principles and patterns KP |\n\n## Knowledge Pack References\n\n| Pack | Files | Purpose |\n|------|-------|---------|\n| architecture | `knowledge\u002Farchitecture.md` | Architecture principles and patterns |\n",{"name":5,"description":7,"allowed-tools":24,"argument-hint":25,"context-budget":26,"user-invocable":27,"requires-capabilities":28},"Read, Write, Edit, Bash, Grep, Glob","[STORY-ID or architecture-plan-path]","light",true,[],"main","952a630c6f38d193a349d86fa18db1de8843e837","src\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring-event-driven\u002F.claude\u002Fskills\u002Fx-update-architecture",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":39,"prompt":49,"zipAvailable":27},[40,43,46],{"tool":41,"command":42},"npx","npx skills add review-bench\u002Federcnj_ia-dev-environment --skill x-update-architecture",{"tool":44,"command":45},"bunx","bunx skills add review-bench\u002Federcnj_ia-dev-environment --skill x-update-architecture",{"tool":47,"command":48},"pnpm","pnpm dlx skills add review-bench\u002Federcnj_ia-dev-environment --skill x-update-architecture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring-event-driven\u002F.claude\u002Fskills\u002Fx-update-architecture\u002FSKILL.md",[51],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"README.md","REFERENCE","参考文档",1781,"https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring-event-driven\u002F.claude\u002Fskills\u002Fx-update-architecture\u002FREADME.md",[58,65,72,79,86,93],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"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":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"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":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"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":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"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":94,"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":95,"categories":96,"keywords":97,"publishedAt":19},"01M757KKBT5Q1SVF8DMJBVF46M","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",[],[]]