[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6WWH0C289YK347ZW2H17HVD":3,"skill-same:01M6WWH0C289YK347ZW2H17HVD":79},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":14,"repositoryHtmlUrl":61,"repositoryHomepageUrl":62,"ownerHtmlUrl":63,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":64,"install":65,"resources":78},"01M6WWH0C289YK347ZW2H17HVD","git-workflow",null,"Git workflow conventions — branch naming, conventional commits, PR descriptions, and merge strategy. Use when deciding on a branch name, writing a commit message or PR description, or choosing a merge strategy.","projectious-work\u002Fprocesskit","projectious-work","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F263889726?v=4","01M6N97TJJ118WQ35CHRV8RD0E","projectious.work","01M6N97TPWJPF0BMKYQ4PBY5W8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fengineering\u002Fgit-workflow\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"workflow","git workflow","git","when","writing","naming","name","conventions","message","conventional commits","use","strategy","branch","work","commits","commit message","pr description","pr","merge","commit","2026-11-10 10:12:30",false,"---\nname: git-workflow\ndescription: |\n  Git workflow conventions — branch naming, conventional commits, PR descriptions, and merge strategy. Use when deciding on a branch name, writing a commit message or PR description, or choosing a merge strategy.\nmetadata:\n  processkit:\n    apiVersion: processkit.projectious.work\u002Fv2\n    id: SKILL-git-workflow\n    version: \"1.1.0\"\n    created: 2026-04-06T00:00:00Z\n    category: engineering\n    layer: 3\n---\n\n# Git Workflow\n\n## Intro\n\nUse typed branch names, Conventional Commits, and PR descriptions\nthat explain the why. Squash-merge feature branches for a clean\nhistory. Keep commits atomic and never force-push to shared\nbranches.\n\n## Overview\n\n### Branch naming\n\nFormat: `\u003Ctype>\u002F\u003Cissue>-\u003Cshort-description>`\n\nTypes: `feat\u002F`, `fix\u002F`, `refactor\u002F`, `docs\u002F`, `chore\u002F`\n\nExamples:\n\n- `feat\u002F42-add-user-auth`\n- `fix\u002F17-null-pointer-crash`\n- `refactor\u002F89-extract-payment-service`\n\n### Version-line release branches\n\nFor concurrently maintained major lines, use explicit development and\nrelease-integration branches. `main` is the published-history branch, not\nthe active development or tagging authority.\n\n| Line | Development | Integration and tag authority | Publication |\n| --- | --- | --- | --- |\n| v0.x | `v0.x-dev` | `v0.x-release` | merge tagged release into `main` |\n| v1.x prerelease | `v1.x-dev` | `v1.x-pre-release` | prerelease tag stays on integration branch |\n| v1.x GA | `v1.x-pre-release` | `v1.x-release` | merge tagged release into `main` |\n\n- Create a version-line release branch from the currently published tag,\n  then create its development branch from that release branch.\n- Merge development into the relevant integration branch for each release;\n  validate, prepare, and tag only on that integration branch.\n- Immediately merge the tagged integration branch into `main`, so every\n  stable release tag is reachable from `main`.\n- Do not commit directly to `main` or an integration branch. Protect them\n  and use merge commits for long-lived branch integration.\n- For a maintenance hotfix, branch from the latest stable tag, merge into\n  the release branch, tag, merge the release branch into `main`, then\n  merge the result back into the development branch.\n\n### Commit messages\n\nFollow Conventional Commits:\n\n- **Format:** `\u003Ctype>: \u003Cdescription>` — lowercase, imperative\n  mood, no trailing period\n- **Types:** `feat`, `fix`, `refactor`, `docs`, `test`, `chore`,\n  `ci`\n- **Body:** explain WHY, not WHAT (the diff shows what)\n- **Footer:** `fixes #N` or `refs #N` for issue links\n\n### PR descriptions\n\n- **Title:** same format as commit messages, under 70 characters\n- **Body:** Summary (what and why), test plan, breaking changes\n- Link related issues\n\n### Merge strategy\n\n- **Squash merge** for feature branches — keeps mainline history\n  clean\n- **Merge commit** for long-lived branches — preserves context\n  across the merge\n- **Rebase** to keep a feature branch up to date before opening\n  the PR\n\n## Gotchas\n\nAgent-specific failure modes — provider-neutral pause-and-self-check items:\n\n- **Mega-commits (\"various fixes\", 40 files changed).** A commit that mixes unrelated changes is impossible to review, impossible to revert selectively, and tells a lie in its message. Each commit should represent one logical change that can stand alone.\n- **Force-pushing to shared branches.** Force-pushing to `main` or any branch others have checked out rewrites history they depend on, causing diverged local states that are painful to recover. Never force-push to a shared branch.\n- **Branches that live for months.** Long-lived branches diverge from main, accumulate merge conflicts, and eventually require heroic merge efforts. Rebase weekly or split long-running work into shorter-lived feature branches.\n- **Tagging a development branch.** A development branch has not passed the\n  integration and release gate. Stable and prerelease tags must originate\n  on their designated integration branch.\n- **PRs with no description.** \"See commits\" is not a description. The PR description is for the reviewer — it explains what changed, why it changed, and how to verify it. Write it before requesting review.\n- **Conventional Commit type misuse.** Using `fix:` for features or `feat:` for refactors corrupts any automation that generates changelogs or determines version bumps from commit types. Match the type to the nature of the change.\n- **Squash-merging a long-lived integration branch.** Squash-merge is for feature branches with noisy \"wip\" commits. A long-lived branch with meaningful commit history should be merge-committed so the history is preserved for future investigation.\n- **Committing unrelated changes in the same PR to \"save time\".** Reviewers are slower on unrelated changes combined in one PR; rollback becomes more expensive if one change needs reverting. Split unrelated changes into separate PRs.\n\n## Full reference\n\n### General rules\n\n- Commit early and often on feature branches; squash at merge time.\n- Never force-push to shared branches (`main`, `develop`, release\n  branches).\n- Keep commits atomic — one logical change per commit. A commit\n  that touches three unrelated concerns is three commits.\n- A commit message body wraps at 72 columns; the subject line at\n  50 if you can.\n\n### Worked example\n\nUser: \"What should I name this branch for adding search?\"\n\nSuggest `feat\u002F30-add-search-functionality` if there's an issue\n#30; otherwise `feat\u002Fadd-search-functionality`. Match the\nexisting repo's convention if it differs.\n\n### Anti-patterns\n\n- **Mega-commits** — \"various fixes\" with 40 files changed.\n  Impossible to review or revert.\n- **Force-push to main** — destroys other contributors' work.\n- **Commit messages like \"wip\", \"fix\", \"stuff\"** — every commit\n  should be reviewable on its own.\n- **PRs with no description** — the PR description is for the\n  reviewer, not the author. \"See commits\" is not a description.\n- **Branches that live for months** — long-lived branches\n  diverge from main and become merge nightmares. Rebase weekly\n  or split the work.\n\n### When to break the rules\n\nSolo-on-a-private-branch force-pushes are fine. Trivial typo\nfixes don't need a long body. Use judgment, but the defaults\nabove are right for almost every team setting.\n","# Git Workflow\n\n## Intro\n\nUse typed branch names, Conventional Commits, and PR descriptions\nthat explain the why. Squash-merge feature branches for a clean\nhistory. Keep commits atomic and never force-push to shared\nbranches.\n\n## Overview\n\n### Branch naming\n\nFormat: `\u003Ctype>\u002F\u003Cissue>-\u003Cshort-description>`\n\nTypes: `feat\u002F`, `fix\u002F`, `refactor\u002F`, `docs\u002F`, `chore\u002F`\n\nExamples:\n\n- `feat\u002F42-add-user-auth`\n- `fix\u002F17-null-pointer-crash`\n- `refactor\u002F89-extract-payment-service`\n\n### Version-line release branches\n\nFor concurrently maintained major lines, use explicit development and\nrelease-integration branches. `main` is the published-history branch, not\nthe active development or tagging authority.\n\n| Line | Development | Integration and tag authority | Publication |\n| --- | --- | --- | --- |\n| v0.x | `v0.x-dev` | `v0.x-release` | merge tagged release into `main` |\n| v1.x prerelease | `v1.x-dev` | `v1.x-pre-release` | prerelease tag stays on integration branch |\n| v1.x GA | `v1.x-pre-release` | `v1.x-release` | merge tagged release into `main` |\n\n- Create a version-line release branch from the currently published tag,\n  then create its development branch from that release branch.\n- Merge development into the relevant integration branch for each release;\n  validate, prepare, and tag only on that integration branch.\n- Immediately merge the tagged integration branch into `main`, so every\n  stable release tag is reachable from `main`.\n- Do not commit directly to `main` or an integration branch. Protect them\n  and use merge commits for long-lived branch integration.\n- For a maintenance hotfix, branch from the latest stable tag, merge into\n  the release branch, tag, merge the release branch into `main`, then\n  merge the result back into the development branch.\n\n### Commit messages\n\nFollow Conventional Commits:\n\n- **Format:** `\u003Ctype>: \u003Cdescription>` — lowercase, imperative\n  mood, no trailing period\n- **Types:** `feat`, `fix`, `refactor`, `docs`, `test`, `chore`,\n  `ci`\n- **Body:** explain WHY, not WHAT (the diff shows what)\n- **Footer:** `fixes #N` or `refs #N` for issue links\n\n### PR descriptions\n\n- **Title:** same format as commit messages, under 70 characters\n- **Body:** Summary (what and why), test plan, breaking changes\n- Link related issues\n\n### Merge strategy\n\n- **Squash merge** for feature branches — keeps mainline history\n  clean\n- **Merge commit** for long-lived branches — preserves context\n  across the merge\n- **Rebase** to keep a feature branch up to date before opening\n  the PR\n\n## Gotchas\n\nAgent-specific failure modes — provider-neutral pause-and-self-check items:\n\n- **Mega-commits (\"various fixes\", 40 files changed).** A commit that mixes unrelated changes is impossible to review, impossible to revert selectively, and tells a lie in its message. Each commit should represent one logical change that can stand alone.\n- **Force-pushing to shared branches.** Force-pushing to `main` or any branch others have checked out rewrites history they depend on, causing diverged local states that are painful to recover. Never force-push to a shared branch.\n- **Branches that live for months.** Long-lived branches diverge from main, accumulate merge conflicts, and eventually require heroic merge efforts. Rebase weekly or split long-running work into shorter-lived feature branches.\n- **Tagging a development branch.** A development branch has not passed the\n  integration and release gate. Stable and prerelease tags must originate\n  on their designated integration branch.\n- **PRs with no description.** \"See commits\" is not a description. The PR description is for the reviewer — it explains what changed, why it changed, and how to verify it. Write it before requesting review.\n- **Conventional Commit type misuse.** Using `fix:` for features or `feat:` for refactors corrupts any automation that generates changelogs or determines version bumps from commit types. Match the type to the nature of the change.\n- **Squash-merging a long-lived integration branch.** Squash-merge is for feature branches with noisy \"wip\" commits. A long-lived branch with meaningful commit history should be merge-committed so the history is preserved for future investigation.\n- **Committing unrelated changes in the same PR to \"save time\".** Reviewers are slower on unrelated changes combined in one PR; rollback becomes more expensive if one change needs reverting. Split unrelated changes into separate PRs.\n\n## Full reference\n\n### General rules\n\n- Commit early and often on feature branches; squash at merge time.\n- Never force-push to shared branches (`main`, `develop`, release\n  branches).\n- Keep commits atomic — one logical change per commit. A commit\n  that touches three unrelated concerns is three commits.\n- A commit message body wraps at 72 columns; the subject line at\n  50 if you can.\n\n### Worked example\n\nUser: \"What should I name this branch for adding search?\"\n\nSuggest `feat\u002F30-add-search-functionality` if there's an issue\n#30; otherwise `feat\u002Fadd-search-functionality`. Match the\nexisting repo's convention if it differs.\n\n### Anti-patterns\n\n- **Mega-commits** — \"various fixes\" with 40 files changed.\n  Impossible to review or revert.\n- **Force-push to main** — destroys other contributors' work.\n- **Commit messages like \"wip\", \"fix\", \"stuff\"** — every commit\n  should be reviewable on its own.\n- **PRs with no description** — the PR description is for the\n  reviewer, not the author. \"See commits\" is not a description.\n- **Branches that live for months** — long-lived branches\n  diverge from main and become merge nightmares. Rebase weekly\n  or split the work.\n\n### When to break the rules\n\nSolo-on-a-private-branch force-pushes are fine. Trivial typo\nfixes don't need a long body. Use judgment, but the defaults\nabove are right for almost every team setting.\n",{"name":5,"metadata":49,"description":57},{"processkit":50},{"id":51,"layer":52,"created":53,"version":54,"category":55,"apiVersion":56},"SKILL-git-workflow",3,1775433600000,"1.1.0","engineering","processkit.projectious.work\u002Fv2","Git workflow conventions — branch naming, conventional commits, PR descriptions, and merge strategy. Use when deciding on a branch name, writing a commit message or PR description, or choosing a merge strategy.\n","main","4876a92620ee792aac2ac9a1a806322d8a572367","archive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fengineering\u002Fgit-workflow","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit","https:\u002F\u002Fprojectious-work.github.io\u002Fprocesskit\u002F","https:\u002F\u002Fgithub.com\u002Fprojectious-work","2026-11-11 23:24:18",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add projectious-work\u002Fprocesskit --skill git-workflow",{"tool":71,"command":72},"bunx","bunx skills add projectious-work\u002Fprocesskit --skill git-workflow",{"tool":74,"command":75},"pnpm","pnpm dlx skills add projectious-work\u002Fprocesskit --skill git-workflow","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fengineering\u002Fgit-workflow\u002FSKILL.md",true,[],[80,87,94,100,123,143],{"skillNo":81,"name":82,"nameZh":6,"description":6,"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":85,"publishedAt":86},"01M7665G2ED3624R3X93304265","standard-ui-design","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-ui-design\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":86},"01M76651QTC6W0HJ4AFW2MMR3V","standard-agent-use","Company standard for working with AI agents. Use when deciding what to delegate to agents, capturing open work, keeping agent memory or knowledge notes, improving an agent workflow, or introducing agent work in a team or for a client.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-agent-use\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":86},"01M76650NN4T8P241021NBR64S","standard-agent-building","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-agent-building\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":107,"publishedAt":44},"01M6X5MTC89B4ZGXW3JVSQCPF8","skill-management","Manage Skill package manifests as v1 ontology entities.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-management\u002FSKILL.md",[106],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[108,109,110,111,112,113,37,114,115,116,117,118,102,119,120,121,122],"management","skill management","ontology","v1","create","as","transition","get","manage","update","alpha","list","package","skill package","manifests",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":130,"publishedAt":44},"01M6X5MCV74NHW5MEDNHZRF2C8","schema-management","Manage generated processkit schema contracts through deterministic MCP rebuild and inspection workflows.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fschema-management\u002FSKILL.md",[129],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[131,132,108,133,134,135,136,137,138,139,140,141,37,115,116,118,142],"schema","schema management","contract","rebuild","contracts","workflows","wed","generated","MCP","validation","deterministic","mode",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":44},"01M6X5M5G6YJ96AMZGSCZJ1D13","proposition-management","Record claims, risks, beliefs, world facts, WSJF estimates, and assumptions through the Proposition interface.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fproposition-management\u002FSKILL.md",[],[150,108,151,152,112,153,154,155,37,115,156,157,117,158,118,159,160,161,162,163],"proposition management","proposition","interface","claims","record","world","creation","event","WSJF","index","updates","query","facts","log"]