[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M752CTEX47HC2V5K2Z2QH404":3,"skill-same:01M752CTEX47HC2V5K2Z2QH404":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},"01M752CTEX47HC2V5K2Z2QH404","x-run-perf-tests",null,"Runs performance tests to validate latency SLAs, throughput targets, and resource stability under load. Supports baseline, normal, peak, and sustained scenarios.","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-quarkus\u002F.claude\u002Fskills\u002Fx-run-perf-tests\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: x-run-perf-tests\ndescription: \"Runs performance tests to validate latency SLAs, throughput targets, and resource stability under load. Supports baseline, normal, peak, and sustained scenarios.\"\nuser-invocable: true\nallowed-tools: Read, Write, Edit, Bash, Grep, Glob\nargument-hint: \"[scenario: baseline|normal|peak|sustained|all] [--save-baseline] [--compare-baseline]\"\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: Performance \u002F Load Tests\n\n## Purpose\n\nRun or implement performance tests to validate the application meets latency SLAs, throughput targets, and resource stability requirements under various load conditions. Measure p50\u002Fp95\u002Fp99 latency, transactions per second (TPS), error rates, and memory stability.\n\n## Activation Condition\n\nInclude this skill for projects with performance testing requirements.\n\n## Triggers\n\n- `\u002Fx-run-perf-tests baseline` -- single user, sequential requests\n- `\u002Fx-run-perf-tests normal` -- expected daily load\n- `\u002Fx-run-perf-tests peak` -- maximum expected concurrent load\n- `\u002Fx-run-perf-tests sustained` -- constant load over extended period (30 min+)\n- `\u002Fx-run-perf-tests all` -- run all scenarios\n- `\u002Fx-run-perf-tests normal --save-baseline` -- save results as baseline\n- `\u002Fx-run-perf-tests normal --compare-baseline` -- compare against stored baseline\n\n## Parameters\n\n| Parameter | Type | Required | Default | Description |\n|-----------|------|----------|---------|-------------|\n| `scenario` | String | No | `all` | Scenario: `baseline`, `normal`, `peak`, `sustained`, `all` |\n| `--save-baseline` | Flag | No | false | Save results to `results\u002Fperformance\u002Fbaseline.json` |\n| `--compare-baseline` | Flag | No | false | Compare results against stored baseline |\n\n## Prerequisites\n\n- Performance test framework configured (e.g., Gatling, k6, JMeter, Locust)\n- Application deployed and accessible (local or remote)\n- Test data feeders\u002Fgenerators available\n- Sufficient system resources for load generation\n\n## Workflow\n\n### Step 1 — Verify Prerequisites\n\n- Performance test framework installed and configured\n- Application running and healthy (check health endpoint)\n- Test data generators available\n\n### Step 2 — Select and Run Scenario\n\n**Baseline** (single user warmup):\n- 1 connection\u002Fuser, 100 sequential requests\n- Validates correctness and establishes latency baseline\n- Target: p99 \u003C 100ms, 0% errors\n\n**Normal Load** (daily traffic):\n- Ramp up to expected concurrent users over 30s\n- Sustain for 2-5 minutes\n- Target: p95 \u003C 150ms, TPS > configured threshold, errors \u003C 0.1%\n\n**Peak Load** (traffic spike):\n- Rapid ramp to maximum concurrent users\n- Sustain for 1-2 minutes\n- Target: p99 \u003C 500ms, errors \u003C 0.5%, no crashes\n\n**Sustained Load** (stability \u002F memory leak detection):\n- Constant moderate load for 30+ minutes\n- Monitor memory growth over time\n- Target: p99 stable (no drift > 20%), memory growth \u003C 10%, errors \u003C 0.1%\n\n### Step 3 — Collect Metrics\n\n- Latency percentiles: p50, p75, p95, p99\n- Throughput: requests\u002Ftransactions per second\n- Error rate: percentage of failed requests\n- Resource usage: memory (RSS), CPU utilization\n- Connection metrics: reuse rate, failures\n\n### Step 4 — Regression Detection (if --compare-baseline)\n\nCompare current test results against stored baseline:\n\n| Metric | Regression Condition | Severity |\n|--------|---------------------|----------|\n| p99 latency | Current > baseline * 1.2 (20% degradation) | FAIL |\n| p95 latency | Current > baseline * 1.15 (15% degradation) | WARN |\n| throughput (RPS) | Current \u003C baseline * 0.85 (15% drop) | FAIL |\n| error rate | Current > baseline + 0.5% (absolute) | FAIL |\n\n### Step 5 — Generate Report\n\nSummary table with all metrics vs SLA targets:\n- PASS\u002FFAIL per SLA criterion\n- Latency distribution chart (if framework supports)\n- Recommendations for failures\n\n## SLA Targets (Defaults)\n\n| Metric | Baseline | Normal | Peak | Sustained |\n|--------|----------|--------|------|-----------|\n| p50 latency | \u003C 10ms | \u003C 20ms | \u003C 50ms | \u003C 25ms |\n| p95 latency | \u003C 50ms | \u003C 150ms | \u003C 300ms | \u003C 150ms |\n| p99 latency | \u003C 100ms | \u003C 300ms | \u003C 500ms | \u003C 200ms |\n| Error rate | 0% | \u003C 0.1% | \u003C 0.5% | \u003C 0.1% |\n| Memory growth | N\u002FA | N\u002FA | N\u002FA | \u003C 10% |\n\n## Data Generation\n\nPerformance tests require realistic data generators:\n- Varied request payloads to avoid cache effects\n- Unique identifiers per request to prevent conflicts\n- Realistic distribution of operation types (e.g., 70% reads, 30% writes)\n- Randomized think time between requests for realistic pacing\n\n## Baseline Management\n\n### Save Baseline\n\nWhen `--save-baseline` is specified:\n1. Execute the selected scenario\n2. Collect all metrics\n3. Write results to `results\u002Fperformance\u002Fbaseline.json`\n4. Overwrite existing baseline (with backup to `baseline.prev.json`)\n\n### baseline.json Structure\n\n```json\n{\n  \"version\": \"1.0\",\n  \"timestamp\": \"ISO-8601\",\n  \"scenario\": \"normal\",\n  \"metrics\": {\n    \"endpoint_or_operation\": {\n      \"p50_ms\": 10,\n      \"p95_ms\": 45,\n      \"p99_ms\": 95,\n      \"throughput_rps\": 1200,\n      \"error_rate_pct\": 0.1\n    }\n  }\n}\n```\n\n## Threshold Validation\n\n| Metric | Absolute Threshold | Relative Threshold (vs baseline) |\n|--------|-------------------|--------------------------------|\n| p99 latency | Scenario SLA (see table above) | +20% vs baseline |\n| p95 latency | Scenario SLA (see table above) | +15% vs baseline |\n| throughput | Scenario minimum TPS | -15% vs baseline |\n| error rate | Scenario max error rate | +0.5% absolute vs baseline |\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| Performance framework not installed | Report missing tool with install instructions |\n| Application health check fails | Abort with health check failure details |\n| Baseline file not found for comparison | Warn and continue without regression detection |\n| SLA threshold exceeded | Report FAIL with metric details and recommendations |\n\n## Integration Notes\n\n| Skill | Relationship | Context |\n|-------|-------------|---------|\n| x-profile-performance | calls | Use `\u002Fx-profile-performance cpu` for latency regressions, `memory` for throughput regressions |\n\n## Review Checklist\n\n- [ ] Baseline scenario establishes latency floor\n- [ ] Normal load matches expected daily traffic pattern\n- [ ] Peak load tests maximum concurrent capacity\n- [ ] Sustained load runs 30+ minutes for stability validation\n- [ ] Latency assertions defined per scenario (p50, p95, p99)\n- [ ] Error rate thresholds enforced\n- [ ] Memory growth monitored during sustained test\n- [ ] Connections are reused (persistent, not per-request)\n- [ ] Test data is varied and realistic\n- [ ] Results report generated with metrics vs SLA comparison\n- [ ] Rate limiting adjusted for test (not interfering with load)\n- [ ] Baseline saved for regression detection (if first run)\n- [ ] Regression comparison executed against stored baseline\n- [ ] Threshold validation passed for p99 and throughput\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: Performance \u002F Load Tests\n\n## Purpose\n\nRun or implement performance tests to validate the application meets latency SLAs, throughput targets, and resource stability requirements under various load conditions. Measure p50\u002Fp95\u002Fp99 latency, transactions per second (TPS), error rates, and memory stability.\n\n## Activation Condition\n\nInclude this skill for projects with performance testing requirements.\n\n## Triggers\n\n- `\u002Fx-run-perf-tests baseline` -- single user, sequential requests\n- `\u002Fx-run-perf-tests normal` -- expected daily load\n- `\u002Fx-run-perf-tests peak` -- maximum expected concurrent load\n- `\u002Fx-run-perf-tests sustained` -- constant load over extended period (30 min+)\n- `\u002Fx-run-perf-tests all` -- run all scenarios\n- `\u002Fx-run-perf-tests normal --save-baseline` -- save results as baseline\n- `\u002Fx-run-perf-tests normal --compare-baseline` -- compare against stored baseline\n\n## Parameters\n\n| Parameter | Type | Required | Default | Description |\n|-----------|------|----------|---------|-------------|\n| `scenario` | String | No | `all` | Scenario: `baseline`, `normal`, `peak`, `sustained`, `all` |\n| `--save-baseline` | Flag | No | false | Save results to `results\u002Fperformance\u002Fbaseline.json` |\n| `--compare-baseline` | Flag | No | false | Compare results against stored baseline |\n\n## Prerequisites\n\n- Performance test framework configured (e.g., Gatling, k6, JMeter, Locust)\n- Application deployed and accessible (local or remote)\n- Test data feeders\u002Fgenerators available\n- Sufficient system resources for load generation\n\n## Workflow\n\n### Step 1 — Verify Prerequisites\n\n- Performance test framework installed and configured\n- Application running and healthy (check health endpoint)\n- Test data generators available\n\n### Step 2 — Select and Run Scenario\n\n**Baseline** (single user warmup):\n- 1 connection\u002Fuser, 100 sequential requests\n- Validates correctness and establishes latency baseline\n- Target: p99 \u003C 100ms, 0% errors\n\n**Normal Load** (daily traffic):\n- Ramp up to expected concurrent users over 30s\n- Sustain for 2-5 minutes\n- Target: p95 \u003C 150ms, TPS > configured threshold, errors \u003C 0.1%\n\n**Peak Load** (traffic spike):\n- Rapid ramp to maximum concurrent users\n- Sustain for 1-2 minutes\n- Target: p99 \u003C 500ms, errors \u003C 0.5%, no crashes\n\n**Sustained Load** (stability \u002F memory leak detection):\n- Constant moderate load for 30+ minutes\n- Monitor memory growth over time\n- Target: p99 stable (no drift > 20%), memory growth \u003C 10%, errors \u003C 0.1%\n\n### Step 3 — Collect Metrics\n\n- Latency percentiles: p50, p75, p95, p99\n- Throughput: requests\u002Ftransactions per second\n- Error rate: percentage of failed requests\n- Resource usage: memory (RSS), CPU utilization\n- Connection metrics: reuse rate, failures\n\n### Step 4 — Regression Detection (if --compare-baseline)\n\nCompare current test results against stored baseline:\n\n| Metric | Regression Condition | Severity |\n|--------|---------------------|----------|\n| p99 latency | Current > baseline * 1.2 (20% degradation) | FAIL |\n| p95 latency | Current > baseline * 1.15 (15% degradation) | WARN |\n| throughput (RPS) | Current \u003C baseline * 0.85 (15% drop) | FAIL |\n| error rate | Current > baseline + 0.5% (absolute) | FAIL |\n\n### Step 5 — Generate Report\n\nSummary table with all metrics vs SLA targets:\n- PASS\u002FFAIL per SLA criterion\n- Latency distribution chart (if framework supports)\n- Recommendations for failures\n\n## SLA Targets (Defaults)\n\n| Metric | Baseline | Normal | Peak | Sustained |\n|--------|----------|--------|------|-----------|\n| p50 latency | \u003C 10ms | \u003C 20ms | \u003C 50ms | \u003C 25ms |\n| p95 latency | \u003C 50ms | \u003C 150ms | \u003C 300ms | \u003C 150ms |\n| p99 latency | \u003C 100ms | \u003C 300ms | \u003C 500ms | \u003C 200ms |\n| Error rate | 0% | \u003C 0.1% | \u003C 0.5% | \u003C 0.1% |\n| Memory growth | N\u002FA | N\u002FA | N\u002FA | \u003C 10% |\n\n## Data Generation\n\nPerformance tests require realistic data generators:\n- Varied request payloads to avoid cache effects\n- Unique identifiers per request to prevent conflicts\n- Realistic distribution of operation types (e.g., 70% reads, 30% writes)\n- Randomized think time between requests for realistic pacing\n\n## Baseline Management\n\n### Save Baseline\n\nWhen `--save-baseline` is specified:\n1. Execute the selected scenario\n2. Collect all metrics\n3. Write results to `results\u002Fperformance\u002Fbaseline.json`\n4. Overwrite existing baseline (with backup to `baseline.prev.json`)\n\n### baseline.json Structure\n\n```json\n{\n  \"version\": \"1.0\",\n  \"timestamp\": \"ISO-8601\",\n  \"scenario\": \"normal\",\n  \"metrics\": {\n    \"endpoint_or_operation\": {\n      \"p50_ms\": 10,\n      \"p95_ms\": 45,\n      \"p99_ms\": 95,\n      \"throughput_rps\": 1200,\n      \"error_rate_pct\": 0.1\n    }\n  }\n}\n```\n\n## Threshold Validation\n\n| Metric | Absolute Threshold | Relative Threshold (vs baseline) |\n|--------|-------------------|--------------------------------|\n| p99 latency | Scenario SLA (see table above) | +20% vs baseline |\n| p95 latency | Scenario SLA (see table above) | +15% vs baseline |\n| throughput | Scenario minimum TPS | -15% vs baseline |\n| error rate | Scenario max error rate | +0.5% absolute vs baseline |\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| Performance framework not installed | Report missing tool with install instructions |\n| Application health check fails | Abort with health check failure details |\n| Baseline file not found for comparison | Warn and continue without regression detection |\n| SLA threshold exceeded | Report FAIL with metric details and recommendations |\n\n## Integration Notes\n\n| Skill | Relationship | Context |\n|-------|-------------|---------|\n| x-profile-performance | calls | Use `\u002Fx-profile-performance cpu` for latency regressions, `memory` for throughput regressions |\n\n## Review Checklist\n\n- [ ] Baseline scenario establishes latency floor\n- [ ] Normal load matches expected daily traffic pattern\n- [ ] Peak load tests maximum concurrent capacity\n- [ ] Sustained load runs 30+ minutes for stability validation\n- [ ] Latency assertions defined per scenario (p50, p95, p99)\n- [ ] Error rate thresholds enforced\n- [ ] Memory growth monitored during sustained test\n- [ ] Connections are reused (persistent, not per-request)\n- [ ] Test data is varied and realistic\n- [ ] Results report generated with metrics vs SLA comparison\n- [ ] Rate limiting adjusted for test (not interfering with load)\n- [ ] Baseline saved for regression detection (if first run)\n- [ ] Regression comparison executed against stored baseline\n- [ ] Threshold validation passed for p99 and throughput\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","[scenario: baseline|normal|peak|sustained|all] [--save-baseline] [--compare-baseline]","light",true,[],"main","952a630c6f38d193a349d86fa18db1de8843e837","src\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-quarkus\u002F.claude\u002Fskills\u002Fx-run-perf-tests",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-run-perf-tests",{"tool":44,"command":45},"bunx","bunx skills add review-bench\u002Federcnj_ia-dev-environment --skill x-run-perf-tests",{"tool":47,"command":48},"pnpm","pnpm dlx skills add review-bench\u002Federcnj_ia-dev-environment --skill x-run-perf-tests","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-quarkus\u002F.claude\u002Fskills\u002Fx-run-perf-tests\u002FSKILL.md",[51],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"README.md","REFERENCE","参考文档",1459,"https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-quarkus\u002F.claude\u002Fskills\u002Fx-run-perf-tests\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":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"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",[],[]]