[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CRCGKSZFFS8P79S3PMFS7B":3,"skill-same:01M6CRCGKSZFFS8P79S3PMFS7B":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":45,"install":46,"resources":58},"01M6CRCGKSZFFS8P79S3PMFS7B","hp-fix",null,"Use after hp-review identifies issues that need fixing.","ohmyhotelco\u002Fhare-cc-plugins","ohmyhotelco","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F258133233?v=4","01M6CR4HP2N9F9ZWNX1KRHQ2W1","01M6CR4HSJC5J80RVQMD5K9QRN",2,"MIT","https:\u002F\u002Fgithub.com\u002Fohmyhotelco\u002Fhare-cc-plugins\u002Fblob\u002Fmain\u002Fhomepage-plugin\u002Fskills\u002Fhp-fix\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30],"fix","hp fix","review","issues","Bash","page","grep","read","write","edit","use","name","true","2026-11-10 10:12:30",false,"---\nname: hp-fix\ndescription: \"Use after hp-review identifies issues that need fixing.\"\nargument-hint: \"\u003Cpage-name>\"\nuser-invocable: true\nallowed-tools: Read, Write, Edit, Glob, Grep, Bash, Agent\n---\n\n# Fix Skill\n\nFixes issues identified by the `hp-review` skill (SEO, quality, and visual fidelity issues) or verification failures from `hp-verify`. All fixes are direct (no TDD classification) since homepage sections are primarily presentational.\n\nConventions: `${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Fhp-shared\u002FSKILL.md`.\n\n## Instructions\n\n### Step 0: Read Configuration\n\nRead `.claude\u002Fhomepage-plugin.json`. If not found, exit with instruction to run `\u002Fhomepage-plugin:hp-init`.\n\nRead `defaultLocale` — all user-facing output in this language.\n\n### Step 1: Validate Prerequisites\n\nRequired files:\n- `docs\u002Fpages\u002F{page-name}\u002Fpage-plan.json` — page plan\n- `docs\u002Fpages\u002F{page-name}\u002F.progress\u002F{page-name}.json` — progress file\n- `docs\u002Fpages\u002F{page-name}\u002F.implementation\u002Fhomepage\u002Freview-report.json` — review report (required for `review-failed`, `reviewed`, `fixing` statuses)\n\nCheck progress status:\n- Accept: `review-failed`, `reviewed` (with warnings), `fixing`, `verified`, `verify-failed`, `escalated`\n- Reject: `planned`, `generated`, `done`\n- If `generated`: instruct user to run `\u002Fhomepage-plugin:hp-verify` or `\u002Fhomepage-plugin:hp-review` first\n- If `verified` or `verify-failed` without `review-report.json`: run verification-based fixes using hp-verify output (tsc\u002Feslint\u002Fbuild errors) instead of review issues\n- If `escalated`: user has manually intervened and wants to re-run fixes\n\n### Step 2: Check Fix Rounds\n\nRead fix history from `docs\u002Fpages\u002F{page-name}\u002F.implementation\u002Fhomepage\u002Ffix-report.json` (if exists):\n- Count previous fix rounds\n- If 3 rounds already completed with remaining issues → warn and suggest manual intervention or plan revision\n\n### Step 3: Acquire Lock\n\nSame lock protocol as hp-gen Step 3 (JSON format with `lockedBy`, `lockedAt`, `pageName`; 30-min stale threshold).\n\nLock file path: `docs\u002Fpages\u002F{page-name}\u002F.implementation\u002Fhomepage\u002F.lock`\n- Write with `lockedBy: \"hp-fix\"`\n- Stale lock (>= 30 min) → auto-remove and proceed\n- Active lock → exit with \"Another homepage-plugin operation is in progress\"\n\n### Step 3.5: Check for Fixable Issues\n\nIf `review-report.json` exists, read it and count total issues across `seo.issues`, `quality.issues`, and `visualFidelity.issues` (if present).\n\nIf there are **zero issues** (e.g., all issues were manually resolved between `hp-review` and `hp-fix`, or the review passed with only score-based warnings that have no associated issue entries):\n- Skip the fix phase entirely\n- Display: \"No fixable issues found in the review report. Run `\u002Fhomepage-plugin:hp-review` to re-evaluate.\"\n- Release the lock and exit without changing the progress status\n\n### Step 4: Launch Review Fixer\n\n**4.1 If `review-report.json` exists** (normal flow — after `hp-review`):\n\nLaunch the `review-fixer` agent (`subagent_type: \"homepage-plugin:review-fixer\"`) with:\n- `pageName` — page identifier\n- `planFile` — path to page-plan.json\n- `projectRoot` — project root\n- `reviewReportFile` — path to review-report.json\n- `config` — homepage-plugin configuration\n\nThe agent will:\n1. Pre-check issues still exist\n2. Apply direct fixes (critical first, then warnings)\n3. Run verification (tsc + ESLint + astro build)\n\n**4.2 If `review-report.json` does NOT exist** (verification-only flow — after `hp-verify` without `hp-review`):\n\nRun verification commands directly (without launching review-fixer agent):\n1. Run `npx tsc --noEmit 2>&1` — collect TypeScript errors\n2. Run `npx eslint . 2>&1` — collect ESLint errors (if config exists)\n3. Run `npx astro build 2>&1` — collect build errors\n\nFor each error found, apply a direct fix using the error message as context.\nAfter fixing, re-run all verification commands to confirm fixes.\n\nConstruct a synthetic fix report (same schema as Step 5) with issues derived from verification output rather than review report.\n\n### Step 5: Save Fix Report\n\nSave agent output to `docs\u002Fpages\u002F{page-name}\u002F.implementation\u002Fhomepage\u002Ffix-report.json`:\n\n```json\n{\n  \"timestamp\": \"2026-03-23T...\",\n  \"round\": 1,\n  \"issuesReceived\": 5,\n  \"issuesFixed\": 4,\n  \"issuesSkipped\": 1,\n  \"skippedReasons\": [\n    {\n      \"issue\": \"...\",\n      \"reason\": \"Issue no longer present in current code\"\n    }\n  ],\n  \"escalated\": [],\n  \"verification\": {\n    \"tsc\": \"pass\",\n    \"eslint\": \"pass\",\n    \"build\": \"pass\"\n  },\n  \"remainingIssues\": []\n}\n```\n\n### Step 6: Update Progress\n\nUpdate `docs\u002Fpages\u002F{page-name}\u002F.progress\u002F{page-name}.json`:\n\n- All issues fixed + verification passes → `fixing` (needs re-review)\n- Some issues remain → `fixing` (needs re-review)\n- Issues escalated → `escalated` (manual intervention)\n\n### Step 7: Release Lock\n\nRelease `docs\u002Fpages\u002F{page-name}\u002F.implementation\u002Fhomepage\u002F.lock`.\n\n### Step 8: Display Results\n\nShow fix summary:\n\n```\nFix Results (Round 1):\n  Issues received: 5\n  Issues fixed:    4\n  Issues skipped:  1 (already resolved)\n  Escalated:       0\n\n  Verification: tsc ✓ | ESLint ✓ | Build ✓\n\nNext step: Run \u002Fhomepage-plugin:hp-review to re-review.\n```\n\nIf visual fidelity issues were fixed:\n```\nFix Results (Round 1):\n  Issues received: 7\n  Issues fixed:    6\n  Issues skipped:  1 (already resolved)\n  Escalated:       0\n\n  Fixed: 3 seo, 2 quality, 1 visual_fidelity\n\n  Verification: tsc ✓ | ESLint ✓ | Build ✓\n\nNext step: Run \u002Fhomepage-plugin:hp-review to re-review.\n```\n\nIf escalated:\n```\nFix Results (Round 3):\n  Escalated issues: 2\n    1. [accessibility] Complex focus management in ContactForm — needs manual review\n    2. [seo] Dynamic OG image generation — requires build pipeline change\n\n  These issues require manual intervention.\n  After resolving, re-enter pipeline via \u002Fhomepage-plugin:hp-review.\n```\n\n### Step 9: 3-Round Warning\n\nAfter 3 fix rounds with remaining issues:\n\n```\nWarning: 3 fix rounds completed with unresolved issues.\nPossible actions:\n  1. Review and manually fix remaining issues\n  2. Re-plan the page: \u002Fhomepage-plugin:hp-plan {page-name}\n  3. Accept current state and mark as done\n```\n\n## Communication Language\n\nRead `defaultLocale` from `.claude\u002Fhomepage-plugin.json` for all user-facing output.\n","# Fix Skill\n\nFixes issues identified by the `hp-review` skill (SEO, quality, and visual fidelity issues) or verification failures from `hp-verify`. All fixes are direct (no TDD classification) since homepage sections are primarily presentational.\n\nConventions: `${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Fhp-shared\u002FSKILL.md`.\n\n## Instructions\n\n### Step 0: Read Configuration\n\nRead `.claude\u002Fhomepage-plugin.json`. If not found, exit with instruction to run `\u002Fhomepage-plugin:hp-init`.\n\nRead `defaultLocale` — all user-facing output in this language.\n\n### Step 1: Validate Prerequisites\n\nRequired files:\n- `docs\u002Fpages\u002F{page-name}\u002Fpage-plan.json` — page plan\n- `docs\u002Fpages\u002F{page-name}\u002F.progress\u002F{page-name}.json` — progress file\n- `docs\u002Fpages\u002F{page-name}\u002F.implementation\u002Fhomepage\u002Freview-report.json` — review report (required for `review-failed`, `reviewed`, `fixing` statuses)\n\nCheck progress status:\n- Accept: `review-failed`, `reviewed` (with warnings), `fixing`, `verified`, `verify-failed`, `escalated`\n- Reject: `planned`, `generated`, `done`\n- If `generated`: instruct user to run `\u002Fhomepage-plugin:hp-verify` or `\u002Fhomepage-plugin:hp-review` first\n- If `verified` or `verify-failed` without `review-report.json`: run verification-based fixes using hp-verify output (tsc\u002Feslint\u002Fbuild errors) instead of review issues\n- If `escalated`: user has manually intervened and wants to re-run fixes\n\n### Step 2: Check Fix Rounds\n\nRead fix history from `docs\u002Fpages\u002F{page-name}\u002F.implementation\u002Fhomepage\u002Ffix-report.json` (if exists):\n- Count previous fix rounds\n- If 3 rounds already completed with remaining issues → warn and suggest manual intervention or plan revision\n\n### Step 3: Acquire Lock\n\nSame lock protocol as hp-gen Step 3 (JSON format with `lockedBy`, `lockedAt`, `pageName`; 30-min stale threshold).\n\nLock file path: `docs\u002Fpages\u002F{page-name}\u002F.implementation\u002Fhomepage\u002F.lock`\n- Write with `lockedBy: \"hp-fix\"`\n- Stale lock (>= 30 min) → auto-remove and proceed\n- Active lock → exit with \"Another homepage-plugin operation is in progress\"\n\n### Step 3.5: Check for Fixable Issues\n\nIf `review-report.json` exists, read it and count total issues across `seo.issues`, `quality.issues`, and `visualFidelity.issues` (if present).\n\nIf there are **zero issues** (e.g., all issues were manually resolved between `hp-review` and `hp-fix`, or the review passed with only score-based warnings that have no associated issue entries):\n- Skip the fix phase entirely\n- Display: \"No fixable issues found in the review report. Run `\u002Fhomepage-plugin:hp-review` to re-evaluate.\"\n- Release the lock and exit without changing the progress status\n\n### Step 4: Launch Review Fixer\n\n**4.1 If `review-report.json` exists** (normal flow — after `hp-review`):\n\nLaunch the `review-fixer` agent (`subagent_type: \"homepage-plugin:review-fixer\"`) with:\n- `pageName` — page identifier\n- `planFile` — path to page-plan.json\n- `projectRoot` — project root\n- `reviewReportFile` — path to review-report.json\n- `config` — homepage-plugin configuration\n\nThe agent will:\n1. Pre-check issues still exist\n2. Apply direct fixes (critical first, then warnings)\n3. Run verification (tsc + ESLint + astro build)\n\n**4.2 If `review-report.json` does NOT exist** (verification-only flow — after `hp-verify` without `hp-review`):\n\nRun verification commands directly (without launching review-fixer agent):\n1. Run `npx tsc --noEmit 2>&1` — collect TypeScript errors\n2. Run `npx eslint . 2>&1` — collect ESLint errors (if config exists)\n3. Run `npx astro build 2>&1` — collect build errors\n\nFor each error found, apply a direct fix using the error message as context.\nAfter fixing, re-run all verification commands to confirm fixes.\n\nConstruct a synthetic fix report (same schema as Step 5) with issues derived from verification output rather than review report.\n\n### Step 5: Save Fix Report\n\nSave agent output to `docs\u002Fpages\u002F{page-name}\u002F.implementation\u002Fhomepage\u002Ffix-report.json`:\n\n```json\n{\n  \"timestamp\": \"2026-03-23T...\",\n  \"round\": 1,\n  \"issuesReceived\": 5,\n  \"issuesFixed\": 4,\n  \"issuesSkipped\": 1,\n  \"skippedReasons\": [\n    {\n      \"issue\": \"...\",\n      \"reason\": \"Issue no longer present in current code\"\n    }\n  ],\n  \"escalated\": [],\n  \"verification\": {\n    \"tsc\": \"pass\",\n    \"eslint\": \"pass\",\n    \"build\": \"pass\"\n  },\n  \"remainingIssues\": []\n}\n```\n\n### Step 6: Update Progress\n\nUpdate `docs\u002Fpages\u002F{page-name}\u002F.progress\u002F{page-name}.json`:\n\n- All issues fixed + verification passes → `fixing` (needs re-review)\n- Some issues remain → `fixing` (needs re-review)\n- Issues escalated → `escalated` (manual intervention)\n\n### Step 7: Release Lock\n\nRelease `docs\u002Fpages\u002F{page-name}\u002F.implementation\u002Fhomepage\u002F.lock`.\n\n### Step 8: Display Results\n\nShow fix summary:\n\n```\nFix Results (Round 1):\n  Issues received: 5\n  Issues fixed:    4\n  Issues skipped:  1 (already resolved)\n  Escalated:       0\n\n  Verification: tsc ✓ | ESLint ✓ | Build ✓\n\nNext step: Run \u002Fhomepage-plugin:hp-review to re-review.\n```\n\nIf visual fidelity issues were fixed:\n```\nFix Results (Round 1):\n  Issues received: 7\n  Issues fixed:    6\n  Issues skipped:  1 (already resolved)\n  Escalated:       0\n\n  Fixed: 3 seo, 2 quality, 1 visual_fidelity\n\n  Verification: tsc ✓ | ESLint ✓ | Build ✓\n\nNext step: Run \u002Fhomepage-plugin:hp-review to re-review.\n```\n\nIf escalated:\n```\nFix Results (Round 3):\n  Escalated issues: 2\n    1. [accessibility] Complex focus management in ContactForm — needs manual review\n    2. [seo] Dynamic OG image generation — requires build pipeline change\n\n  These issues require manual intervention.\n  After resolving, re-enter pipeline via \u002Fhomepage-plugin:hp-review.\n```\n\n### Step 9: 3-Round Warning\n\nAfter 3 fix rounds with remaining issues:\n\n```\nWarning: 3 fix rounds completed with unresolved issues.\nPossible actions:\n  1. Review and manually fix remaining issues\n  2. Re-plan the page: \u002Fhomepage-plugin:hp-plan {page-name}\n  3. Accept current state and mark as done\n```\n\n## Communication Language\n\nRead `defaultLocale` from `.claude\u002Fhomepage-plugin.json` for all user-facing output.\n",{"name":5,"description":7,"allowed-tools":36,"argument-hint":37,"user-invocable":38},"Read, Write, Edit, Glob, Grep, Bash, Agent","\u003Cpage-name>",true,"main","eaef2a5b6092b72972ff2f25ef79803753bc9bbf","homepage-plugin\u002Fskills\u002Fhp-fix",0,"https:\u002F\u002Fgithub.com\u002Fohmyhotelco\u002Fhare-cc-plugins","https:\u002F\u002Fgithub.com\u002Fohmyhotelco","2026-11-11 08:26:27",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":38},[48,51,54],{"tool":49,"command":50},"npx","npx skills add ohmyhotelco\u002Fhare-cc-plugins --skill hp-fix",{"tool":52,"command":53},"bunx","bunx skills add ohmyhotelco\u002Fhare-cc-plugins --skill hp-fix",{"tool":55,"command":56},"pnpm","pnpm dlx skills add ohmyhotelco\u002Fhare-cc-plugins --skill hp-fix","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fohmyhotelco\u002Fhare-cc-plugins\u002Fblob\u002Fmain\u002Fhomepage-plugin\u002Fskills\u002Fhp-fix\u002FSKILL.md",[],[60,85,111,135,151,171],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":31},"01M6M5QVXQNQMJBP1JZP9T440T","hp-shared","Shared conventions for every homepage-plugin agent and skill — stack, code conventions, state-file writes, check commands and how to report them. Preloaded into agents through their `skills:` frontmatter; not meant to be invoked by hand.","https:\u002F\u002Fgithub.com\u002Fohmyhotelco\u002Fhare-cc-plugins\u002Fblob\u002Fmain\u002Fhomepage-plugin\u002Fskills\u002Fhp-shared\u002FSKILL.md",[],[67,68,69,70,71,72,73,74,75,76,77,78,79,80,81,82,83,84],"shared","hp shared","state","stack","plugin","how","for","report","code conventions","commands","how to","conventions","false","frontmatter","file","code","hand","check",{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":99,"publishedAt":31},"01M6M5PZTN1M0G4AHJV08VF1HV","fe-shared","Shared conventions for every frontend-react-plugin agent and skill — code conventions, state files and locks, accepted deviations, design principles, build working directory, router-mode command matrix, TypeScript check. Preloaded into agents through their `skills:` frontmatter; not meant to be invoked by hand.","https:\u002F\u002Fgithub.com\u002Fohmyhotelco\u002Fhare-cc-plugins\u002Fblob\u002Fmain\u002Ffrontend-react-plugin\u002Fskills\u002Ffe-shared\u002FSKILL.md",[91,96],{"categoryNo":92,"categoryName":93,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":97,"categoryName":98,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000015","视觉设计",[67,100,73,101,75,102,103,104,105,79,82,83,106,84,107,69,71,108,109,110],"fe shared","mode","frontend","design","design principles","files","react","router","principles","command","build",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":123,"publishedAt":31},"01M6M5GAW7ZZ3580DVCMH51SFQ","be-spring-shared","Shared conventions for every backend-springboot-plugin agent and skill — tech stack, CQRS architecture, naming, coding standards, TDD, commit and build rules, state files. Preloaded into agents through their `skills:` frontmatter; not meant to be invoked by hand.","https:\u002F\u002Fgithub.com\u002Fohmyhotelco\u002Fhare-cc-plugins\u002Fblob\u002Fmain\u002Fbackend-springboot-plugin\u002Fskills\u002Fbe-spring-shared\u002FSKILL.md",[117,120],{"categoryNo":118,"categoryName":119,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":121,"categoryName":122,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000023","Skill与智能体开发",[67,124,125,105,79,126,127,83,70,128,80,129,130,131,73,132,133,69,71,134],"spring","be spring shared","commit","architecture","coding standards","coding","standards","tech","Rules","cqrs","naming",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":31},"01M6FNV58QMW8K71SA9FGTXMF4","pp-translate","Use after directly editing the working language spec to sync changes to other supported languages.","https:\u002F\u002Fgithub.com\u002Fohmyhotelco\u002Fhare-cc-plugins\u002Fblob\u002Fmain\u002Fplanning-plugin\u002Fskills\u002Fpp-translate\u002FSKILL.md",[],[142,143,144,145,29,146,25,147,26,27,148,28,81,149,30,150],"pp","pp translate","translate","feature","editing","spec","sync","language","changes",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":158,"publishedAt":31},"01M6FNV0PGRKR2MW0AEPS6XP0Q","pp-sync-stitch","Use when wireframes were manually edited on the Stitch website and need to be re-fetched to the local project.","https:\u002F\u002Fgithub.com\u002Fohmyhotelco\u002Fhare-cc-plugins\u002Fblob\u002Fmain\u002Fplanning-plugin\u002Fskills\u002Fpp-sync-stitch\u002FSKILL.md",[157],{"categoryNo":121,"categoryName":122,"taxonomyType":94,"taxonomyTypeDesc":95},[159,142,160,148,161,162,145,163,164,165,166,28,22,167,168,169,170,29,25,30],"pp sync stitch","stitch","projects","get","project","re","local","MCP","id","wireframes","website","screen",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":178,"publishedAt":31},"01M6FNTWW2KHS9XRAR72X33G0B","pp-sync-notion","Use when a specification needs to be published or re-synced to Notion after finalization or manual edits.","https:\u002F\u002Fgithub.com\u002Fohmyhotelco\u002Fhare-cc-plugins\u002Fblob\u002Fmain\u002Fplanning-plugin\u002Fskills\u002Fpp-sync-notion\u002FSKILL.md",[177],{"categoryNo":121,"categoryName":122,"taxonomyType":94,"taxonomyTypeDesc":95},[142,179,148,180,145,164,181,182,166,28,183,29,25,26,27,24,30],"notion","pp sync notion","search","manual","specification"]