[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H44ATZRBZ5WB96F8PCZKB5":3,"skill-same:01M6H44ATZRBZ5WB96F8PCZKB5":76},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":56,"repositoryHtmlUrl":57,"repositoryHomepageUrl":6,"ownerHtmlUrl":58,"ownerBlogUrl":59,"ownerDescription":60,"updatedAt":61,"install":62,"resources":75},"01M6H44ATZRBZ5WB96F8PCZKB5","dx-plan-resolve",null,"Resolve risks flagged by \u002Fdx-plan-validate — research the codebase and update implement.md steps with concrete fixes. Use for 'resolve plan issues', 'fix plan risks'.","easingthemes\u002Fdx-aem-flow","easingthemes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F2750284?v=4","01M6H3XYGJY8QCX9ES36P2WF4H","Dragan Filipović","01M6H3XYMN1XVSGKN7N79SW3RH",7,"MIT","https:\u002F\u002Fgithub.com\u002Feasingthemes\u002Fdx-aem-flow\u002Fblob\u002Fmain\u002Fplugins\u002Fdx-core\u002Fskills\u002Fdx-plan-resolve\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"dx plan resolve","plan","dx","validate","edit","write","codebase","read","update","research","work","id","with","implement","use","issues","fix","search","for","fixes","2026-11-10 10:12:30",false,"---\nname: dx-plan-resolve\ndescription: \"Resolve risks flagged by \u002Fdx-plan-validate — research the codebase and update implement.md steps with concrete fixes. Use for 'resolve plan issues', 'fix plan risks'.\"\nargument-hint: \"[Work Item ID or slug (optional — uses most recent if omitted)]\"\ncontext: fork\nallowed-tools: [\"read\", \"edit\", \"search\", \"write\", \"agent\"]\n---\n\n**Isolation check.** This skill is meant to run in its own context (`context: fork`). If you can see the user's messages from before this skill was invoked, you are running inline (Copilot CLI ignores `context: fork`): do not run the steps below yourself. Start one subagent with your task\u002Fsubagent tool, give it only this instruction — \"Invoke the dx-core:dx-plan-resolve skill with these arguments: \u003Cthe arguments you were given, or none>. Run it fully and reply with its final report only.\" — then show the user that report and stop. If you cannot see earlier user messages, or your only earlier message is that instruction to invoke dx-core:dx-plan-resolve (you are a fork or that subagent), continue below.\n\nYou resolve risks and issues found during plan validation by researching the codebase for concrete solutions, then updating `implement.md` with specific fix instructions.\n\nUse ultrathink for this skill — solving risks requires deep reasoning about patterns and codebase specifics.\n\n## Output\n\nYou run in a forked context. Before emitting any chat output, determine whether you were invoked by the orchestrator (`dx-agent-all`) or standalone — see `plugins\u002Fdx-core\u002Fshared\u002Forchestration-check.md`:\n\n```bash\nORCHESTRATED=0\nFLAG=\".ai\u002Frun-context\u002Forchestrating.flag\"\nif [ -f \"$FLAG\" ]; then\n  AGE=$(( $(date +%s) - $(date -r \"$FLAG\" +%s) ))\n  [ \"$AGE\" -lt 7200 ] && ORCHESTRATED=1\nfi\n```\n\n- **If `$ORCHESTRATED == 1`** (orchestrator path): write the full report to `$SPEC_DIR\u002Fresolve-report.md` and emit ONLY the `## Return` block to chat.\n- **If `$ORCHESTRATED == 0`** (standalone path): write the same report AND emit the human-friendly summary marked `\u003C!-- standalone-only -->` below, followed by the `## Return` block at the very end.\n\nPer-phase progress lines during the run are allowed in both paths.\n\nThis skill writes its full report (per-issue resolution actions and updated `implement.md` diff summary) to `$SPEC_DIR\u002Fresolve-report.md`.\n\n## 1. Locate the Spec Directory\n\n```bash\nSPEC_DIR=$(bash .ai\u002Flib\u002Fdx-common.sh find-spec-dir $ARGUMENTS)\n```\n\nRead from `$SPEC_DIR`:\n- `implement.md` (required)\n- `research.md` (required — for codebase context)\n- `explain.md` (for requirement context)\n\n## 2. Identify Issues to Resolve\n\nScan `implement.md` for:\n1. **Risks section** — anything listed under `## Risks`\n2. **Blocked steps** — steps with `**Status:** blocked`\n3. **Vague instructions** — steps that say \"may need\", \"might require\", \"consider\", \"TBD\" without a concrete solution\n\nCollect each issue as a task to resolve.\n\nIf no issues found → print `No risks or issues to resolve — plan is ready.` and STOP.\n\n## 3. Research Solutions\n\nFor each issue, search the codebase for how the project already solves similar problems.\n\nIf `.github\u002Finstructions\u002F` (or `.ai\u002Finstructions\u002F`) exists, read instruction files relevant to the issue's file types — these provide detailed framework patterns and code examples.\n\n**Example: \"Dynamic show\u002Fhide scoping inside nested repeatable fields\"**\n1. Search for existing repeatable fields that use show\u002Fhide → `Grep` for the show\u002Fhide pattern in config files\n2. Find how they handle scoping → read the matching config and any companion JS\n3. Identify the concrete pattern (scoped CSS classes, row-targeted selectors, etc.)\n4. Formulate a specific solution with exact code\u002Fconfig to add\n\n**General approach:**\n- Search for the pattern or keyword in the existing codebase\n- Find 1-2 working examples of the same technique\n- Extract the concrete implementation details (class names, config structure, selectors, etc.)\n- Formulate a specific fix, not a generic recommendation\n\n## 4. Update implement.md\n\nFor each resolved issue:\n\n**If the fix belongs in an existing step** — append the fix details to that step's `**What:**` section:\n```markdown\n**What:**\n\u003Cexisting instructions>\n- **Risk mitigation:** Use unique scoped class `cmp-component__toggle--step{N}` on the\n  checkbox field (see `card\u002Fconfig.xml:42` for the same pattern). This scopes\n  the show\u002Fhide listener to the correct repeatable row.\n```\n\n**If the fix needs a new step** — insert a step in the correct dependency position:\n```markdown\n### Step N: \u003CDescriptive title>\n**Status:** pending\n**Files:** `path\u002Fto\u002Ffile`, `path\u002Fto\u002Fother-if-needed`\n**What:**\n- \u003Cconcrete instructions with file:line references>\n**Why:** Mitigates risk — \u003Cone sentence explaining the issue>\n**Test:** \u003Cspecific verification approach>\n```\n\n**Update the Risks section** — replace vague risk with resolution:\n```markdown\n## Risks\n- ~~\u003Coriginal risk description>~~ → **Resolved:** \u003Cone-line solution> (Step N)\n```\n\n## 5. Write Resolve Report\n\n**Write** the following table and summary to `$SPEC_DIR\u002Fresolve-report.md`. Do not print to chat.\n\n```markdown\n## Plan Risks Resolved\n\n| # | Risk\u002FIssue | Resolution | Step Updated |\n|---|-----------|------------|--------------|\n| 1 | \u003Crisk description> | \u003Cone-line solution> | Step N |\n| 2 | \u003Crisk description> | \u003Cone-line solution> | New Step M |\n\n**Issues resolved:** \u003Ccount>\n**Steps modified:** \u003Ccount>\n**Steps added:** \u003Ccount>\n```\n\n## Examples\n\n1. `\u002Fdx-plan-resolve 2416553` — Reads implement.md risks (\"Dynamic show\u002Fhide scoping in nested repeatable fields\"), searches the codebase for existing repeatable field patterns, finds a working example in `card\u002Fconfig.xml`, and updates Step 4 with a concrete fix using scoped CSS classes.\n\n2. `\u002Fdx-plan-resolve` (no argument) — Uses the most recent spec directory. Finds 2 risks and 1 vague step. Resolves all by adding specific file:line references and inserting a new Step 3b for risk mitigation. Updates the Risks section with strikethrough originals and resolution notes.\n\n3. `\u002Fdx-plan-resolve 2416553` (no issues) — Reads implement.md, finds no risks, blocked steps, or vague instructions. Prints \"No risks or issues to resolve — plan is ready.\" and stops.\n\n## Troubleshooting\n\n- **\"No risks or issues to resolve\"**\n  **Cause:** The plan has no Risks section, no blocked steps, and no vague instructions.\n  **Fix:** This is good — the plan is ready for execution. Run `\u002Fdx-step-all` to proceed.\n\n- **Resolution references a file that doesn't exist**\n  **Cause:** The codebase search found a pattern in a file that was since moved or deleted.\n  **Fix:** Run `\u002Fdx-plan-validate` after resolving to verify file existence. Fix any invalid references manually in implement.md.\n\n- **Step numbering is broken after inserting new steps**\n  **Cause:** A new step was inserted but cross-references to step numbers weren't updated.\n  **Fix:** Re-run `\u002Fdx-plan-validate` — it checks dependency order and will flag any broken cross-references.\n\n## Rules\n\n- **Research before solving** — don't guess at solutions. Find working examples in the codebase first.\n- **Concrete fixes only** — every solution must include specific file paths, class names, or code snippets. \"Consider using unique selectors\" is not a fix. \"`class='cmp-component__toggle--step2'`\" is a fix.\n- **Minimal plan changes** — prefer adding to existing steps over creating new ones. Only add a new step if the fix is substantial enough to warrant separate execution.\n- **Preserve step numbering** — when inserting steps, renumber correctly and update any cross-references.\n- **Don't execute** — update the plan only. Execution happens in step-* skills.\n- **One pass** — resolve what you can, report what you can't. Don't loop.\n\n## Present Summary (standalone path only)\n\n\u003C!-- standalone-only — emit only when $ORCHESTRATED == 0 -->\n\nWhen running standalone, emit the resolve summary to chat:\n\n```markdown\n## Plan Risks Resolved\n\n| # | Risk\u002FIssue | Resolution | Step Updated |\n|---|-----------|------------|--------------|\n| 1 | \u003Crisk description> | \u003Cone-line solution> | Step N |\n| 2 | \u003Crisk description> | \u003Cone-line solution> | New Step M |\n\n**Issues resolved:** \u003Ccount>\n**Steps modified:** \u003Ccount>\n**Steps added:** \u003Ccount>\n\n### Next step:\n- `\u002Fdx-plan-validate` — re-validate the updated plan\n```\n\nWhen orchestrated (`$ORCHESTRATED == 1`), skip this section entirely and emit only the `## Return` block.\n\n## Return\n\nThis skill runs in a forked context. It MUST end with a `## Return` block per `plugins\u002Fdx-core\u002Fshared\u002Fskill-return-contract.md`.\n\nExamples:\n\n```markdown\n## Return\nverdict: pass\nsummary: Resolved 2 risks; updated implement.md (Step 3 split into 3a\u002F3b for clearer commit boundary).\nartifacts:\n  - .ai\u002Fspecs\u002F2490722-microsite\u002Fresolve-report.md\n  - .ai\u002Fspecs\u002F2490722-microsite\u002Fimplement.md\nnext_action: re-run \u002Fdx-plan-validate\n```\n","**Isolation check.** This skill is meant to run in its own context (`context: fork`). If you can see the user's messages from before this skill was invoked, you are running inline (Copilot CLI ignores `context: fork`): do not run the steps below yourself. Start one subagent with your task\u002Fsubagent tool, give it only this instruction — \"Invoke the dx-core:dx-plan-resolve skill with these arguments: \u003Cthe arguments you were given, or none>. Run it fully and reply with its final report only.\" — then show the user that report and stop. If you cannot see earlier user messages, or your only earlier message is that instruction to invoke dx-core:dx-plan-resolve (you are a fork or that subagent), continue below.\n\nYou resolve risks and issues found during plan validation by researching the codebase for concrete solutions, then updating `implement.md` with specific fix instructions.\n\nUse ultrathink for this skill — solving risks requires deep reasoning about patterns and codebase specifics.\n\n## Output\n\nYou run in a forked context. Before emitting any chat output, determine whether you were invoked by the orchestrator (`dx-agent-all`) or standalone — see `plugins\u002Fdx-core\u002Fshared\u002Forchestration-check.md`:\n\n```bash\nORCHESTRATED=0\nFLAG=\".ai\u002Frun-context\u002Forchestrating.flag\"\nif [ -f \"$FLAG\" ]; then\n  AGE=$(( $(date +%s) - $(date -r \"$FLAG\" +%s) ))\n  [ \"$AGE\" -lt 7200 ] && ORCHESTRATED=1\nfi\n```\n\n- **If `$ORCHESTRATED == 1`** (orchestrator path): write the full report to `$SPEC_DIR\u002Fresolve-report.md` and emit ONLY the `## Return` block to chat.\n- **If `$ORCHESTRATED == 0`** (standalone path): write the same report AND emit the human-friendly summary marked `\u003C!-- standalone-only -->` below, followed by the `## Return` block at the very end.\n\nPer-phase progress lines during the run are allowed in both paths.\n\nThis skill writes its full report (per-issue resolution actions and updated `implement.md` diff summary) to `$SPEC_DIR\u002Fresolve-report.md`.\n\n## 1. Locate the Spec Directory\n\n```bash\nSPEC_DIR=$(bash .ai\u002Flib\u002Fdx-common.sh find-spec-dir $ARGUMENTS)\n```\n\nRead from `$SPEC_DIR`:\n- `implement.md` (required)\n- `research.md` (required — for codebase context)\n- `explain.md` (for requirement context)\n\n## 2. Identify Issues to Resolve\n\nScan `implement.md` for:\n1. **Risks section** — anything listed under `## Risks`\n2. **Blocked steps** — steps with `**Status:** blocked`\n3. **Vague instructions** — steps that say \"may need\", \"might require\", \"consider\", \"TBD\" without a concrete solution\n\nCollect each issue as a task to resolve.\n\nIf no issues found → print `No risks or issues to resolve — plan is ready.` and STOP.\n\n## 3. Research Solutions\n\nFor each issue, search the codebase for how the project already solves similar problems.\n\nIf `.github\u002Finstructions\u002F` (or `.ai\u002Finstructions\u002F`) exists, read instruction files relevant to the issue's file types — these provide detailed framework patterns and code examples.\n\n**Example: \"Dynamic show\u002Fhide scoping inside nested repeatable fields\"**\n1. Search for existing repeatable fields that use show\u002Fhide → `Grep` for the show\u002Fhide pattern in config files\n2. Find how they handle scoping → read the matching config and any companion JS\n3. Identify the concrete pattern (scoped CSS classes, row-targeted selectors, etc.)\n4. Formulate a specific solution with exact code\u002Fconfig to add\n\n**General approach:**\n- Search for the pattern or keyword in the existing codebase\n- Find 1-2 working examples of the same technique\n- Extract the concrete implementation details (class names, config structure, selectors, etc.)\n- Formulate a specific fix, not a generic recommendation\n\n## 4. Update implement.md\n\nFor each resolved issue:\n\n**If the fix belongs in an existing step** — append the fix details to that step's `**What:**` section:\n```markdown\n**What:**\n\u003Cexisting instructions>\n- **Risk mitigation:** Use unique scoped class `cmp-component__toggle--step{N}` on the\n  checkbox field (see `card\u002Fconfig.xml:42` for the same pattern). This scopes\n  the show\u002Fhide listener to the correct repeatable row.\n```\n\n**If the fix needs a new step** — insert a step in the correct dependency position:\n```markdown\n### Step N: \u003CDescriptive title>\n**Status:** pending\n**Files:** `path\u002Fto\u002Ffile`, `path\u002Fto\u002Fother-if-needed`\n**What:**\n- \u003Cconcrete instructions with file:line references>\n**Why:** Mitigates risk — \u003Cone sentence explaining the issue>\n**Test:** \u003Cspecific verification approach>\n```\n\n**Update the Risks section** — replace vague risk with resolution:\n```markdown\n## Risks\n- ~~\u003Coriginal risk description>~~ → **Resolved:** \u003Cone-line solution> (Step N)\n```\n\n## 5. Write Resolve Report\n\n**Write** the following table and summary to `$SPEC_DIR\u002Fresolve-report.md`. Do not print to chat.\n\n```markdown\n## Plan Risks Resolved\n\n| # | Risk\u002FIssue | Resolution | Step Updated |\n|---|-----------|------------|--------------|\n| 1 | \u003Crisk description> | \u003Cone-line solution> | Step N |\n| 2 | \u003Crisk description> | \u003Cone-line solution> | New Step M |\n\n**Issues resolved:** \u003Ccount>\n**Steps modified:** \u003Ccount>\n**Steps added:** \u003Ccount>\n```\n\n## Examples\n\n1. `\u002Fdx-plan-resolve 2416553` — Reads implement.md risks (\"Dynamic show\u002Fhide scoping in nested repeatable fields\"), searches the codebase for existing repeatable field patterns, finds a working example in `card\u002Fconfig.xml`, and updates Step 4 with a concrete fix using scoped CSS classes.\n\n2. `\u002Fdx-plan-resolve` (no argument) — Uses the most recent spec directory. Finds 2 risks and 1 vague step. Resolves all by adding specific file:line references and inserting a new Step 3b for risk mitigation. Updates the Risks section with strikethrough originals and resolution notes.\n\n3. `\u002Fdx-plan-resolve 2416553` (no issues) — Reads implement.md, finds no risks, blocked steps, or vague instructions. Prints \"No risks or issues to resolve — plan is ready.\" and stops.\n\n## Troubleshooting\n\n- **\"No risks or issues to resolve\"**\n  **Cause:** The plan has no Risks section, no blocked steps, and no vague instructions.\n  **Fix:** This is good — the plan is ready for execution. Run `\u002Fdx-step-all` to proceed.\n\n- **Resolution references a file that doesn't exist**\n  **Cause:** The codebase search found a pattern in a file that was since moved or deleted.\n  **Fix:** Run `\u002Fdx-plan-validate` after resolving to verify file existence. Fix any invalid references manually in implement.md.\n\n- **Step numbering is broken after inserting new steps**\n  **Cause:** A new step was inserted but cross-references to step numbers weren't updated.\n  **Fix:** Re-run `\u002Fdx-plan-validate` — it checks dependency order and will flag any broken cross-references.\n\n## Rules\n\n- **Research before solving** — don't guess at solutions. Find working examples in the codebase first.\n- **Concrete fixes only** — every solution must include specific file paths, class names, or code snippets. \"Consider using unique selectors\" is not a fix. \"`class='cmp-component__toggle--step2'`\" is a fix.\n- **Minimal plan changes** — prefer adding to existing steps over creating new ones. Only add a new step if the fix is substantial enough to warrant separate execution.\n- **Preserve step numbering** — when inserting steps, renumber correctly and update any cross-references.\n- **Don't execute** — update the plan only. Execution happens in step-* skills.\n- **One pass** — resolve what you can, report what you can't. Don't loop.\n\n## Present Summary (standalone path only)\n\n\u003C!-- standalone-only — emit only when $ORCHESTRATED == 0 -->\n\nWhen running standalone, emit the resolve summary to chat:\n\n```markdown\n## Plan Risks Resolved\n\n| # | Risk\u002FIssue | Resolution | Step Updated |\n|---|-----------|------------|--------------|\n| 1 | \u003Crisk description> | \u003Cone-line solution> | Step N |\n| 2 | \u003Crisk description> | \u003Cone-line solution> | New Step M |\n\n**Issues resolved:** \u003Ccount>\n**Steps modified:** \u003Ccount>\n**Steps added:** \u003Ccount>\n\n### Next step:\n- `\u002Fdx-plan-validate` — re-validate the updated plan\n```\n\nWhen orchestrated (`$ORCHESTRATED == 1`), skip this section entirely and emit only the `## Return` block.\n\n## Return\n\nThis skill runs in a forked context. It MUST end with a `## Return` block per `plugins\u002Fdx-core\u002Fshared\u002Fskill-return-contract.md`.\n\nExamples:\n\n```markdown\n## Return\nverdict: pass\nsummary: Resolved 2 risks; updated implement.md (Step 3 split into 3a\u002F3b for clearer commit boundary).\nartifacts:\n  - .ai\u002Fspecs\u002F2490722-microsite\u002Fresolve-report.md\n  - .ai\u002Fspecs\u002F2490722-microsite\u002Fimplement.md\nnext_action: re-run \u002Fdx-plan-validate\n```\n",{"name":5,"context":49,"description":7,"allowed-tools":50,"argument-hint":52},"fork",[31,28,41,29,51],"agent","[Work Item ID or slug (optional — uses most recent if omitted)]","main","5c642842a92100dc7561ae0682a152a74846e186","plugins\u002Fdx-core\u002Fskills\u002Fdx-plan-resolve",3,"https:\u002F\u002Fgithub.com\u002Feasingthemes\u002Fdx-aem-flow","https:\u002F\u002Fgithub.com\u002Feasingthemes","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fdraganfilipovic\u002F","Agentic SDLC platform in production. I build agent-ready codebases. AEM MCP Server author.","2026-11-11 09:59:48",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add easingthemes\u002Fdx-aem-flow --skill dx-plan-resolve",{"tool":68,"command":69},"bunx","bunx skills add easingthemes\u002Fdx-aem-flow --skill dx-plan-resolve",{"tool":71,"command":72},"pnpm","pnpm dlx skills add easingthemes\u002Fdx-aem-flow --skill dx-plan-resolve","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Feasingthemes\u002Fdx-aem-flow\u002Fblob\u002Fmain\u002Fplugins\u002Fdx-core\u002Fskills\u002Fdx-plan-resolve\u002FSKILL.md",true,[],[77,97,118,139,155,170],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":44},"01M6H48W19F46A7B7TSSQAMYRW","dx-hub-status","Show hub dispatch status — which repos are running, done, blocked or failed. Use for 'hub status', 'what's running'.","https:\u002F\u002Fgithub.com\u002Feasingthemes\u002Fdx-aem-flow\u002Fblob\u002Fmain\u002Fplugins\u002Fdx-hub\u002Fskills\u002Fdx-hub-status\u002FSKILL.md",[],[26,84,85,86,87,88,89,42,90,91,38,92,93,35,94,31,29,95,96],"dx hub status","hub","status","hub status","which","show","ticket","clean","done","Bash","dispatch","repos","grep",{"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":44},"01M6H48R6ZH7YMVPMVWMMWT3RA","dx-hub-init","Initialize a hub directory for multi-repo orchestration. Discovers sibling repos, merges configs, validates CLI compatibility. Use when setting up hub mode for the first time. Trigger on \"init hub\", \"set up hub\", \"multi-repo setup\".","https:\u002F\u002Fgithub.com\u002Feasingthemes\u002Fdx-aem-flow\u002Fblob\u002Fmain\u002Fplugins\u002Fdx-hub\u002Fskills\u002Fdx-hub-init\u002FSKILL.md",[],[104,105,26,106,85,107,108,109,110,111,112,113,114,115,93,116,117,31,29,28],"init","hub init","dx hub init","SET","time","mode","default","up","repo setup","orchestration","configure","multi-repo","cli","directory",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":127,"publishedAt":44},"01M6H48K267CWEF8YNN3Y49BVT","dx-hub-dispatch","Dispatch a ticket to several repos — open an independent Claude session per repo in VS Code terminals. Use for 'hub dispatch', 'work on ticket across repos'.","https:\u002F\u002Fgithub.com\u002Feasingthemes\u002Fdx-aem-flow\u002Fblob\u002Fmain\u002Fplugins\u002Fdx-hub\u002Fskills\u002Fdx-hub-dispatch\u002FSKILL.md",[124],{"categoryNo":125,"categoryName":126,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[26,128,94,85,129,42,130,131,132,90,133,134,38,135,93,136,137,138,35,34],"dx hub dispatch","ado","repo","work on","session","open","MCP","URL","vscode","code","across",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":44},"01M6H48FAWKTT6AAWT3H80ZKE0","dx-hub-config","View and edit hub configuration — add repos, adjust terminal delay. Use to manage hub settings. Trigger on \"hub config\", \"add repo to hub\", \"terminal delay\".","https:\u002F\u002Fgithub.com\u002Feasingthemes\u002Fdx-aem-flow\u002Fblob\u002Fmain\u002Fplugins\u002Fdx-hub\u002Fskills\u002Fdx-hub-config\u002FSKILL.md",[],[26,146,85,147,89,148,130,149,150,151,152,38,114,93,153,31,154,29,28,95],"dx hub config","config","view","manage","trigger","true","adjust","terminal","settings",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":161,"publishedAt":44},"01M6H48BNMYEJY6CCWPYHNQDAT","dx-discover-repos","Resolve which repos a work item touches (explicit directive → simple block → cross-repo table → LLM). Used by the KAI-HUB router to fan an agent out across repos; 'which repos'.","https:\u002F\u002Fgithub.com\u002Feasingthemes\u002Fdx-aem-flow\u002Fblob\u002Fmain\u002Fplugins\u002Fdx-hub\u002Fskills\u002Fdx-discover-repos\u002FSKILL.md",[],[162,26,163,95,88,130,138,164,35,165,34,166,85,167,168,169],"discover","dx discover repos","router","directive","simple","block","sonnet","table",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":177,"publishedAt":44},"01M6H487QA1FDSBT1HTZGW4HAQ","dx-upgrade","Upgrade a consumer project to the installed plugin versions — run dx-doctor, fix stale and missing files, list manual actions. Use after upgrading plugins.","https:\u002F\u002Fgithub.com\u002Feasingthemes\u002Fdx-aem-flow\u002Fblob\u002Fmain\u002Fplugins\u002Fdx-core\u002Fskills\u002Fdx-upgrade\u002FSKILL.md",[176],{"categoryNo":125,"categoryName":126,"taxonomyType":21,"taxonomyTypeDesc":22},[178,26,179,180,181,41,40,182,183,184,31,29,28,185,186,187,188,38,189,190],"upgrade","dx upgrade","project","actions","files","auto","run","list","doctor","manual","missing","plugin","plugins"]