Setting the skill. One moment.
Credited skills
54 skills · 155 min
Credited skills
Skill 29 of 54
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…
2 minutes · 420 words · 3 sections
Use this skill when reviewing or writing code in pkg/workflow/, actions/setup/js/, or compiled .lock.yml workflows that runs git, gh, or any other remote-touching operation against a repository checkout.
Each 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/checkout step (pkg/workflow/checkout_step_generator.go (opens in a new tab)). Generated checkouts always set persist-credentials: false, so the on-disk repo retains no credentials after the step finishes — only actions/checkout‘s own internal token is used during the clone, and it is scrubbed in its post-step.
A 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-tokens into downstream steps.
Two important contexts deliberately run with no git credentials:
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/push will fail for private repos.actions/checkout. The agent prompt in actions/setup/md/safe_outputs_push_to_pr_branch.md (opens in a new tab) 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.When you see a new git, gh, execFileSync('git'…), or compiled run: block:
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.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).try/catch, fail soft, and surface a clear “no credentials” error rather than a raw git stderr.git fetch --unshallow, --deepen=N) or widen (git fetch origin '+refs/heads/*') a sparse or shallow checkout of a large monorepo — these need credentials and can pull hundreds of MB. Prefer expanding fetch: / fetch-depth: / sparse-checkout: at compile time so it happens during actions/checkout with its internal token, never later.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.Credited
This skill is installed in github/gh-aw — in use here rather than published from here — so there is no install command for it on this page.
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.
The verbatim description from this skill’s front matter — the string an agent matches on to decide whether to load it.
main, last pushed 24 September 2026.SKILL.md, not by matching a directory convention. 4 distinct layouts observed: .claude/skills/*/SKILL.md, .github/skills/*/SKILL.md, .squad/*/skill.md, SKILL.md (repo root).h1 and no skipped levels:/github/gh-aw.md, and each skill at its own .md URL.