[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75X8555BMKHRF7GD86AM188":3,"skill-same:01M75X8555BMKHRF7GD86AM188":74},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":47},"01M75X8555BMKHRF7GD86AM188","setup-matt-pocock-skills",null,"Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.","mambo-wang\u002FCodeWiki-Plus","mambo-wang","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F17296917?v=4","01M75489WXT2KCG0TDVRGMTEET","WanderingBug","01M75WY0F23J9DB5GBVTH8F8Q9",21,"MIT","https:\u002F\u002Fgithub.com\u002Fmambo-wang\u002FCodeWiki-Plus\u002Fblob\u002Fdevelop\u002F.trae\u002Fskills\u002Fsetup-matt-pocock-skills\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: setup-matt-pocock-skills\ndescription: \"Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.\"\ndisable-model-invocation: true\n---\n\n# Setup Matt Pocock's Skills\n\nScaffold the per-repo configuration that the engineering skills assume:\n\n- **Issue tracker**: where issues live (GitHub by default; local markdown is also supported out of the box)\n- **Triage labels**: the strings used for the five canonical triage roles\n- **Domain docs**: where `CONTEXT.md` and ADRs live, and the consumer rules for reading them\n\nThis is a prompt-driven skill, not a deterministic script. Explore, present what you found, confirm with the user, then write.\n\n## Process\n\n### 1. Explore\n\nLook at the current repo to understand its starting state. Read whatever exists; don't assume:\n\n- `git remote -v` and `.git\u002Fconfig`: is this a GitHub repo? Which one?\n- `AGENTS.md` and `CLAUDE.md` at the repo root: does either exist? Is there already an `## Agent skills` section in either?\n- `CONTEXT.md` and `CONTEXT-MAP.md` at the repo root\n- `docs\u002Fadr\u002F` and any `src\u002F*\u002Fdocs\u002Fadr\u002F` directories\n- `docs\u002Fagents\u002F`: does this skill's prior output already exist?\n- `.scratch\u002F`: a sign that a local-markdown issue tracker convention is already in use\n- Is the `triage` skill installed? (a `triage` skill folder alongside this one, or `triage` in your available skills.) This decides whether Section B runs at all.\n- Monorepo signals: a `pnpm-workspace.yaml`, a `workspaces` field in `package.json`, or a populated `packages\u002F*` with its own `src\u002F`. These are present only in a genuinely large multi-package repo; their absence means single-context, which is almost every repo.\n\n### 2. Present findings and ask\n\nSummarise what's present and what's missing. Then take the sections in order. One section, one answer, then the next.\n\nLead each section with the recommended answer so the user can accept it in a word. Give a one-line explainer only when the choice genuinely branches; skip the section entirely when exploration already settled it (Section B when `triage` isn't installed, Section C when there's no monorepo).\n\n**Section A: Issue tracker.**\n\n> Explainer: The \"issue tracker\" is where issues live for this repo. Skills like `to-tickets`, `triage`, and `to-spec` read from and write to it. They need to know whether to call `gh issue create`, write a markdown file under `.scratch\u002F`, or follow some other workflow you describe. Pick the place you actually track work for this repo.\n\nDefault posture: these skills were designed for GitHub. If a `git remote` points at GitHub, propose that. If a `git remote` points at GitLab (`gitlab.com` or a self-hosted host), propose GitLab. Otherwise (or if the user prefers), offer:\n\n- **GitHub**: issues live in the repo's GitHub Issues (uses the `gh` CLI)\n- **GitLab**: issues live in the repo's GitLab Issues (uses the [`glab`](https:\u002F\u002Fgitlab.com\u002Fgitlab-org\u002Fcli) CLI)\n- **Local markdown**: issues live as files under `.scratch\u002F\u003Cfeature>\u002F` in this repo (good for solo projects or repos without a remote)\n- **Other** (Jira, Linear, etc.): ask the user to describe the workflow in one paragraph; the skill will record it as freeform prose\n\nRecord the choice in `docs\u002Fagents\u002Fissue-tracker.md`. The GitHub and GitLab templates carry a \"PRs as a request surface\" flag, defaulted **off**. Leave it off and don't raise it: a user who wants external PRs in the triage queue can flip the flag in the file later.\n\n**Section B: Triage label vocabulary.** Skip this section entirely if the `triage` skill isn't installed (exploration told you), since an uninstalled skill needs no labels.\n\nIf it is installed, ask exactly one question:\n\n> Do you want to keep the default triage labels? (recommended: **yes**)\n\nThe defaults are the five canonical roles, each label string equal to its name: `needs-triage`, `needs-info`, `ready-for-agent`, `ready-for-human`, `wontfix`. On **yes**, write them as-is. Only if the user says no, usually because their tracker already uses other names (e.g. `bug:triage` for `needs-triage`), collect the overrides so `triage` applies existing labels instead of creating duplicates.\n\n**Section C: Domain docs.** Default to **single-context** (one `CONTEXT.md` + `docs\u002Fadr\u002F` at the repo root). This fits almost every repo; write it without asking.\n\nOffer **multi-context** (a root `CONTEXT-MAP.md` pointing to per-context `CONTEXT.md` files) only when exploration found monorepo signals. Then confirm which layout they want.\n\n### 3. Confirm and edit\n\nShow the user a draft of:\n\n- The `## Agent skills` block to add to whichever of `CLAUDE.md` \u002F `AGENTS.md` is being edited (see step 4 for selection rules)\n- The contents of `docs\u002Fagents\u002Fissue-tracker.md`, `docs\u002Fagents\u002Fdomain.md`, and `docs\u002Fagents\u002Ftriage-labels.md` (the last only when `triage` is installed)\n\nLet them edit before writing.\n\n### 4. Write\n\n**Pick the file to edit:**\n\n- If `CLAUDE.md` exists, edit it.\n- Else if `AGENTS.md` exists, edit it.\n- If neither exists, ask the user which one to create; don't pick for them.\n\nNever create `AGENTS.md` when `CLAUDE.md` already exists (or vice versa); always edit the one that's already there.\n\nIf an `## Agent skills` block already exists in the chosen file, update its contents in-place rather than appending a duplicate. Don't overwrite user edits to the surrounding sections.\n\nThe block:\n\n```markdown\n## Agent skills\n\n### Issue tracker\n\n[one-line summary of where issues are tracked]. See `docs\u002Fagents\u002Fissue-tracker.md`.\n\n### Triage labels\n\n[one-line summary of the label vocabulary]. See `docs\u002Fagents\u002Ftriage-labels.md`.\n\n### Domain docs\n\n[one-line summary of layout: \"single-context\" or \"multi-context\"]. See `docs\u002Fagents\u002Fdomain.md`.\n```\n\nInclude the `### Triage labels` sub-block, and write `docs\u002Fagents\u002Ftriage-labels.md`, only when `triage` is installed and Section B ran. When it isn't, both are omitted.\n\nThen write the docs files using the seed templates in this skill folder as a starting point:\n\n- [issue-tracker-github.md](.\u002Fissue-tracker-github.md): GitHub issue tracker\n- [issue-tracker-gitlab.md](.\u002Fissue-tracker-gitlab.md): GitLab issue tracker\n- [issue-tracker-local.md](.\u002Fissue-tracker-local.md): local-markdown issue tracker\n- [triage-labels.md](.\u002Ftriage-labels.md): label mapping (only if `triage` is installed)\n- [domain.md](.\u002Fdomain.md): domain doc consumer rules + layout\n\nFor \"other\" issue trackers, write `docs\u002Fagents\u002Fissue-tracker.md` from scratch using the user's description.\n\n### 5. Done\n\nTell the user the setup is complete and which engineering skills will now read from these files. Mention they can edit `docs\u002Fagents\u002F*.md` directly later; re-running this skill is only necessary if they want to switch issue trackers or restart from scratch.\n","# Setup Matt Pocock's Skills\n\nScaffold the per-repo configuration that the engineering skills assume:\n\n- **Issue tracker**: where issues live (GitHub by default; local markdown is also supported out of the box)\n- **Triage labels**: the strings used for the five canonical triage roles\n- **Domain docs**: where `CONTEXT.md` and ADRs live, and the consumer rules for reading them\n\nThis is a prompt-driven skill, not a deterministic script. Explore, present what you found, confirm with the user, then write.\n\n## Process\n\n### 1. Explore\n\nLook at the current repo to understand its starting state. Read whatever exists; don't assume:\n\n- `git remote -v` and `.git\u002Fconfig`: is this a GitHub repo? Which one?\n- `AGENTS.md` and `CLAUDE.md` at the repo root: does either exist? Is there already an `## Agent skills` section in either?\n- `CONTEXT.md` and `CONTEXT-MAP.md` at the repo root\n- `docs\u002Fadr\u002F` and any `src\u002F*\u002Fdocs\u002Fadr\u002F` directories\n- `docs\u002Fagents\u002F`: does this skill's prior output already exist?\n- `.scratch\u002F`: a sign that a local-markdown issue tracker convention is already in use\n- Is the `triage` skill installed? (a `triage` skill folder alongside this one, or `triage` in your available skills.) This decides whether Section B runs at all.\n- Monorepo signals: a `pnpm-workspace.yaml`, a `workspaces` field in `package.json`, or a populated `packages\u002F*` with its own `src\u002F`. These are present only in a genuinely large multi-package repo; their absence means single-context, which is almost every repo.\n\n### 2. Present findings and ask\n\nSummarise what's present and what's missing. Then take the sections in order. One section, one answer, then the next.\n\nLead each section with the recommended answer so the user can accept it in a word. Give a one-line explainer only when the choice genuinely branches; skip the section entirely when exploration already settled it (Section B when `triage` isn't installed, Section C when there's no monorepo).\n\n**Section A: Issue tracker.**\n\n> Explainer: The \"issue tracker\" is where issues live for this repo. Skills like `to-tickets`, `triage`, and `to-spec` read from and write to it. They need to know whether to call `gh issue create`, write a markdown file under `.scratch\u002F`, or follow some other workflow you describe. Pick the place you actually track work for this repo.\n\nDefault posture: these skills were designed for GitHub. If a `git remote` points at GitHub, propose that. If a `git remote` points at GitLab (`gitlab.com` or a self-hosted host), propose GitLab. Otherwise (or if the user prefers), offer:\n\n- **GitHub**: issues live in the repo's GitHub Issues (uses the `gh` CLI)\n- **GitLab**: issues live in the repo's GitLab Issues (uses the [`glab`](https:\u002F\u002Fgitlab.com\u002Fgitlab-org\u002Fcli) CLI)\n- **Local markdown**: issues live as files under `.scratch\u002F\u003Cfeature>\u002F` in this repo (good for solo projects or repos without a remote)\n- **Other** (Jira, Linear, etc.): ask the user to describe the workflow in one paragraph; the skill will record it as freeform prose\n\nRecord the choice in `docs\u002Fagents\u002Fissue-tracker.md`. The GitHub and GitLab templates carry a \"PRs as a request surface\" flag, defaulted **off**. Leave it off and don't raise it: a user who wants external PRs in the triage queue can flip the flag in the file later.\n\n**Section B: Triage label vocabulary.** Skip this section entirely if the `triage` skill isn't installed (exploration told you), since an uninstalled skill needs no labels.\n\nIf it is installed, ask exactly one question:\n\n> Do you want to keep the default triage labels? (recommended: **yes**)\n\nThe defaults are the five canonical roles, each label string equal to its name: `needs-triage`, `needs-info`, `ready-for-agent`, `ready-for-human`, `wontfix`. On **yes**, write them as-is. Only if the user says no, usually because their tracker already uses other names (e.g. `bug:triage` for `needs-triage`), collect the overrides so `triage` applies existing labels instead of creating duplicates.\n\n**Section C: Domain docs.** Default to **single-context** (one `CONTEXT.md` + `docs\u002Fadr\u002F` at the repo root). This fits almost every repo; write it without asking.\n\nOffer **multi-context** (a root `CONTEXT-MAP.md` pointing to per-context `CONTEXT.md` files) only when exploration found monorepo signals. Then confirm which layout they want.\n\n### 3. Confirm and edit\n\nShow the user a draft of:\n\n- The `## Agent skills` block to add to whichever of `CLAUDE.md` \u002F `AGENTS.md` is being edited (see step 4 for selection rules)\n- The contents of `docs\u002Fagents\u002Fissue-tracker.md`, `docs\u002Fagents\u002Fdomain.md`, and `docs\u002Fagents\u002Ftriage-labels.md` (the last only when `triage` is installed)\n\nLet them edit before writing.\n\n### 4. Write\n\n**Pick the file to edit:**\n\n- If `CLAUDE.md` exists, edit it.\n- Else if `AGENTS.md` exists, edit it.\n- If neither exists, ask the user which one to create; don't pick for them.\n\nNever create `AGENTS.md` when `CLAUDE.md` already exists (or vice versa); always edit the one that's already there.\n\nIf an `## Agent skills` block already exists in the chosen file, update its contents in-place rather than appending a duplicate. Don't overwrite user edits to the surrounding sections.\n\nThe block:\n\n```markdown\n## Agent skills\n\n### Issue tracker\n\n[one-line summary of where issues are tracked]. See `docs\u002Fagents\u002Fissue-tracker.md`.\n\n### Triage labels\n\n[one-line summary of the label vocabulary]. See `docs\u002Fagents\u002Ftriage-labels.md`.\n\n### Domain docs\n\n[one-line summary of layout: \"single-context\" or \"multi-context\"]. See `docs\u002Fagents\u002Fdomain.md`.\n```\n\nInclude the `### Triage labels` sub-block, and write `docs\u002Fagents\u002Ftriage-labels.md`, only when `triage` is installed and Section B ran. When it isn't, both are omitted.\n\nThen write the docs files using the seed templates in this skill folder as a starting point:\n\n- [issue-tracker-github.md](.\u002Fissue-tracker-github.md): GitHub issue tracker\n- [issue-tracker-gitlab.md](.\u002Fissue-tracker-gitlab.md): GitLab issue tracker\n- [issue-tracker-local.md](.\u002Fissue-tracker-local.md): local-markdown issue tracker\n- [triage-labels.md](.\u002Ftriage-labels.md): label mapping (only if `triage` is installed)\n- [domain.md](.\u002Fdomain.md): domain doc consumer rules + layout\n\nFor \"other\" issue trackers, write `docs\u002Fagents\u002Fissue-tracker.md` from scratch using the user's description.\n\n### 5. Done\n\nTell the user the setup is complete and which engineering skills will now read from these files. Mention they can edit `docs\u002Fagents\u002F*.md` directly later; re-running this skill is only necessary if they want to switch issue trackers or restart from scratch.\n",{"name":5,"description":7,"disable-model-invocation":24},true,"develop","ba8919e7a5182cc94dbe3e9b3a46f4c2e8fa209d",".trae\u002Fskills\u002Fsetup-matt-pocock-skills",4,"https:\u002F\u002Fgithub.com\u002Fmambo-wang\u002FCodeWiki-Plus","https:\u002F\u002Fpypi.org\u002Fproject\u002Fcodewiki-plus\u002F","https:\u002F\u002Fgithub.com\u002Fmambo-wang","https:\u002F\u002Fblog.csdn.net\u002Fsinat_27143551","专注Java后端开发，喜欢运动","2026-11-13 15:29:46",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":24},[37,40,43],{"tool":38,"command":39},"npx","npx skills add mambo-wang\u002FCodeWiki-Plus --skill setup-matt-pocock-skills",{"tool":41,"command":42},"bunx","bunx skills add mambo-wang\u002FCodeWiki-Plus --skill setup-matt-pocock-skills",{"tool":44,"command":45},"pnpm","pnpm dlx skills add mambo-wang\u002FCodeWiki-Plus --skill setup-matt-pocock-skills","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmambo-wang\u002FCodeWiki-Plus\u002Fblob\u002Fdevelop\u002F.trae\u002Fskills\u002Fsetup-matt-pocock-skills\u002FSKILL.md",[48,54,58,62,66,70],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"agents\u002Fopenai.yaml","REFERENCE","参考文档",152,"https:\u002F\u002Fgithub.com\u002Fmambo-wang\u002FCodeWiki-Plus\u002Fblob\u002Fdevelop\u002F.trae\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fagents\u002Fopenai.yaml",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"domain.md",2033,"https:\u002F\u002Fgithub.com\u002Fmambo-wang\u002FCodeWiki-Plus\u002Fblob\u002Fdevelop\u002F.trae\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fdomain.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"issue-tracker-github.md",3731,"https:\u002F\u002Fgithub.com\u002Fmambo-wang\u002FCodeWiki-Plus\u002Fblob\u002Fdevelop\u002F.trae\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fissue-tracker-github.md",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"issue-tracker-gitlab.md",3809,"https:\u002F\u002Fgithub.com\u002Fmambo-wang\u002FCodeWiki-Plus\u002Fblob\u002Fdevelop\u002F.trae\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fissue-tracker-gitlab.md",{"path":67,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":68,"sourceHtmlUrl":69},"issue-tracker-local.md",1810,"https:\u002F\u002Fgithub.com\u002Fmambo-wang\u002FCodeWiki-Plus\u002Fblob\u002Fdevelop\u002F.trae\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fissue-tracker-local.md",{"path":71,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":72,"sourceHtmlUrl":73},"triage-labels.md",1045,"https:\u002F\u002Fgithub.com\u002Fmambo-wang\u002FCodeWiki-Plus\u002Fblob\u002Fdevelop\u002F.trae\u002Fskills\u002Fsetup-matt-pocock-skills\u002Ftriage-labels.md",[75,82,89,96,103,110],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M75XA78546E66PCC3JV2TM3Q","write-doc-file-content-file-sidechannel","write_doc_file 建档报目标路径已被手写文件占用\u002F路由冲突时——走 content_file 临时文件侧通道：正文写临时文件→删占位文件→write_doc_file(content_file=...) 正式建档→删临时文件","https:\u002F\u002Fgithub.com\u002Fmambo-wang\u002FCodeWiki-Plus\u002Fblob\u002Fdevelop\u002Frepowiki\u002Fskills\u002Fwrite-doc-file-content-file-sidechannel\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M75X9YQNDX8B6ZEVMKGM2TYR","windows-python-release","当要手动发布 Python 包（codewiki-plus）到 PyPI 并建 GitHub Release 时——CI 不发布、Windows 控制台为 GBK、可能无 gh CLI、本机网络对 upload.pypi.org 的 Python TLS 握手有干扰——先核对 tag 区间与工作区未提交改动定 bump 级别，再按 8 步主干执行：同步四处版本→bump 提交（只 add 具体文件）→聚焦+ruff+全量闸门→清 dist 构建→PR 合并 main→tag merge commit 建 Release→uv publish（TLS 超时则 curl.exe 直传）→PyPI JSON API 核对","https:\u002F\u002Fgithub.com\u002Fmambo-wang\u002FCodeWiki-Plus\u002Fblob\u002Fdevelop\u002Frepowiki\u002Fskills\u002Fwindows-python-release\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M75X9MGBPRG6JDCRAY97E5T0","windows-dev-env","Windows\u002FPowerShell 下做 git 写操作、跑子进程或批量文件\u002F测试清理时：shell 漂移与中文路径致命令静默失败、无控制台宿主子进程闪窗、GCM 每次弹 OAuth 框、原生 DLL 被锁——须显式复核落盘、subprocess 加 CREATE_NO_WINDOW、gh auth setup-git 持久化凭据，并用 cmd \u002Fc 绕 safe-delete 钩子","https:\u002F\u002Fgithub.com\u002Fmambo-wang\u002FCodeWiki-Plus\u002Fblob\u002Fdevelop\u002Frepowiki\u002Fskills\u002Fwindows-dev-env\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M75X9H4YYF5C29JR7AF44K84","repowiki-conclusion-update","已落库 repowiki 结论发生变化时，按「结论方向 vs 表述」分流：方向变则新写 decision 笔记+reject_note 旧+confirm 并回源 ADR，仅表述\u002F证据变则 edit_doc_file 原地改","https:\u002F\u002Fgithub.com\u002Fmambo-wang\u002FCodeWiki-Plus\u002Fblob\u002Fdevelop\u002Frepowiki\u002Fskills\u002Frepowiki-conclusion-update\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":19},"01M75X9CD6FDMX1RDE9NZEFNVY","maintain-fork-pr-merge","当合入 fork 来源的 PR 且 mergeStateStatus=CONFLICTING\u002FDIRTY 时——先 git merge-tree 探测冲突清单，查 maintainer_can_modify，再在 worktree 隔离目录解冲突后 push fork 分支，勿因 CI 绿直接 merge","https:\u002F\u002Fgithub.com\u002Fmambo-wang\u002FCodeWiki-Plus\u002Fblob\u002Fdevelop\u002Frepowiki\u002Fskills\u002Fmaintain-fork-pr-merge\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":19},"01M75X98KRKX80JQ9Y4PR8WZCK","git-commit-hygiene","在共享 worktree 多会话并行或暂存区有残留时提交代码——用显式 pathspec 只提交自己的文件并排除临时目录，禁止 git add -A 或裸 commit 扫入并行会话的改动","https:\u002F\u002Fgithub.com\u002Fmambo-wang\u002FCodeWiki-Plus\u002Fblob\u002Fdevelop\u002Frepowiki\u002Fskills\u002Fgit-commit-hygiene\u002FSKILL.md",[],[]]