[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AASE1PD2H3TCX7V2AQBD53":3,"skill-same:01M7AASE1PD2H3TCX7V2AQBD53":49},{"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":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M7AASE1PD2H3TCX7V2AQBD53","git-change-conventions",null,"在此 repository 建立或命名 branch、pull request、commit 時使用。遵守既定 type prefix，並撰寫詳盡 commit message。","Andy-CH-BO-AN\u002Fplaywright-self-healing-tests","Andy-CH-BO-AN","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F58759761?v=4","01M71FSKGT9TWBMY2SFP4V2JR8","01M7AAS4QMEMT1S49WSF8H4NWE",0,"MIT","https:\u002F\u002Fgithub.com\u002FAndy-CH-BO-AN\u002Fplaywright-self-healing-tests\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgit-change-conventions\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: git-change-conventions\ndescription: 在此 repository 建立或命名 branch、pull request、commit 時使用。遵守既定 type prefix，並撰寫詳盡 commit message。\n---\n\n# Git Change Conventions\n\ntask 包含建立 branch、更新 README、命名 pull request、撰寫 commit message，或提議 branch／PR／commit naming convention 時使用。\n\n## PR title format\n\nPull request title 必須精確採用：`\u003CTYPE>: \u003Csummary>`。\n\n允許的 `\u003CTYPE>`：\n\n- `FEATURE:` new feature\n- `FIX:` bug fix\n- `REFACTOR:` 無行為變更的 code refactor\n- `DOCS:` documentation only\n- `TEST:` tests only\n- `STYLE:` 僅 formatting，例如 linting 或 layout cleanup\n- `PERF:` performance improvement\n- `CHORE:` maintenance 或 miscellaneous housekeeping\n- `CI:` continuous integration configuration 或 script\n\n## Branch format\n\nGit branch 不可含 `:` 或 space，故採用：`\u003Ctype>\u002F\u003Csummary-in-kebab-case>`。\n\n例：`feat\u002Fadd-weekly-fatigue-summary`、`fix\u002Fhandle-empty-garmin-heart-rate-payload`。\n\n## 必要規則\n\n1. 除非有明確理由，branch 與 PR title 使用相同 logical type。\n2. branch 使用 short lowercase prefix（如 `feat`）；PR title 使用完整允許的 TYPE（如 `FEATURE:`）。\n3. prefix 後文字精確描述實際變更。\n4. 使用者未明確改變 convention 前，不得自創 top-level prefix。\n5. 跨多 category 時選擇最符合主要 user-facing outcome 的 prefix。\n6. branch summary 轉為 lowercase kebab-case。\n7. PR description 應包含 summary、why、what changed、重要 implementation／validation note。\n\n## Commit message 規則\n\n- Commit message 必須詳盡，不可過短。\n- subject line 清楚說明 intent 與 affected area。\n- 非 trivial 變更優先採 multiline commit message。\n- body 摘要 what changed、why 需要此變更、重要 implementation 或 validation note。\n\n## 範例\n\n- Branch：`feat\u002Fadd-weekly-fatigue-summary`\n- PR title：`FEATURE: add weekly fatigue summary to coach report`\n- Branch：`fix\u002Fhandle-empty-garmin-heart-rate-payload`\n- PR title：`FIX: handle empty Garmin heart rate payload`\n- Branch：`docs\u002Fadd-shared-git-naming-conventions`\n- PR title：`DOCS: add shared Git naming conventions for branch, PR, and commits`\n\n## GitHub CLI environment\n\n所有 `gh` command 必須在 local host environment 執行，使用其 credential store 與 GitHub configuration。不可使用 sandboxed `gh` credential 或 fallback；local-host `gh` authentication 失敗時停止並回報 authentication blocker。\n\n## 使用 GitHub CLI 建立 PR\n\n使用 `gh` 建立 PR 時套用上述 convention：\n\n```bash\ngh pr create \\\n  --title \"TYPE: summary\" \\\n  --body \"## Summary\n\u003C這個 PR 做什麼>\n\n## Why\n\u003C為何需要此變更>\n\n## Changes\n- \u003Cfile\u002Farea>: \u003Cdescription>\n\n## Validation\n- \u003C執行的 test、manual check 或 screenshot>\" \\\n  --base main\n```\n\n- 不得使用 `--draft`；每個 PR 都必須可立即 review。\n- team 要求 reviewer 時加入 `--reviewer \u003Chandle>`。\n- 有 project label 時加入 `--label \u003Clabel>`。\n- PR title TYPE 必須用允許名稱，不可直接將 branch prefix 大寫：`feat`→`FEATURE`、`fix`→`FIX`、`refactor`→`REFACTOR`、`docs`→`DOCS`、`test`→`TEST`、`style`→`STYLE`、`perf`→`PERF`、`chore`→`CHORE`、`ci`→`CI`。\n\n## PR review follow-up\n\n完成要求的 PR review change 後，commit 並 push fix，再使用 PR 的 **Add a comment** action 發布 `@codex review`，要求 Codex reviewer 再次審查。\n\n## Output expectation\n\n- 被要求建立名稱時，提供精確符合 convention 的 branch 與 PR title。\n- 被要求 commit 時，依變更範圍撰寫詳盡 commit message，不用單行 shorthand。\n","# Git Change Conventions\n\ntask 包含建立 branch、更新 README、命名 pull request、撰寫 commit message，或提議 branch／PR／commit naming convention 時使用。\n\n## PR title format\n\nPull request title 必須精確採用：`\u003CTYPE>: \u003Csummary>`。\n\n允許的 `\u003CTYPE>`：\n\n- `FEATURE:` new feature\n- `FIX:` bug fix\n- `REFACTOR:` 無行為變更的 code refactor\n- `DOCS:` documentation only\n- `TEST:` tests only\n- `STYLE:` 僅 formatting，例如 linting 或 layout cleanup\n- `PERF:` performance improvement\n- `CHORE:` maintenance 或 miscellaneous housekeeping\n- `CI:` continuous integration configuration 或 script\n\n## Branch format\n\nGit branch 不可含 `:` 或 space，故採用：`\u003Ctype>\u002F\u003Csummary-in-kebab-case>`。\n\n例：`feat\u002Fadd-weekly-fatigue-summary`、`fix\u002Fhandle-empty-garmin-heart-rate-payload`。\n\n## 必要規則\n\n1. 除非有明確理由，branch 與 PR title 使用相同 logical type。\n2. branch 使用 short lowercase prefix（如 `feat`）；PR title 使用完整允許的 TYPE（如 `FEATURE:`）。\n3. prefix 後文字精確描述實際變更。\n4. 使用者未明確改變 convention 前，不得自創 top-level prefix。\n5. 跨多 category 時選擇最符合主要 user-facing outcome 的 prefix。\n6. branch summary 轉為 lowercase kebab-case。\n7. PR description 應包含 summary、why、what changed、重要 implementation／validation note。\n\n## Commit message 規則\n\n- Commit message 必須詳盡，不可過短。\n- subject line 清楚說明 intent 與 affected area。\n- 非 trivial 變更優先採 multiline commit message。\n- body 摘要 what changed、why 需要此變更、重要 implementation 或 validation note。\n\n## 範例\n\n- Branch：`feat\u002Fadd-weekly-fatigue-summary`\n- PR title：`FEATURE: add weekly fatigue summary to coach report`\n- Branch：`fix\u002Fhandle-empty-garmin-heart-rate-payload`\n- PR title：`FIX: handle empty Garmin heart rate payload`\n- Branch：`docs\u002Fadd-shared-git-naming-conventions`\n- PR title：`DOCS: add shared Git naming conventions for branch, PR, and commits`\n\n## GitHub CLI environment\n\n所有 `gh` command 必須在 local host environment 執行，使用其 credential store 與 GitHub configuration。不可使用 sandboxed `gh` credential 或 fallback；local-host `gh` authentication 失敗時停止並回報 authentication blocker。\n\n## 使用 GitHub CLI 建立 PR\n\n使用 `gh` 建立 PR 時套用上述 convention：\n\n```bash\ngh pr create \\\n  --title \"TYPE: summary\" \\\n  --body \"## Summary\n\u003C這個 PR 做什麼>\n\n## Why\n\u003C為何需要此變更>\n\n## Changes\n- \u003Cfile\u002Farea>: \u003Cdescription>\n\n## Validation\n- \u003C執行的 test、manual check 或 screenshot>\" \\\n  --base main\n```\n\n- 不得使用 `--draft`；每個 PR 都必須可立即 review。\n- team 要求 reviewer 時加入 `--reviewer \u003Chandle>`。\n- 有 project label 時加入 `--label \u003Clabel>`。\n- PR title TYPE 必須用允許名稱，不可直接將 branch prefix 大寫：`feat`→`FEATURE`、`fix`→`FIX`、`refactor`→`REFACTOR`、`docs`→`DOCS`、`test`→`TEST`、`style`→`STYLE`、`perf`→`PERF`、`chore`→`CHORE`、`ci`→`CI`。\n\n## PR review follow-up\n\n完成要求的 PR review change 後，commit 並 push fix，再使用 PR 的 **Add a comment** action 發布 `@codex review`，要求 Codex reviewer 再次審查。\n\n## Output expectation\n\n- 被要求建立名稱時，提供精確符合 convention 的 branch 與 PR title。\n- 被要求 commit 時，依變更範圍撰寫詳盡 commit message，不用單行 shorthand。\n",{"name":5,"description":7},"main","41b33db37e0cff05594180ed30962ae769bb66f6",".agents\u002Fskills\u002Fgit-change-conventions","https:\u002F\u002Fgithub.com\u002FAndy-CH-BO-AN\u002Fplaywright-self-healing-tests","https:\u002F\u002Fgithub.com\u002FAndy-CH-BO-AN","2026-09-19 18:58:37",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add Andy-CH-BO-AN\u002Fplaywright-self-healing-tests --skill git-change-conventions",{"tool":35,"command":36},"bunx","bunx skills add Andy-CH-BO-AN\u002Fplaywright-self-healing-tests --skill git-change-conventions",{"tool":38,"command":39},"pnpm","pnpm dlx skills add Andy-CH-BO-AN\u002Fplaywright-self-healing-tests --skill git-change-conventions","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAndy-CH-BO-AN\u002Fplaywright-self-healing-tests\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgit-change-conventions\u002FSKILL.md",true,[43],{"path":44,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":47,"sourceHtmlUrl":48},"agents\u002Fopenai.yaml","REFERENCE","参考文档",278,"https:\u002F\u002Fgithub.com\u002FAndy-CH-BO-AN\u002Fplaywright-self-healing-tests\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgit-change-conventions\u002Fagents\u002Fopenai.yaml",[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":18},"01M7AASPR946YZRE5RF4A9Y712","readme-pm-review","僅在使用者明確要求以 product-manager 角度審查 repository README 時使用。先只讀 README，不推測未記錄功能，提供可讀性回饋、改寫建議與產品優先順序建議。","https:\u002F\u002Fgithub.com\u002FAndy-CH-BO-AN\u002Fplaywright-self-healing-tests\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Freadme-pm-review\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":18},"01M7AASN0CP3ET98VX899G692M","improve-codebase-architecture","掃描 codebase 的 deepening 機會，以視覺化 HTML report 呈現，並針對使用者選擇的項目進行 grilling。","https:\u002F\u002Fgithub.com\u002FAndy-CH-BO-AN\u002Fplaywright-self-healing-tests\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimprove-codebase-architecture\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M7AASKTD9ZN18D6NTKKW1MXH","handoff","將目前對話濃縮為可供下一位 agent 接手的交接文件。","https:\u002F\u002Fgithub.com\u002FAndy-CH-BO-AN\u002Fplaywright-self-healing-tests\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fhandoff\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M7AASJGF9S5PYDPX06TE8SAP","grilling","以密集提問檢驗使用者的計畫、決策或想法。使用者想壓力測試思考或使用任何「grill」觸發語時使用。","https:\u002F\u002Fgithub.com\u002FAndy-CH-BO-AN\u002Fplaywright-self-healing-tests\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgrilling\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M7AASH7K8B19AZ6Z5FF1TRDB","grill-with-docs","以密集訪談釐清並磨練計畫或設計，並同步建立 ADR 與 glossary 文件。","https:\u002F\u002Fgithub.com\u002FAndy-CH-BO-AN\u002Fplaywright-self-healing-tests\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgrill-with-docs\u002FSKILL.md",[],[],{"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":91,"publishedAt":18},"01M7AASG4404RPT22AMJX2PMP9","grill-me","以密集訪談釐清並磨練計畫或設計。","https:\u002F\u002Fgithub.com\u002FAndy-CH-BO-AN\u002Fplaywright-self-healing-tests\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgrill-me\u002FSKILL.md",[],[]]