[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6WWGWZ3FPP31QGV0GW0VT73":3,"skill-same:01M6WWGWZ3FPP31QGV0GW0VT73":86},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":59,"commitSha":60,"skillDirectory":61,"forksCount":14,"repositoryHtmlUrl":62,"repositoryHomepageUrl":63,"ownerHtmlUrl":64,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":65,"install":66,"resources":79},"01M6WWGWZ3FPP31QGV0GW0VT73","git-branching",null,"Select, document, and evolve a Git branching strategy for a repository.\nUse when comparing Gitflow, GitHub Flow, trunk-based development,\nfeature branches, release branches, or concurrent version lines.","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-branching\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"git","git branching","branching","selection","when","for","v1","gitflow","feature","branches","methods","workflow","document","use","strategy","branch","select","commits","pull","development","2026-11-10 10:12:30",false,"---\nname: git-branching\ndescription: |\n  Select, document, and evolve a Git branching strategy for a repository.\n  Use when comparing Gitflow, GitHub Flow, trunk-based development,\n  feature branches, release branches, or concurrent version lines.\nmetadata:\n  processkit:\n    apiVersion: processkit.projectious.work\u002Fv1\n    id: SKILL-git-branching\n    version: \"1.0.0\"\n    created: 2026-07-21T19:05:00Z\n    category: engineering\n    layer: null\n    uses:\n      - skill: git-workflow\n        purpose: \"Apply the chosen strategy through branch names, commits, pull requests, and merge methods.\"\n    provides:\n      processes: [branching-strategy-selection]\n---\n\n# Git Branching\n\n## Intro\n\nChoose a branching strategy from the repository's delivery cadence,\nsupported versions, deployment environments, and release controls. Then\nwrite a small branch contract that makes integration and tagging authority\nunambiguous.\n\n## Overview\n\n### Select a strategy\n\nAnswer these questions before naming branches:\n\n1. Is `main` continuously deployable, or is there a separate release gate?\n2. Are older versions supported while new major work continues?\n3. Do environments promote the same commit through test and production?\n4. Can incomplete work be hidden with feature flags?\n5. Is the team able to keep shared branches continuously integrated?\n\nUse the smallest model that meets those constraints.\n\n| Strategy | Best fit | Long-lived branches | Release authority |\n| --- | --- | --- | --- |\n| Feature Branch Workflow | Shared integration branch, periodic releases | integration branch | integration or release branch |\n| GitHub Flow | Frequent deployment and one supported production line | `main` | `main` |\n| Trunk-Based Development | Strong CI, feature flags, rapid integration | `main`; optional short release branch | `main` or just-in-time release branch |\n| Gitflow | Scheduled releases and formal stabilization | `main`, `develop`, temporary release branches | release branch |\n| GitLab Flow | Environment promotion or maintained stable lines | `main`, environment or stable branches | production or stable branch |\n| Version-line integration | Concurrent major lines or long-lived maintenance | one dev and release branch per line | designated line release branch |\n\nRead [strategy catalog](references\u002Fstrategies.md) before choosing a model\nwith release branches, multiple environments, or concurrent version lines.\n\n### Write the branch contract\n\nFor each protected long-lived branch, record:\n\n- purpose and allowed changes;\n- source branches and merge direction;\n- tag authority and release validation command;\n- hotfix and backport path;\n- required checks, review, force-push, and deletion policy.\n\nKeep task branches short-lived and name them according to `git-workflow`.\nUse merge commits for meaningful integration between long-lived branches;\nuse the repository's chosen merge method for task branches.\n\n### Apply the version-line integration model\n\nUse this model when v0 maintenance and v1 development, or any two supported\nmajor lines, must progress independently:\n\n```text\nline.x-dev -> line.x-release -> tag stable release -> main\n\nnext.x-dev -> next.x-pre-release -> tag alpha\u002Fbeta\u002Frc\n                                     -> next.x-release -> tag GA -> main\n```\n\n- Create `line.x-release` from the latest stable tag and `line.x-dev` from\n  that release branch.\n- Merge development into the release branch, validate there, and tag only\n  there. Merge the tagged stable release into `main` immediately afterwards.\n- For prereleases, merge development into `next.x-pre-release` and tag only\n  on that branch. Create `next.x-release` only for general availability.\n- Hotfix from the latest stable tag, then merge to the release branch, tag,\n  merge to `main`, and merge back to the development branch.\n\n## Gotchas\n\n- **Treating `main` as both active development and release authority.**\n  This makes concurrent version lines indistinguishable. State whether\n  `main` is trunk or published history before creating branches.\n- **Copying Gitflow mechanically.** Gitflow's `develop` and release branches\n  add synchronization cost. Choose it only when scheduled stabilization or\n  parallel release preparation needs that cost.\n- **Tagging a development branch.** A development head may not have passed\n  integration checks. Tag only the contract's designated release branch.\n- **Using environment branches as feature integration branches.** Environment\n  branches promote tested commits; they are not a substitute for a developer\n  integration target unless the contract explicitly says so.\n- **Forgetting the return path for hotfixes.** A production fix that is not\n  merged back into active development will recur in the next release.\n- **Protecting a branch without defining how automation merges it.** Check\n  required reviews, checks, merge queue, and allowed merge methods before\n  making the branch the only release path.\n\n## Full reference\n\n### Required output\n\nDeliver a branch contract in this form:\n\n```text\nStrategy:\nReason for fit:\nProtected branches:\nMerge directions:\nTag authority:\nHotfix and backport policy:\nRequired checks and release commands:\nMigration steps and rollback point:\n```\n\nDo not migrate a live repository by renaming, deleting, or force-updating\nbranches until its existing tags, release consumers, and protection rules\nhave been inspected.\n\n### Anti-patterns\n\n- **A branch per person or indefinitely open feature branch.** Prefer a\n  focused task branch and merge it promptly.\n- **A release branch for every routine deployment.** If the product can\n  release directly from a healthy trunk, extra release branches add delay.\n- **One undocumented catch-all branch.** A branch without a stated authority\n  eventually receives incompatible development, release, and hotfix changes.\n\n### Cross-references\n\n- [Strategy catalog](references\u002Fstrategies.md)\n- `git-workflow` — naming, commits, pull requests, and merge methods\n- `release-semver` — changelog, tags, publishing, and release verification\n","# Git Branching\n\n## Intro\n\nChoose a branching strategy from the repository's delivery cadence,\nsupported versions, deployment environments, and release controls. Then\nwrite a small branch contract that makes integration and tagging authority\nunambiguous.\n\n## Overview\n\n### Select a strategy\n\nAnswer these questions before naming branches:\n\n1. Is `main` continuously deployable, or is there a separate release gate?\n2. Are older versions supported while new major work continues?\n3. Do environments promote the same commit through test and production?\n4. Can incomplete work be hidden with feature flags?\n5. Is the team able to keep shared branches continuously integrated?\n\nUse the smallest model that meets those constraints.\n\n| Strategy | Best fit | Long-lived branches | Release authority |\n| --- | --- | --- | --- |\n| Feature Branch Workflow | Shared integration branch, periodic releases | integration branch | integration or release branch |\n| GitHub Flow | Frequent deployment and one supported production line | `main` | `main` |\n| Trunk-Based Development | Strong CI, feature flags, rapid integration | `main`; optional short release branch | `main` or just-in-time release branch |\n| Gitflow | Scheduled releases and formal stabilization | `main`, `develop`, temporary release branches | release branch |\n| GitLab Flow | Environment promotion or maintained stable lines | `main`, environment or stable branches | production or stable branch |\n| Version-line integration | Concurrent major lines or long-lived maintenance | one dev and release branch per line | designated line release branch |\n\nRead [strategy catalog](references\u002Fstrategies.md) before choosing a model\nwith release branches, multiple environments, or concurrent version lines.\n\n### Write the branch contract\n\nFor each protected long-lived branch, record:\n\n- purpose and allowed changes;\n- source branches and merge direction;\n- tag authority and release validation command;\n- hotfix and backport path;\n- required checks, review, force-push, and deletion policy.\n\nKeep task branches short-lived and name them according to `git-workflow`.\nUse merge commits for meaningful integration between long-lived branches;\nuse the repository's chosen merge method for task branches.\n\n### Apply the version-line integration model\n\nUse this model when v0 maintenance and v1 development, or any two supported\nmajor lines, must progress independently:\n\n```text\nline.x-dev -> line.x-release -> tag stable release -> main\n\nnext.x-dev -> next.x-pre-release -> tag alpha\u002Fbeta\u002Frc\n                                     -> next.x-release -> tag GA -> main\n```\n\n- Create `line.x-release` from the latest stable tag and `line.x-dev` from\n  that release branch.\n- Merge development into the release branch, validate there, and tag only\n  there. Merge the tagged stable release into `main` immediately afterwards.\n- For prereleases, merge development into `next.x-pre-release` and tag only\n  on that branch. Create `next.x-release` only for general availability.\n- Hotfix from the latest stable tag, then merge to the release branch, tag,\n  merge to `main`, and merge back to the development branch.\n\n## Gotchas\n\n- **Treating `main` as both active development and release authority.**\n  This makes concurrent version lines indistinguishable. State whether\n  `main` is trunk or published history before creating branches.\n- **Copying Gitflow mechanically.** Gitflow's `develop` and release branches\n  add synchronization cost. Choose it only when scheduled stabilization or\n  parallel release preparation needs that cost.\n- **Tagging a development branch.** A development head may not have passed\n  integration checks. Tag only the contract's designated release branch.\n- **Using environment branches as feature integration branches.** Environment\n  branches promote tested commits; they are not a substitute for a developer\n  integration target unless the contract explicitly says so.\n- **Forgetting the return path for hotfixes.** A production fix that is not\n  merged back into active development will recur in the next release.\n- **Protecting a branch without defining how automation merges it.** Check\n  required reviews, checks, merge queue, and allowed merge methods before\n  making the branch the only release path.\n\n## Full reference\n\n### Required output\n\nDeliver a branch contract in this form:\n\n```text\nStrategy:\nReason for fit:\nProtected branches:\nMerge directions:\nTag authority:\nHotfix and backport policy:\nRequired checks and release commands:\nMigration steps and rollback point:\n```\n\nDo not migrate a live repository by renaming, deleting, or force-updating\nbranches until its existing tags, release consumers, and protection rules\nhave been inspected.\n\n### Anti-patterns\n\n- **A branch per person or indefinitely open feature branch.** Prefer a\n  focused task branch and merge it promptly.\n- **A release branch for every routine deployment.** If the product can\n  release directly from a healthy trunk, extra release branches add delay.\n- **One undocumented catch-all branch.** A branch without a stated authority\n  eventually receives incompatible development, release, and hotfix changes.\n\n### Cross-references\n\n- [Strategy catalog](references\u002Fstrategies.md)\n- `git-workflow` — naming, commits, pull requests, and merge methods\n- `release-semver` — changelog, tags, publishing, and release verification\n",{"name":5,"metadata":44,"description":58},{"processkit":45},{"id":46,"uses":47,"layer":6,"created":51,"version":52,"category":53,"provides":54,"apiVersion":57},"SKILL-git-branching",[48],{"skill":49,"purpose":50},"git-workflow","Apply the chosen strategy through branch names, commits, pull requests, and merge methods.",1784660700000,"1.0.0","engineering",{"processes":55},[56],"branching-strategy-selection","processkit.projectious.work\u002Fv1","Select, document, and evolve a Git branching strategy for a repository.\nUse when comparing Gitflow, GitHub Flow, trunk-based development,\nfeature branches, release branches, or concurrent version lines.\n","main","4876a92620ee792aac2ac9a1a806322d8a572367","archive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fengineering\u002Fgit-branching","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":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add projectious-work\u002Fprocesskit --skill git-branching",{"tool":72,"command":73},"bunx","bunx skills add projectious-work\u002Fprocesskit --skill git-branching",{"tool":75,"command":76},"pnpm","pnpm dlx skills add projectious-work\u002Fprocesskit --skill git-branching","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fengineering\u002Fgit-branching\u002FSKILL.md",true,[80],{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fstrategies.md","REFERENCE","参考文档",3374,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fengineering\u002Fgit-branching\u002Freferences\u002Fstrategies.md",[87,94,101,107,134,154],{"skillNo":88,"name":89,"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":90,"categories":91,"keywords":92,"publishedAt":93},"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":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":93},"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":102,"name":103,"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":104,"categories":105,"keywords":106,"publishedAt":93},"01M76650NN4T8P241021NBR64S","standard-agent-building","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-agent-building\u002FSKILL.md",[],[],{"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":118,"publishedAt":39},"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",[113],{"categoryNo":114,"categoryName":115,"taxonomyType":116,"taxonomyTypeDesc":117},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[119,120,121,25,122,123,124,125,126,127,128,129,109,130,131,132,133],"management","skill management","ontology","create","as","work","transition","get","manage","update","alpha","list","package","skill package","manifests",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":141,"publishedAt":39},"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",[140],{"categoryNo":114,"categoryName":115,"taxonomyType":116,"taxonomyTypeDesc":117},[142,143,119,144,145,146,147,148,149,150,151,152,124,126,127,129,153],"schema","schema management","contract","rebuild","contracts","workflows","wed","generated","MCP","validation","deterministic","mode",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":39},"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",[],[161,119,162,163,122,164,165,166,124,126,167,168,128,169,129,170,171,172,173,174],"proposition management","proposition","interface","claims","record","world","creation","event","WSJF","index","updates","query","facts","log"]