[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71K3ZZD3EBBAH4F72AX8YF9":3,"skill-same:01M71K3ZZD3EBBAH4F72AX8YF9":78},{"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":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":13,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":53,"install":54,"resources":67},"01M71K3ZZD3EBBAH4F72AX8YF9","gh-first-workflow",null,"Enforce gh-first GitHub investigation, pull request maintenance, and Conventional Commit output rules. Use when investigating GitHub issues or pull requests, creating or updating pull requests, summarizing investigation results, or preparing commit messages.","mryfmo\u002Fdotfiles","mryfmo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F11512262?v=4","01M71K2RDZFFQKYGMHMS5Y9PW1","01M71K2REKJ0WS61PNFQPTYP5T",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Fhome\u002Fdot_agents\u002Fskills\u002Fgh-first-workflow\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"workflow","gh first workflow","gh","first","pull request","issues","pull","messages","commit","pull requests","Rules","results","use","maintenance","enforce","output","requests","request","when","github","2026-11-10 10:12:30",false,"---\nname: gh-first-workflow\ndescription: Enforce gh-first GitHub investigation, pull request maintenance, and Conventional Commit output rules. Use when investigating GitHub issues or pull requests, creating or updating pull requests, summarizing investigation results, or preparing commit messages.\n---\n\n# GH-First Workflow\n\n## Overview\n\nUse this workflow to keep GitHub investigation and commit output consistent with repository policy.\nFor pull requests, keep the description aligned with the full current PR contents, not just the latest delta.\n\n## Read Acknowledgement\n\n- After reading this skill, say: `🐙 私は gh-first-workflow を読みました。`\n\n## Workflow\n\n1. Start issue\u002FPR investigation with `gh` commands.\n2. Use `web` only when `gh` cannot provide required details.\n3. Collect URLs for every issue\u002FPR that was inspected.\n4. When creating a PR, write the PR description as a summary of the full PR.\n5. If additional commits are pushed after PR creation, inspect the updated commits\u002Fdiff with `gh` and refresh the PR description so it reflects the full current PR, not only the latest increment.\n6. Include inspected URLs in the response.\n7. Write commit messages in Conventional Commit format.\n8. Before merging or accepting a PR in a repository that has a program store (`.orchestration\u002Forchestrate\u002F\u003Cprogram>\u002F`), follow the `hcom-orchestration` SKILL's loop: a verdict row for the head sha, CI green, every bot finding fixed at root cause or dismissed with a pasted refutation, then the squash merge pinned to that head sha (`--match-head-commit`). In any other repository, follow that repository's own merge rules.\n\n## Output Checklist\n\n- State that `gh` was used first.\n- State why `web` was used when fallback was necessary.\n- Include inspected issue\u002FPR URLs.\n- When commits were added after PR creation, confirm the PR description was updated to match the full current PR.\n- Keep commit subject in Conventional Commit form: `\u003Ctype>(\u003Cscope>): \u003Csummary>`.\n- Before a merge in a repository with a program store: every bot finding, including any CodeRabbit review and every `failure` and `warning` annotation, is fixed at root cause or dismissed with a pasted refutation; a bot review is optional and not gated. Elsewhere, the repository's own merge rules apply.\n- Do NOT include local absolute file paths (e.g., `\u002FUsers\u002F...\u002F`, `\u002Fhome\u002F...\u002F`) in any output. Use repository-relative paths instead.\n\nUse [gh-git-rules.md](references\u002Fgh-git-rules.md) for command examples and commit-type guidance.\n","# GH-First Workflow\n\n## Overview\n\nUse this workflow to keep GitHub investigation and commit output consistent with repository policy.\nFor pull requests, keep the description aligned with the full current PR contents, not just the latest delta.\n\n## Read Acknowledgement\n\n- After reading this skill, say: `🐙 私は gh-first-workflow を読みました。`\n\n## Workflow\n\n1. Start issue\u002FPR investigation with `gh` commands.\n2. Use `web` only when `gh` cannot provide required details.\n3. Collect URLs for every issue\u002FPR that was inspected.\n4. When creating a PR, write the PR description as a summary of the full PR.\n5. If additional commits are pushed after PR creation, inspect the updated commits\u002Fdiff with `gh` and refresh the PR description so it reflects the full current PR, not only the latest increment.\n6. Include inspected URLs in the response.\n7. Write commit messages in Conventional Commit format.\n8. Before merging or accepting a PR in a repository that has a program store (`.orchestration\u002Forchestrate\u002F\u003Cprogram>\u002F`), follow the `hcom-orchestration` SKILL's loop: a verdict row for the head sha, CI green, every bot finding fixed at root cause or dismissed with a pasted refutation, then the squash merge pinned to that head sha (`--match-head-commit`). In any other repository, follow that repository's own merge rules.\n\n## Output Checklist\n\n- State that `gh` was used first.\n- State why `web` was used when fallback was necessary.\n- Include inspected issue\u002FPR URLs.\n- When commits were added after PR creation, confirm the PR description was updated to match the full current PR.\n- Keep commit subject in Conventional Commit form: `\u003Ctype>(\u003Cscope>): \u003Csummary>`.\n- Before a merge in a repository with a program store: every bot finding, including any CodeRabbit review and every `failure` and `warning` annotation, is fixed at root cause or dismissed with a pasted refutation; a bot review is optional and not gated. Elsewhere, the repository's own merge rules apply.\n- Do NOT include local absolute file paths (e.g., `\u002FUsers\u002F...\u002F`, `\u002Fhome\u002F...\u002F`) in any output. Use repository-relative paths instead.\n\nUse [gh-git-rules.md](references\u002Fgh-git-rules.md) for command examples and commit-type guidance.\n",{"name":5,"description":7},"main","af601a97567f1f07e9337cad899506f601f419f1","home\u002Fdot_agents\u002Fskills\u002Fgh-first-workflow","https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles","https:\u002F\u002Fgithub.com\u002Fmryfmo","2026-11-11 10:15:31",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add mryfmo\u002Fdotfiles --skill gh-first-workflow",{"tool":60,"command":61},"bunx","bunx skills add mryfmo\u002Fdotfiles --skill gh-first-workflow",{"tool":63,"command":64},"pnpm","pnpm dlx skills add mryfmo\u002Fdotfiles --skill gh-first-workflow","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Fhome\u002Fdot_agents\u002Fskills\u002Fgh-first-workflow\u002FSKILL.md",true,[68,74],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"agents\u002Fopenai.yaml","REFERENCE","参考文档",276,"https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Fhome\u002Fdot_agents\u002Fskills\u002Fgh-first-workflow\u002Fagents\u002Fopenai.yaml",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fgh-git-rules.md",1259,"https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Fhome\u002Fdot_agents\u002Fskills\u002Fgh-first-workflow\u002Freferences\u002Fgh-git-rules.md",[79,85,91,121,143,162],{"skillNo":80,"name":81,"nameZh":6,"description":6,"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":43},"01M71K61D634ATEV8NWTGGWNGS","x","https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fponytail\u002Fskills\u002Fx\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":43},"01M71K605VRE3ABPN1MZHJNZ29","y","https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fponytail\u002Fdocs\u002Fskills\u002Fy\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":102,"publishedAt":43},"01M71K5Y3XX1PYZAWA7M5RG9VD","status-report","Generate a status report with KPIs, risks, and action items. Use when writing a weekly or monthly update for leadership, summarizing project health with green\u002Fyellow\u002Fred status, surfacing risks and decisions that need stakeholder attention, or turning a pile of project tracker activity into a readable narrative.","https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fkwp-upstream\u002Foperations\u002Fskills\u002Fstatus-report\u002FSKILL.md",[97],{"categoryNo":98,"categoryName":99,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,35,41,118,119,120],"status report","report","status","tracker","health","generate","leadership","narrative","with","weekly","attention","green","for","project","writing","decisions","team","project health",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":43},"01M71K5VJAHGE1NH22BGBXP693","runbook","Create or update an operational runbook for a recurring task or procedure. Use when documenting a task that on-call or ops needs to run repeatably, turning tribal knowledge into exact step-by-step commands, adding troubleshooting and rollback steps to an existing procedure, or writing escalation paths for when things go wrong.","https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fkwp-upstream\u002Foperations\u002Fskills\u002Frunbook\u002FSKILL.md",[],[123,128,129,130,131,132,133,134,135,41,136,137,35,117,138,139,115,140,141,142],"task","update","name","run","process","operational","create","call","ops","Existing","knowledge","rollback","escalation","recurring","things",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":43},"01M71K5SJ0FT7KD82E7PJCGATX","risk-assessment","Identify, assess, and mitigate operational risks. Trigger with \"what are the risks\", \"risk assessment\", \"risk register\", \"what could go wrong\", or when the user is evaluating risks associated with a project, vendor, process, or decision.","https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fkwp-upstream\u002Foperations\u002Fskills\u002Frisk-assessment\u002FSKILL.md",[],[150,151,152,111,153,154,155,41,156,157,158,159,160,132,116,133,161],"risk assessment","assessment","risk","decision","user","Wrong","go","assess","trigger","risk register","vendor","register",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":168,"publishedAt":43},"01M71K5PYD2A2BDM6KMZ8F01SV","change-request","Create a change management request with impact analysis and rollback plan. Use when proposing a system or process change that needs approval, preparing a change record for CAB review, documenting risk and rollback steps before a deployment, or planning stakeholder communications for a rollout.","https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fkwp-upstream\u002Foperations\u002Fskills\u002Fchange-request\u002FSKILL.md",[],[40,169,170,35,111,171,172,173,174,175,176,41,177,178,179,180,181,115,182,152],"change request","change","communications","stakeholder communications","review","rollback plan","analysis","rollout","impact","change management","impact analysis","system","deployment","planning"]