[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AD47FND6TESXRBS4PAKGFD":3,"skill-same:01M6AD47FND6TESXRBS4PAKGFD":62},{"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":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":38,"commitSha":39,"skillDirectory":40,"forksCount":41,"repositoryHtmlUrl":42,"repositoryHomepageUrl":43,"ownerHtmlUrl":44,"ownerBlogUrl":45,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M6AD47FND6TESXRBS4PAKGFD","checkout-credential-review",null,"Review code that performs git or gh operations against repository checkouts in gh-aw, checking that the right credentials are available at the right time and that sparseness, shallowness and credential-free factors are properly considered.","github\u002Fgh-aw","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3VCZ4WKQSFSRTPN7N9DN",5636,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcheckout-credential-review\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32],"review","checkout credential review","credential","checkout","code","git","repository","credentials","review code","gh","operations","time","free","at","2026-11-10 10:12:30",false,"---\nname: checkout-credential-review\ndescription: Review code that performs git or gh operations against repository checkouts in gh-aw, checking that the right credentials are available at the right time and that sparseness, shallowness and credential-free factors are properly considered.\n---\n\n# Checkout Credential Review\n\nUse this skill when reviewing or writing code in `pkg\u002Fworkflow\u002F`, `actions\u002Fsetup\u002Fjs\u002F`, or compiled `.lock.yml` workflows that runs `git`, `gh`, or any other remote-touching operation against a repository checkout.\n\n## Background\n\nEach entry in a workflow's `checkout:` block may declare its own credentials (`github-token:`, `github-app:`), and the compiler wires those into the corresponding `actions\u002Fcheckout` step ([pkg\u002Fworkflow\u002Fcheckout_step_generator.go](..\u002F..\u002F..\u002Fpkg\u002Fworkflow\u002Fcheckout_step_generator.go)). Generated checkouts always set `persist-credentials: false`, so the on-disk repo retains **no** credentials after the step finishes — only `actions\u002Fcheckout`'s own internal token is used during the clone, and it is scrubbed in its post-step.\n\nA separate step that wants to authenticate later must either (a) re-inject a token at command level (e.g. `git -c http.extraheader=...`) or (b) be passed the per-checkout token via env. The compiler does *not* automatically thread per-checkout `github-token`s into downstream steps.\n\nTwo important contexts deliberately run with **no git credentials**:\n\n- The **safe-outputs MCP server** and its handlers (`generate_git_bundle.cjs`, `generate_git_patch.cjs`, `create_pull_request.cjs`). Errors in these paths explicitly say \"the safe-outputs MCP server has no credentials for private repositories\" — fetch\u002Fpush will fail for private repos.\n- The **agent runtime** after `actions\u002Fcheckout`. The agent prompt in [actions\u002Fsetup\u002Fmd\u002Fsafe_outputs_push_to_pr_branch.md](..\u002F..\u002F..\u002Factions\u002Fsetup\u002Fmd\u002Fsafe_outputs_push_to_pr_branch.md) explicitly tells the model not to attempt `git fetch`, `git pull`, `git push`, or any other authenticated git operation, and to report unavailable branches rather than try to fetch them.\n\n## Review checklist\n\nWhen you see a new `git`, `gh`, `execFileSync('git'…)`, or compiled `run:` block:\n\n1. **Does it touch a remote?** Local-only commands (`symbolic-ref`, `rev-parse`, `log`, `show`, `merge-base`, `diff`, `status`) need no credentials. Anything in `fetch | pull | push | clone | ls-remote | remote (set-url|add|update)` does, plus on-demand blob fetches in partial clones.\n2. **Which checkout is it operating on?** If it's a cross-repo entry from `checkout:`, the relevant credential is *that entry's* `github-token`, not the workflow's default `GITHUB_TOKEN`. Confirm the per-entry token is actually threaded into the step's env (or refuse to do remote operations and degrade gracefully).\n3. **Which job\u002Fcontext emits it?** Agent job and safe-outputs MCP server both run without git credentials by design. Any remote git operation there must be wrapped in `try\u002Fcatch`, fail soft, and surface a clear \"no credentials\" error rather than a raw git stderr.\n4. **Sparse \u002F shallow \u002F monorepo concerns.** Avoid emitting steps that deepen (`git fetch --unshallow`, `--deepen=N`) or widen (`git fetch origin '+refs\u002Fheads\u002F*'`) a sparse or shallow checkout of a large monorepo — these need credentials *and* can pull hundreds of MB. Prefer expanding `fetch:` \u002F `fetch-depth:` \u002F `sparse-checkout:` at compile time so it happens during `actions\u002Fcheckout` with its internal token, never later.\n5. **`gh` is REST, not git.** `gh api …` uses whatever `GH_TOKEN` is in the step's env — it does **not** automatically inherit per-checkout PATs. For cross-org private repos, either thread the right token in or accept the call will 404 and handle it.\n\n## Related\n\n- [docs\u002Fsrc\u002Fcontent\u002Fdocs\u002Freference\u002Fcheckout.md](..\u002F..\u002F..\u002Fdocs\u002Fsrc\u002Fcontent\u002Fdocs\u002Freference\u002Fcheckout.md) — \"Git Credentials After Checkout\"\n- [docs\u002Fsparseness.md](..\u002F..\u002F..\u002Fdocs\u002Fsparseness.md) — sparse\u002Fblobless credential lifecycle\n- [pkg\u002Fworkflow\u002Fcheckout_step_generator.go](..\u002F..\u002F..\u002Fpkg\u002Fworkflow\u002Fcheckout_step_generator.go) — token wiring per checkout\n- [actions\u002Fsetup\u002Fmd\u002Fsafe_outputs_push_to_pr_branch.md](..\u002F..\u002F..\u002Factions\u002Fsetup\u002Fmd\u002Fsafe_outputs_push_to_pr_branch.md) — agent-facing guidance\n","# Checkout Credential Review\n\nUse this skill when reviewing or writing code in `pkg\u002Fworkflow\u002F`, `actions\u002Fsetup\u002Fjs\u002F`, or compiled `.lock.yml` workflows that runs `git`, `gh`, or any other remote-touching operation against a repository checkout.\n\n## Background\n\nEach entry in a workflow's `checkout:` block may declare its own credentials (`github-token:`, `github-app:`), and the compiler wires those into the corresponding `actions\u002Fcheckout` step ([pkg\u002Fworkflow\u002Fcheckout_step_generator.go](..\u002F..\u002F..\u002Fpkg\u002Fworkflow\u002Fcheckout_step_generator.go)). Generated checkouts always set `persist-credentials: false`, so the on-disk repo retains **no** credentials after the step finishes — only `actions\u002Fcheckout`'s own internal token is used during the clone, and it is scrubbed in its post-step.\n\nA separate step that wants to authenticate later must either (a) re-inject a token at command level (e.g. `git -c http.extraheader=...`) or (b) be passed the per-checkout token via env. The compiler does *not* automatically thread per-checkout `github-token`s into downstream steps.\n\nTwo important contexts deliberately run with **no git credentials**:\n\n- The **safe-outputs MCP server** and its handlers (`generate_git_bundle.cjs`, `generate_git_patch.cjs`, `create_pull_request.cjs`). Errors in these paths explicitly say \"the safe-outputs MCP server has no credentials for private repositories\" — fetch\u002Fpush will fail for private repos.\n- The **agent runtime** after `actions\u002Fcheckout`. The agent prompt in [actions\u002Fsetup\u002Fmd\u002Fsafe_outputs_push_to_pr_branch.md](..\u002F..\u002F..\u002Factions\u002Fsetup\u002Fmd\u002Fsafe_outputs_push_to_pr_branch.md) explicitly tells the model not to attempt `git fetch`, `git pull`, `git push`, or any other authenticated git operation, and to report unavailable branches rather than try to fetch them.\n\n## Review checklist\n\nWhen you see a new `git`, `gh`, `execFileSync('git'…)`, or compiled `run:` block:\n\n1. **Does it touch a remote?** Local-only commands (`symbolic-ref`, `rev-parse`, `log`, `show`, `merge-base`, `diff`, `status`) need no credentials. Anything in `fetch | pull | push | clone | ls-remote | remote (set-url|add|update)` does, plus on-demand blob fetches in partial clones.\n2. **Which checkout is it operating on?** If it's a cross-repo entry from `checkout:`, the relevant credential is *that entry's* `github-token`, not the workflow's default `GITHUB_TOKEN`. Confirm the per-entry token is actually threaded into the step's env (or refuse to do remote operations and degrade gracefully).\n3. **Which job\u002Fcontext emits it?** Agent job and safe-outputs MCP server both run without git credentials by design. Any remote git operation there must be wrapped in `try\u002Fcatch`, fail soft, and surface a clear \"no credentials\" error rather than a raw git stderr.\n4. **Sparse \u002F shallow \u002F monorepo concerns.** Avoid emitting steps that deepen (`git fetch --unshallow`, `--deepen=N`) or widen (`git fetch origin '+refs\u002Fheads\u002F*'`) a sparse or shallow checkout of a large monorepo — these need credentials *and* can pull hundreds of MB. Prefer expanding `fetch:` \u002F `fetch-depth:` \u002F `sparse-checkout:` at compile time so it happens during `actions\u002Fcheckout` with its internal token, never later.\n5. **`gh` is REST, not git.** `gh api …` uses whatever `GH_TOKEN` is in the step's env — it does **not** automatically inherit per-checkout PATs. For cross-org private repos, either thread the right token in or accept the call will 404 and handle it.\n\n## Related\n\n- [docs\u002Fsrc\u002Fcontent\u002Fdocs\u002Freference\u002Fcheckout.md](..\u002F..\u002F..\u002Fdocs\u002Fsrc\u002Fcontent\u002Fdocs\u002Freference\u002Fcheckout.md) — \"Git Credentials After Checkout\"\n- [docs\u002Fsparseness.md](..\u002F..\u002F..\u002Fdocs\u002Fsparseness.md) — sparse\u002Fblobless credential lifecycle\n- [pkg\u002Fworkflow\u002Fcheckout_step_generator.go](..\u002F..\u002F..\u002Fpkg\u002Fworkflow\u002Fcheckout_step_generator.go) — token wiring per checkout\n- [actions\u002Fsetup\u002Fmd\u002Fsafe_outputs_push_to_pr_branch.md](..\u002F..\u002F..\u002Factions\u002Fsetup\u002Fmd\u002Fsafe_outputs_push_to_pr_branch.md) — agent-facing guidance\n",{"name":5,"description":7},"main","8541229759617347888641eba917d3b0ad66a984",".github\u002Fskills\u002Fcheckout-credential-review",626,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw","https:\u002F\u002Fgh.io\u002Fgh-aw","https:\u002F\u002Fgithub.com\u002Fgithub","https:\u002F\u002Fgithub.com\u002Fabout","How people build software.","2026-11-15 06:45:15",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add github\u002Fgh-aw --skill checkout-credential-review",{"tool":54,"command":55},"bunx","bunx skills add github\u002Fgh-aw --skill checkout-credential-review",{"tool":57,"command":58},"pnpm","pnpm dlx skills add github\u002Fgh-aw --skill checkout-credential-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcheckout-credential-review\u002FSKILL.md",true,[],[63,71,79,107,124,149],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":70},"01M7DQYVZ9W9DDXKQ9452SNP8J","cracktro","Edit, preview, and verify the standalone interactive talk deck in docs\u002Fpublic\u002Fcracktro (slides, SVG diagrams, transitions, WebAudio sound).","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcracktro\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":78},"01M7612HQ4378TK8QZ5HPAF4KR","create-connector","Create or extend a declaration-only third-party connector, with narrow reads, separate safe outputs, optional protected triggers, and offline conformance evidence.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcreate-connector\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":93,"publishedAt":33},"01M6ADC942STTXHFV410J4DH0X","GitHub Agentic Workflows","GitHub Agentic Workflows (`gh-aw`) is a GitHub CLI extension for writing Agentic Workflows in markdown and compiling them to GitHub Actions.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002FSKILL.md",[85,90],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",{"categoryNo":91,"categoryName":92,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000023","Skill与智能体开发",[9,94,95,96,97,98,99,100,101,28,102,103,104,105,106],"github agentic workflows","agentic workflows","workflows","agentic","extension","markdown","github cli","cli","for","compiling","writing","github actions","actions",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":33},"01M6ADC6ZXSA46N9XD6VNAP1MS","windows-compatibility","Cross-platform path handling and command patterns","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Fwindows-compatibility\u002FSKILL.md",[],[114,115,116,117,24,118,119,120,121,122,123],"windows","windows compatibility","compatibility","command","bugs","platform","high","patterns","cross-platform","path",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":33},"01M6ADC44957SVQF96R5YY247P","versioning-policy","Semver versioning rules for Squad SDK and CLI — prevents prerelease version incidents","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Fversioning-policy\u002FSKILL.md",[],[131,132,133,134,135,101,136,137,138,139,140,141,142,143,102,144,145,146,147,148],"versioning","policy","versioning policy","gate","implementation","workspace","pr","sdk","release","ci","npm","semver","squad","incident","incidents","Rules","version","resolution",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":159,"publishedAt":33},"01M6ADC1PHMEAEVR87F8PDR89X","tiered-memory","Three-tier agent memory model (hot\u002Fcold\u002Fwiki) for context reduction per spawn","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Ftiered-memory\u002FSKILL.md",[155,158],{"categoryNo":156,"categoryName":157,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":91,"categoryName":92,"taxonomyType":88,"taxonomyTypeDesc":89},[160,161,162,163,164,165,166,167,168,169,170,171,172,102,173,174],"tiered memory","memory","performance","design","agent memory","proposal","cold","model","wiki","spawn","memory-management","context","three","runtime","management"]