[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M752G2TA57ASH8CESMPW7A9K":3,"skill-same:01M752G2TA57ASH8CESMPW7A9K":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":29,"commitSha":30,"skillDirectory":31,"forksCount":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":35,"ownerDescription":36,"updatedAt":37,"install":38,"resources":50},"01M752G2TA57ASH8CESMPW7A9K","x-create-jira-epic",null,"Create a Jira Epic from an existing local epic markdown file. Read the epic file, map fields to Jira, create the issue via MCP, and sync the Jira key back to the local file.","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-clickhouse\u002F.claude\u002Fskills\u002Fx-create-jira-epic\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: x-create-jira-epic\ndescription: \"Create a Jira Epic from an existing local epic markdown file. Read the epic file, map fields to Jira, create the issue via MCP, and sync the Jira key back to the local file.\"\nuser-invocable: true\nallowed-tools: Read, Write, Edit, Bash, Grep, Glob, AskUserQuestion\nargument-hint: \"[EPIC_FILE_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: Create Jira Epic\n\n## Purpose\n\nCreate a Jira Epic issue from an existing local `epic-XXXX.md` file. Parse the epic markdown, map fields to Jira issue attributes, create the Epic via MCP, and sync the returned Jira key back to the local file for bidirectional traceability.\n\n## Triggers\n\n- `\u002Fx-create-jira-epic \u003Cepic_file_path>` — create Jira Epic from the specified file\n- User says \"create epic in Jira\", \"sync epic to Jira\", or \"push epic to Jira\"\n- After running `\u002Fx-epic-create` or `\u002Fx-epic-decompose` without Jira integration\n\n## Parameters\n\n| Parameter | Type | Required | Default | Description |\n|-----------|------|----------|---------|-------------|\n| `EPIC_FILE_PATH` | Path | No | — | Path to the epic markdown file (prompted if omitted) |\n\n## Prerequisites\n\nRead the field mapping reference before creating issues:\n- `.claude\u002Fskills\u002Fx-create-jira-epic\u002Freferences\u002Fjira-field-mapping.md`\n\n## Workflow\n\n### Step 1 — Input and Parse\n\n\u003C!-- TELEMETRY: phase.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh start x-create-jira-epic Phase-1-Read-Markdown`\n\n1. Accept the epic file path as argument. If not provided, ask:\n   ```\n   question: \"Qual o caminho do arquivo do epico? (ex: ai\u002Fepics\u002Fepic-XXXX\u002Fepic-XXXX.md)\"\n   header: \"Epic File\"\n   ```\n2. Read the epic file completely\n3. Extract:\n   - **Title**: From `# Epico: \u003Ctitulo>` (line 1)\n   - **Local ID**: From the directory name (`epic-XXXX`)\n   - **Overview**: From Section 1 (Visao Geral) — all text after `**Chave Jira:**` line until Section 2\n   - **Status**: From the header `**Status:**` field\n   - **Existing Jira Key**: From `**Chave Jira:**` field\n\n### Step 2 — Pre-checks\n\n1. Verify `mcp__atlassian__createJiraIssue` is available. If not:\n   ```\n   ERROR: MCP tool mcp__atlassian__createJiraIssue not available.\n   Ensure the Atlassian MCP server is configured in .claude\u002Fsettings.json.\n   ```\n   Abort.\n\n2. Check existing Jira key. If `**Chave Jira:**` has a real value (not `\u003CCHAVE-JIRA>` and not `—`):\n   ```\n   question: \"Este epico ja tem chave Jira: {KEY}. O que deseja fazer?\"\n   header: \"Epico ja vinculado ao Jira\"\n   options:\n     - label: \"Criar novo epico no Jira\"\n       description: \"Ignorar a chave existente e criar um novo issue\"\n     - label: \"Pular — manter a chave existente\"\n       description: \"Nao criar no Jira, manter o vinculo atual\"\n   ```\n   If \"Pular\": exit with message \"Epico mantido com chave {KEY}.\"\n\n### Step 3 — Project Selection\n\n1. Call `mcp__atlassian__getAccessibleAtlassianResources` to discover available Atlassian sites\n2. Use the first available site's `id` as `cloudId`. If no sites returned:\n   ```\n   ERROR: No accessible Atlassian sites found. Check your Atlassian credentials.\n   ```\n   Abort.\n\n3. Call `mcp__atlassian__getVisibleJiraProjects` with the discovered `cloudId`\n4. Present the project list to the user:\n   ```\n   question: \"Selecione o projeto Jira para criar o epico:\"\n   header: \"Projeto Jira\"\n   options:\n     - label: \"{PROJECT_KEY} — my-spring-clickhouse\"\n       description: \"Project key: {PROJECT_KEY}\"\n     (one option per project)\n   ```\n5. Capture the selected `projectKey`\n\n\u003C!-- TELEMETRY: phase.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh end x-create-jira-epic Phase-1-Read-Markdown ok`\n\n### Step 4 — Create Epic in Jira\n\n\u003C!-- TELEMETRY: phase.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh start x-create-jira-epic Phase-2-MCP-Call`\n\nWrap the Jira MCP call with mcp-start \u002F mcp-end markers (story-0040-0008\n§3.2) so the `tool.call` event carries `tool=mcp__atlassian__createJiraIssue`\nand a measured `durationMs`:\n\n\u003C!-- TELEMETRY: tool.call mcp-start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh mcp-start x-create-jira-epic createJiraIssue`\n\nCall `mcp__atlassian__createJiraIssue` with:\n- `cloudId`: discovered cloudId\n- `projectKey`: selected project key\n- `issueTypeName`: \"Epic\"\n- `summary`: epic title (extracted from `# Epico: \u003Ctitulo>`)\n- `description`: Section 1 (Visao Geral) text content\n- `contentFormat`: \"markdown\"\n- `additional_fields`:\n  ```json\n  {\n    \"labels\": [\n      { \"name\": \"generated-by-ia-dev-env\" },\n      { \"name\": \"epic-XXXX\" }\n    ]\n  }\n  ```\n\nWhere `epic-XXXX` is the local epic ID (e.g., `epic-0012`).\n\n\u003C!-- TELEMETRY: tool.call mcp-end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh mcp-end x-create-jira-epic createJiraIssue ok`\n\n(On MCP failure, invoke the mcp-end marker with status `failed` instead of\n`ok` so the telemetry record reflects the real outcome — §5.3.)\n\n\u003C!-- TELEMETRY: phase.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh end x-create-jira-epic Phase-2-MCP-Call ok`\n\n### Step 5 — Sync Jira Key Back to Local File\n\n\u003C!-- TELEMETRY: phase.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh start x-create-jira-epic Phase-3-Sync-Back`\n\n1. Capture the returned Jira issue key (e.g., `PROJ-123`)\n2. Read the epic markdown file\n3. Replace the `**Chave Jira:**` value:\n   - If current value is `\u003CCHAVE-JIRA>`: replace with the actual key\n   - If current value is `—`: replace with the actual key\n   - If creating a new epic (user chose to ignore existing key): replace with the new key\n4. Write the updated file\n\n### Step 6 — Report\n\nOutput:\n```\nEpico criado no Jira: {JIRA_KEY}\nProjeto: {PROJECT_KEY}\nArquivo local atualizado: {EPIC_FILE_PATH}\nLabel de sync: epic-XXXX\n```\n\n\u003C!-- TELEMETRY: phase.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh end x-create-jira-epic Phase-3-Sync-Back ok`\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| MCP tool not available | Abort with clear message about MCP configuration |\n| No Atlassian sites found | Abort with credential check message |\n| Issue creation fails | Report the error, do NOT update the local file |\n| File write fails | Report error, mention Jira key was created but local file not updated |\n| Epic file not found | Abort with message: \"Epic file not found at {path}\" |\n| Epic file unparseable | Abort with message: \"Cannot parse epic file — verify format\" |\n\n## Integration Notes\n\n| Skill | Relationship | Context |\n|-------|-------------|---------|\n| x-epic-create | reads | Reads the epic file generated by this skill |\n| x-epic-decompose | called-by | Orchestrator may invoke this in Phase B |\n| x-create-jira-stories | calls | Creates Jira stories linked to the epic |\n\n## ID Synchronization Strategy\n\nBidirectional lookup is enabled by:\n- **Local to Jira**: The local ID (`epic-XXXX`) is stored as a Jira label\n- **Jira to Local**: The Jira key (e.g., `PROJ-123`) is stored in the `**Chave Jira:**` field\n- **JQL Lookup**: `labels = \"epic-XXXX\" AND labels = \"generated-by-ia-dev-env\"`\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: Create Jira Epic\n\n## Purpose\n\nCreate a Jira Epic issue from an existing local `epic-XXXX.md` file. Parse the epic markdown, map fields to Jira issue attributes, create the Epic via MCP, and sync the returned Jira key back to the local file for bidirectional traceability.\n\n## Triggers\n\n- `\u002Fx-create-jira-epic \u003Cepic_file_path>` — create Jira Epic from the specified file\n- User says \"create epic in Jira\", \"sync epic to Jira\", or \"push epic to Jira\"\n- After running `\u002Fx-epic-create` or `\u002Fx-epic-decompose` without Jira integration\n\n## Parameters\n\n| Parameter | Type | Required | Default | Description |\n|-----------|------|----------|---------|-------------|\n| `EPIC_FILE_PATH` | Path | No | — | Path to the epic markdown file (prompted if omitted) |\n\n## Prerequisites\n\nRead the field mapping reference before creating issues:\n- `.claude\u002Fskills\u002Fx-create-jira-epic\u002Freferences\u002Fjira-field-mapping.md`\n\n## Workflow\n\n### Step 1 — Input and Parse\n\n\u003C!-- TELEMETRY: phase.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh start x-create-jira-epic Phase-1-Read-Markdown`\n\n1. Accept the epic file path as argument. If not provided, ask:\n   ```\n   question: \"Qual o caminho do arquivo do epico? (ex: ai\u002Fepics\u002Fepic-XXXX\u002Fepic-XXXX.md)\"\n   header: \"Epic File\"\n   ```\n2. Read the epic file completely\n3. Extract:\n   - **Title**: From `# Epico: \u003Ctitulo>` (line 1)\n   - **Local ID**: From the directory name (`epic-XXXX`)\n   - **Overview**: From Section 1 (Visao Geral) — all text after `**Chave Jira:**` line until Section 2\n   - **Status**: From the header `**Status:**` field\n   - **Existing Jira Key**: From `**Chave Jira:**` field\n\n### Step 2 — Pre-checks\n\n1. Verify `mcp__atlassian__createJiraIssue` is available. If not:\n   ```\n   ERROR: MCP tool mcp__atlassian__createJiraIssue not available.\n   Ensure the Atlassian MCP server is configured in .claude\u002Fsettings.json.\n   ```\n   Abort.\n\n2. Check existing Jira key. If `**Chave Jira:**` has a real value (not `\u003CCHAVE-JIRA>` and not `—`):\n   ```\n   question: \"Este epico ja tem chave Jira: {KEY}. O que deseja fazer?\"\n   header: \"Epico ja vinculado ao Jira\"\n   options:\n     - label: \"Criar novo epico no Jira\"\n       description: \"Ignorar a chave existente e criar um novo issue\"\n     - label: \"Pular — manter a chave existente\"\n       description: \"Nao criar no Jira, manter o vinculo atual\"\n   ```\n   If \"Pular\": exit with message \"Epico mantido com chave {KEY}.\"\n\n### Step 3 — Project Selection\n\n1. Call `mcp__atlassian__getAccessibleAtlassianResources` to discover available Atlassian sites\n2. Use the first available site's `id` as `cloudId`. If no sites returned:\n   ```\n   ERROR: No accessible Atlassian sites found. Check your Atlassian credentials.\n   ```\n   Abort.\n\n3. Call `mcp__atlassian__getVisibleJiraProjects` with the discovered `cloudId`\n4. Present the project list to the user:\n   ```\n   question: \"Selecione o projeto Jira para criar o epico:\"\n   header: \"Projeto Jira\"\n   options:\n     - label: \"{PROJECT_KEY} — my-spring-clickhouse\"\n       description: \"Project key: {PROJECT_KEY}\"\n     (one option per project)\n   ```\n5. Capture the selected `projectKey`\n\n\u003C!-- TELEMETRY: phase.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh end x-create-jira-epic Phase-1-Read-Markdown ok`\n\n### Step 4 — Create Epic in Jira\n\n\u003C!-- TELEMETRY: phase.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh start x-create-jira-epic Phase-2-MCP-Call`\n\nWrap the Jira MCP call with mcp-start \u002F mcp-end markers (story-0040-0008\n§3.2) so the `tool.call` event carries `tool=mcp__atlassian__createJiraIssue`\nand a measured `durationMs`:\n\n\u003C!-- TELEMETRY: tool.call mcp-start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh mcp-start x-create-jira-epic createJiraIssue`\n\nCall `mcp__atlassian__createJiraIssue` with:\n- `cloudId`: discovered cloudId\n- `projectKey`: selected project key\n- `issueTypeName`: \"Epic\"\n- `summary`: epic title (extracted from `# Epico: \u003Ctitulo>`)\n- `description`: Section 1 (Visao Geral) text content\n- `contentFormat`: \"markdown\"\n- `additional_fields`:\n  ```json\n  {\n    \"labels\": [\n      { \"name\": \"generated-by-ia-dev-env\" },\n      { \"name\": \"epic-XXXX\" }\n    ]\n  }\n  ```\n\nWhere `epic-XXXX` is the local epic ID (e.g., `epic-0012`).\n\n\u003C!-- TELEMETRY: tool.call mcp-end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh mcp-end x-create-jira-epic createJiraIssue ok`\n\n(On MCP failure, invoke the mcp-end marker with status `failed` instead of\n`ok` so the telemetry record reflects the real outcome — §5.3.)\n\n\u003C!-- TELEMETRY: phase.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh end x-create-jira-epic Phase-2-MCP-Call ok`\n\n### Step 5 — Sync Jira Key Back to Local File\n\n\u003C!-- TELEMETRY: phase.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh start x-create-jira-epic Phase-3-Sync-Back`\n\n1. Capture the returned Jira issue key (e.g., `PROJ-123`)\n2. Read the epic markdown file\n3. Replace the `**Chave Jira:**` value:\n   - If current value is `\u003CCHAVE-JIRA>`: replace with the actual key\n   - If current value is `—`: replace with the actual key\n   - If creating a new epic (user chose to ignore existing key): replace with the new key\n4. Write the updated file\n\n### Step 6 — Report\n\nOutput:\n```\nEpico criado no Jira: {JIRA_KEY}\nProjeto: {PROJECT_KEY}\nArquivo local atualizado: {EPIC_FILE_PATH}\nLabel de sync: epic-XXXX\n```\n\n\u003C!-- TELEMETRY: phase.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh end x-create-jira-epic Phase-3-Sync-Back ok`\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| MCP tool not available | Abort with clear message about MCP configuration |\n| No Atlassian sites found | Abort with credential check message |\n| Issue creation fails | Report the error, do NOT update the local file |\n| File write fails | Report error, mention Jira key was created but local file not updated |\n| Epic file not found | Abort with message: \"Epic file not found at {path}\" |\n| Epic file unparseable | Abort with message: \"Cannot parse epic file — verify format\" |\n\n## Integration Notes\n\n| Skill | Relationship | Context |\n|-------|-------------|---------|\n| x-epic-create | reads | Reads the epic file generated by this skill |\n| x-epic-decompose | called-by | Orchestrator may invoke this in Phase B |\n| x-create-jira-stories | calls | Creates Jira stories linked to the epic |\n\n## ID Synchronization Strategy\n\nBidirectional lookup is enabled by:\n- **Local to Jira**: The local ID (`epic-XXXX`) is stored as a Jira label\n- **Jira to Local**: The Jira key (e.g., `PROJ-123`) is stored in the `**Chave Jira:**` field\n- **JQL Lookup**: `labels = \"epic-XXXX\" AND labels = \"generated-by-ia-dev-env\"`\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, AskUserQuestion","[EPIC_FILE_PATH]","light",true,[],"main","952a630c6f38d193a349d86fa18db1de8843e837","src\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring-clickhouse\u002F.claude\u002Fskills\u002Fx-create-jira-epic",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-create-jira-epic",{"tool":44,"command":45},"bunx","bunx skills add review-bench\u002Federcnj_ia-dev-environment --skill x-create-jira-epic",{"tool":47,"command":48},"pnpm","pnpm dlx skills add review-bench\u002Federcnj_ia-dev-environment --skill x-create-jira-epic","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring-clickhouse\u002F.claude\u002Fskills\u002Fx-create-jira-epic\u002FSKILL.md",[51,57],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"README.md","REFERENCE","参考文档",1665,"https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring-clickhouse\u002F.claude\u002Fskills\u002Fx-create-jira-epic\u002FREADME.md",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fjira-field-mapping.md",4888,"https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring-clickhouse\u002F.claude\u002Fskills\u002Fx-create-jira-epic\u002Freferences\u002Fjira-field-mapping.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",[],[]]