[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75P0Q9PMF5ESZBCBCFX9RSS":3,"skill-same:01M75P0Q9PMF5ESZBCBCFX9RSS":51},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":35,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M75P0Q9PMF5ESZBCBCFX9RSS","github-repo-workflow",null,"Use when editing a GitHub repository, opening or reviewing a PR, or operating on issues. Covers clone → branch → edit → commit → push → PR using pre-wired GH_TOKEN and git credentials.","pixeloven\u002Fcrew","pixeloven","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F5751260?v=4","01M75P0048G371B0AWRKQ7FJN8","PixelOven","01M75P0051RK1ZEY0SA9HCMX2Z",1,"MIT","https:\u002F\u002Fgithub.com\u002Fpixeloven\u002Fcrew\u002Fblob\u002Fmain\u002Fskills\u002Fgithub-repo-workflow\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: github-repo-workflow\ndescription: Use when editing a GitHub repository, opening or reviewing a PR, or operating on issues. Covers clone → branch → edit → commit → push → PR using pre-wired GH_TOKEN and git credentials.\ntier: subject\nrequires: [external:github]\nexpects-local: [secret-paths]\n---\n\n# GitHub Repo Workflow\n\nWhen a task requires editing a GitHub repo (manifests, configs, code), follow this end-to-end pattern: clone → branch → edit → commit → push → PR.\n\n## Auth is already wired\n\nYou don't need to set up credentials. The environment provides:\n\n- `GH_TOKEN` env var (injected from the project's secret manager)\n- `gh` CLI installed and authenticated against `GH_TOKEN`\n- git's credential helper for `https:\u002F\u002Fgithub.com` set to `gh auth git-credential` system-wide (`\u002Fetc\u002Fgitconfig`)\n- `safe.directory = *` set system-wide so cloned repos don't trigger ownership warnings\n\nPlain `git clone https:\u002F\u002Fgithub.com\u002F...` and `gh repo clone owner\u002Frepo` both authenticate transparently. Never embed tokens in remote URLs.\n\nThe GH_TOKEN's scope determines which repos you can reach (read\u002Fwrite). In a deployment's worker images, the token is typically an operator PAT sourced from the deployment's secret manager (the concrete reference belongs in its secret-paths local skill) and scoped to push\u002Fissue\u002FPR only for the intended organization.\n\n## Start in the workspace you were given\n\nIf a harness, CI job or supervising tool has already prepared a checkout (a worktree, a container checkout, the current directory), work there. A second copy elsewhere is one the host doesn't know about: its work is never reviewed, shipped or cleaned up.\n\nWhen the host's task contract defines delivery — who commits, pushes or opens the PR, and how — follow it over the steps below, per the reporting contract's *A supervising host's contract wins* rule.\n\nClone only when no workspace exists. Where the clone goes is the project's choice: check `AGENTS.md` for the canonical clone location and any pre-cloned paths.\n\n```bash\ngit clone https:\u002F\u002Fgithub.com\u002F\u003Cowner>\u002F\u003Crepo> \u003Cpath>\n# or, with the GitHub CLI\ngh repo clone \u003Cowner>\u002F\u003Crepo> \u003Cpath>\n```\n\n## Sync without discarding work\n\nThis applies only when starting new work. If the workspace is already on a branch prepared for the task, or the task is to continue an existing branch (such as addressing review comments on a PR), stay on that branch and skip this sync.\n\nAn existing checkout may hold uncommitted edits, a stash in progress, or local commits you can't see the value of. Check before you touch it:\n\n```bash\ngit status --porcelain                    # any output: the tree is dirty\ngit fetch origin main\ngit rev-list --count origin\u002Fmain..HEAD    # non-zero: local commits not on main\n```\n\nIf the tree is dirty or ahead, **stop and report** what you found; don't stash, reset or discard it. Otherwise branch from the fresh remote main and leave local `main` alone:\n\n```bash\ngit switch -c \u003Cbranch> origin\u002Fmain\n# edit files\n```\n\nNever `git reset --hard` or `git checkout -- .` to \"start fresh\". Both discard work with no prompt.\n\n## Name the branch\n\nUse the project's branch convention, from its `AGENTS.md` or a local skill. When it has none, use a prefix matching the change type: `fix\u002F`, `feat\u002F`, `chore\u002F`, `docs\u002F`, `refactor\u002F`.\n\n## Commit\n\nStage specific files, not the entire tree (`git add -A` can sweep in untracked content you didn't author).\n\n```bash\ngit add path\u002Fto\u002Ffile1 path\u002Fto\u002Ffile2\ngit commit -m \"$(cat \u003C\u003C'EOF'\n\u003Ctype>(\u003Cscope>): \u003Csubject>\n\n\u003Coptional body — why this change, not what>\nEOF\n)\"\n```\n\nThe heredoc form preserves multi-line formatting and avoids shell-escape hazards in the message body.\n\n## Push the branch\n\n```bash\ngit push -u origin \u003Cbranch>\n```\n\n## Open the PR\n\nThe commands below use the GitHub CLI (`cli:gh`). When it is absent, or the host gives GitHub through another tool, do the same operations through that tool; the steps and the marker rule are unchanged (see `docs\u002FCAPABILITIES.md` in the crew repo).\n\n```bash\ngh pr create --title \"\u003Ctype>(\u003Cscope>): \u003Csubject>\" --body \"$(cat \u003C\u003C'EOF'\n## Summary\n- \u003Cbullet>\n- \u003Cbullet>\n\n## Why\n\u003Cone paragraph rationale>\n\n## Test plan\n- [ ] \u003Cverification step>\n- [ ] \u003Cverification step>\nEOF\n)\"\n```\n\nThe PR URL is printed on stdout — capture it from the command output if you need to reference it in subsequent steps.\n\n## Mark what the agent writes\n\nEvery comment or review the agent posts on a PR or issue starts with a fixed marker, so readers can tell agent output from human output at a glance:\n\n```bash\ngh pr comment \u003CN> --body \"🤖 **Agent**: \u003Ccomment>\"\n```\n\n- **Never post agent output unmarked** — including a draft the operator approved without editing.\n- **Never mark human text.** When posting words the operator wrote, post them as theirs; mark only the agent's own additions.\n- Commits, titles and PR or issue bodies keep the project's own format and attribution convention; the marker is for comments and reviews.\n\n## Iterate on review\n\n```bash\ngh pr view \u003CN>                            # description + state + conversation\ngh pr checks \u003CN>                          # CI status rollup\ngh pr view \u003CN> --json reviews,comments    # programmatic check\ngh pr comment \u003CN> --body \"🤖 **Agent**: ...\"  # post a top-level comment (marked)\ngh api repos\u002F\u003Cowner>\u002F\u003Crepo>\u002Fpulls\u002F\u003CN>\u002Fcomments  # inline review comments\n```\n\nFor continuing work on an existing PR (e.g., addressing review feedback):\n\n```bash\ngh pr checkout \u003CN>                        # local-checkout the PR's branch\n# edit, git add, git commit\ngit push                                  # pushes to the PR's branch\n```\n\n## Issues\n\n```bash\ngh issue create --title \"...\" --body \"$(cat \u003C\u003C'EOF'\n...\nEOF\n)\" --label \u003Clabel1>,\u003Clabel2>\n\ngh issue view \u003CN>                         # full body + labels + state\ngh issue comment \u003CN> --body \"🤖 **Agent**: ...\"  # update with progress (marked)\ngh issue edit \u003CN> --add-label \u003Clabel>     # routing labels (e.g. `agent:queued`)\ngh issue close \u003CN> --reason completed     # close with a reason\n```\n\n## What not to do\n\n- **Don't `git reset --hard`** an existing checkout. When starting new work there, if it is dirty or ahead of `origin\u002Fmain`, stop and report.\n- **Don't `--no-verify`** to skip pre-commit hooks. Hooks catch secrets, formatting, and lint issues — investigate failures, don't bypass.\n- **Don't `git add -A`** in repos with untracked files you didn't create. Add specific paths.\n- **Don't force-push** a branch with reviews unless rebase is the explicit intent. Push new commits instead.\n- **Don't commit secrets**. Treat `.env`, `*.key`, and anything with `secret` in its name as suspect.\n- **Don't embed `GH_TOKEN` in URLs or commit messages.** The credential helper handles auth invisibly.\n","# GitHub Repo Workflow\n\nWhen a task requires editing a GitHub repo (manifests, configs, code), follow this end-to-end pattern: clone → branch → edit → commit → push → PR.\n\n## Auth is already wired\n\nYou don't need to set up credentials. The environment provides:\n\n- `GH_TOKEN` env var (injected from the project's secret manager)\n- `gh` CLI installed and authenticated against `GH_TOKEN`\n- git's credential helper for `https:\u002F\u002Fgithub.com` set to `gh auth git-credential` system-wide (`\u002Fetc\u002Fgitconfig`)\n- `safe.directory = *` set system-wide so cloned repos don't trigger ownership warnings\n\nPlain `git clone https:\u002F\u002Fgithub.com\u002F...` and `gh repo clone owner\u002Frepo` both authenticate transparently. Never embed tokens in remote URLs.\n\nThe GH_TOKEN's scope determines which repos you can reach (read\u002Fwrite). In a deployment's worker images, the token is typically an operator PAT sourced from the deployment's secret manager (the concrete reference belongs in its secret-paths local skill) and scoped to push\u002Fissue\u002FPR only for the intended organization.\n\n## Start in the workspace you were given\n\nIf a harness, CI job or supervising tool has already prepared a checkout (a worktree, a container checkout, the current directory), work there. A second copy elsewhere is one the host doesn't know about: its work is never reviewed, shipped or cleaned up.\n\nWhen the host's task contract defines delivery — who commits, pushes or opens the PR, and how — follow it over the steps below, per the reporting contract's *A supervising host's contract wins* rule.\n\nClone only when no workspace exists. Where the clone goes is the project's choice: check `AGENTS.md` for the canonical clone location and any pre-cloned paths.\n\n```bash\ngit clone https:\u002F\u002Fgithub.com\u002F\u003Cowner>\u002F\u003Crepo> \u003Cpath>\n# or, with the GitHub CLI\ngh repo clone \u003Cowner>\u002F\u003Crepo> \u003Cpath>\n```\n\n## Sync without discarding work\n\nThis applies only when starting new work. If the workspace is already on a branch prepared for the task, or the task is to continue an existing branch (such as addressing review comments on a PR), stay on that branch and skip this sync.\n\nAn existing checkout may hold uncommitted edits, a stash in progress, or local commits you can't see the value of. Check before you touch it:\n\n```bash\ngit status --porcelain                    # any output: the tree is dirty\ngit fetch origin main\ngit rev-list --count origin\u002Fmain..HEAD    # non-zero: local commits not on main\n```\n\nIf the tree is dirty or ahead, **stop and report** what you found; don't stash, reset or discard it. Otherwise branch from the fresh remote main and leave local `main` alone:\n\n```bash\ngit switch -c \u003Cbranch> origin\u002Fmain\n# edit files\n```\n\nNever `git reset --hard` or `git checkout -- .` to \"start fresh\". Both discard work with no prompt.\n\n## Name the branch\n\nUse the project's branch convention, from its `AGENTS.md` or a local skill. When it has none, use a prefix matching the change type: `fix\u002F`, `feat\u002F`, `chore\u002F`, `docs\u002F`, `refactor\u002F`.\n\n## Commit\n\nStage specific files, not the entire tree (`git add -A` can sweep in untracked content you didn't author).\n\n```bash\ngit add path\u002Fto\u002Ffile1 path\u002Fto\u002Ffile2\ngit commit -m \"$(cat \u003C\u003C'EOF'\n\u003Ctype>(\u003Cscope>): \u003Csubject>\n\n\u003Coptional body — why this change, not what>\nEOF\n)\"\n```\n\nThe heredoc form preserves multi-line formatting and avoids shell-escape hazards in the message body.\n\n## Push the branch\n\n```bash\ngit push -u origin \u003Cbranch>\n```\n\n## Open the PR\n\nThe commands below use the GitHub CLI (`cli:gh`). When it is absent, or the host gives GitHub through another tool, do the same operations through that tool; the steps and the marker rule are unchanged (see `docs\u002FCAPABILITIES.md` in the crew repo).\n\n```bash\ngh pr create --title \"\u003Ctype>(\u003Cscope>): \u003Csubject>\" --body \"$(cat \u003C\u003C'EOF'\n## Summary\n- \u003Cbullet>\n- \u003Cbullet>\n\n## Why\n\u003Cone paragraph rationale>\n\n## Test plan\n- [ ] \u003Cverification step>\n- [ ] \u003Cverification step>\nEOF\n)\"\n```\n\nThe PR URL is printed on stdout — capture it from the command output if you need to reference it in subsequent steps.\n\n## Mark what the agent writes\n\nEvery comment or review the agent posts on a PR or issue starts with a fixed marker, so readers can tell agent output from human output at a glance:\n\n```bash\ngh pr comment \u003CN> --body \"🤖 **Agent**: \u003Ccomment>\"\n```\n\n- **Never post agent output unmarked** — including a draft the operator approved without editing.\n- **Never mark human text.** When posting words the operator wrote, post them as theirs; mark only the agent's own additions.\n- Commits, titles and PR or issue bodies keep the project's own format and attribution convention; the marker is for comments and reviews.\n\n## Iterate on review\n\n```bash\ngh pr view \u003CN>                            # description + state + conversation\ngh pr checks \u003CN>                          # CI status rollup\ngh pr view \u003CN> --json reviews,comments    # programmatic check\ngh pr comment \u003CN> --body \"🤖 **Agent**: ...\"  # post a top-level comment (marked)\ngh api repos\u002F\u003Cowner>\u002F\u003Crepo>\u002Fpulls\u002F\u003CN>\u002Fcomments  # inline review comments\n```\n\nFor continuing work on an existing PR (e.g., addressing review feedback):\n\n```bash\ngh pr checkout \u003CN>                        # local-checkout the PR's branch\n# edit, git add, git commit\ngit push                                  # pushes to the PR's branch\n```\n\n## Issues\n\n```bash\ngh issue create --title \"...\" --body \"$(cat \u003C\u003C'EOF'\n...\nEOF\n)\" --label \u003Clabel1>,\u003Clabel2>\n\ngh issue view \u003CN>                         # full body + labels + state\ngh issue comment \u003CN> --body \"🤖 **Agent**: ...\"  # update with progress (marked)\ngh issue edit \u003CN> --add-label \u003Clabel>     # routing labels (e.g. `agent:queued`)\ngh issue close \u003CN> --reason completed     # close with a reason\n```\n\n## What not to do\n\n- **Don't `git reset --hard`** an existing checkout. When starting new work there, if it is dirty or ahead of `origin\u002Fmain`, stop and report.\n- **Don't `--no-verify`** to skip pre-commit hooks. Hooks catch secrets, formatting, and lint issues — investigate failures, don't bypass.\n- **Don't `git add -A`** in repos with untracked files you didn't create. Add specific paths.\n- **Don't force-push** a branch with reviews unless rebase is the explicit intent. Push new commits instead.\n- **Don't commit secrets**. Treat `.env`, `*.key`, and anything with `secret` in its name as suspect.\n- **Don't embed `GH_TOKEN` in URLs or commit messages.** The credential helper handles auth invisibly.\n",{"name":5,"tier":24,"requires":25,"description":7,"expects-local":27},"subject",[26],"external:github",[28],"secret-paths","main","686d42537f9efddb1aeece969b1a4fee2e4d1a88","skills\u002Fgithub-repo-workflow",0,"https:\u002F\u002Fgithub.com\u002Fpixeloven\u002Fcrew","https:\u002F\u002Fgithub.com\u002Fpixeloven","www.pixeloven.com","2026-11-07 09:18:41",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add pixeloven\u002Fcrew --skill github-repo-workflow",{"tool":43,"command":44},"bunx","bunx skills add pixeloven\u002Fcrew --skill github-repo-workflow",{"tool":46,"command":47},"pnpm","pnpm dlx skills add pixeloven\u002Fcrew --skill github-repo-workflow","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpixeloven\u002Fcrew\u002Fblob\u002Fmain\u002Fskills\u002Fgithub-repo-workflow\u002FSKILL.md",true,[],[52,59,66,73,79,85],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M75P2X72QCY4H2H6C7D3KQ1Z","orchard-gh-runs","Use when reading a failed GitHub Actions run with the gh CLI in this project, before re-running it or reporting a CI failure, so the failing step's log is read instead of the whole run.","https:\u002F\u002Fgithub.com\u002Fpixeloven\u002Fcrew\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fproposals\u002Forchard\u002F.agents\u002Fskills\u002Forchard-gh-runs\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M75P2T76B22B314Q3W25GDCK","orchard-gh","Hand-edited after promotion; the learned marker was dropped, so Doctor and check_skills --local can no longer see it.","https:\u002F\u002Fgithub.com\u002Fpixeloven\u002Fcrew\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fproposals\u002Finvalid\u002F.agents\u002Fskills\u002Forchard-gh\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M75P2Q410WX0H3ZZ61R210F4","demo-topology","Use when exercising the inventory contract fixture so that this fixture description comfortably clears the schema-v2 minimum length.","https:\u002F\u002Fgithub.com\u002Fpixeloven\u002Fcrew\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finventory\u002Fproject\u002F.agents\u002Fskills\u002Fdemo-topology\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M75P2KTWZ94KNSKHPGFB6Y6J","helper-jq","https:\u002F\u002Fgithub.com\u002Fpixeloven\u002Fcrew\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finventory\u002Fhome\u002F.codex\u002Fplugins\u002Fcache\u002Facme\u002Fhelper\u002F2.0.0\u002Fskills\u002Fhelper-jq\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M75P2GT2CXZR4EZE2DS9GTS7","user-notes","https:\u002F\u002Fgithub.com\u002Fpixeloven\u002Fcrew\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finventory\u002Fhome\u002F.claude\u002Fskills\u002Fuser-notes\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M75P2D61GDSH9NFNEBV4HDBS","toolkit-gh","https:\u002F\u002Fgithub.com\u002Fpixeloven\u002Fcrew\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finventory\u002Fhome\u002F.claude\u002Fplugins\u002Fcache\u002Facme\u002Ftoolkit\u002F1.2.0\u002Fskills\u002Ftoolkit-gh\u002FSKILL.md",[],[]]