[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DJW33G2SHYSENP3DYR8T0V":3,"skill-same:01M7DJW33G2SHYSENP3DYR8T0V":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":28,"updatedAt":29,"install":30,"resources":43},"01M7DJW33G2SHYSENP3DYR8T0V","maestro-git-workflow",null,"Use when branches, worktrees, commits, history investigation or branch completion need attention.","Orchestration-Maestro\u002Fmaestro-manifests","Orchestration-Maestro","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F322897002?v=4","01M7DJV5QYHV5358EX4AGZJZK3","01M7DJV5RPB4CBJZBKV9AHREM6",0,"MIT","https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro\u002Fmaestro-manifests\u002Fblob\u002Fmain\u002Fmanifests\u002Fcapabilities\u002Fpractice\u002Fmaestro-skills\u002Fskills\u002Fmaestro-git-workflow\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: maestro-git-workflow\ndescription: \"Use when branches, worktrees, commits, history investigation or branch completion need attention.\"\n---\n\n# Preserve work while using Git\n\nRead the repository's merge, release, signing and generated-file rules first. They\nwin over this guidance. Inspect status, branch, remotes and existing worktree metadata\nbefore changing the checkout. Establish who owns the workspace and what must survive.\n\n## Detect isolation before creating it\n\nDistinguish an ordinary checkout, an existing linked worktree, a submodule and an\nexternally managed detached HEAD. Inspect `git worktree list`, the Git directory and\n`git rev-parse --show-superproject-working-tree`; a `.git` file alone is ambiguous.\nUse the host's native isolation where available and respect the user's location\npreference. Reuse suitable existing isolation instead of nesting another worktree.\nA managed detached HEAD is not permission to switch branches or remove its workspace.\n\nFor a manually created local worktree, prefer the repository's existing convention.\nConfirm the directory is ignored with `git check-ignore` before creating it inside\nthe repository. If it is not ignored, obtain the appropriate ignore change first.\nCreate a named short-lived branch, install only the project's documented prerequisites\nand run its baseline checks. Report permission errors or a red baseline; ask how to\nproceed rather than bypassing permissions or treating existing failures as yours.\n\n## Commits and history\n\nKeep branches short-lived and integrate frequently under the repository's policy.\nMake atomic commits whose messages explain why the change exists, not just which\nfiles moved. Keep behaviour-preserving refactors in their own commits, separate from\nfeatures and fixes, so review and revert remain intelligible.\n\nBefore committing, inspect status and the staged diff. Stage only intended files;\nexclude secrets, scratch output, build artifacts and unrelated changes. Review\nnew files and generated output too. Change generation inputs rather than editing\nowned generated records; regenerate through the documented command. Run required\nhooks and checks, and inspect the resulting diff if formatting changes it.\n\nUse `git log`, `git show` and `git blame` to understand an unfamiliar constraint.\nFor a regression with a reproducible predicate, use `git bisect`: mark known good\nand bad revisions, run the same discriminating check at each step, and end with\n`git bisect reset`. Protect uncommitted work before moving history.\n\nFollow the repository's semantic-version policy: patch for compatible fixes, minor\nfor compatible additions, major for breaking changes unless its documented policy\ndiffers. Tags identify immutable releases; do not move a published tag. Let existing\nrelease tooling own version updates, generated changelogs and release notes.\n\n## Permission boundary\n\nObtain user confirmation before push or any use of `reset --hard`, `clean -f`,\n`branch -D`, `checkout .` or `restore .`. Explain the exact target and effect. A\nrequest to finish a feature is not blanket permission to destroy local work. Stop\non a permission failure rather than retrying through a bypass.\n\n## Finish a green branch\n\nUse `\u002Fskill:maestro-verify` before offering completion choices. Report failing tests\nand repair them before presenting a green finish. Offer:\n\n1. Merge locally, if repository rules allow it and HEAD is on an owned branch.\n2. Open a pull or merge request through `\u002Fskill:maestro-pr`.\n3. Keep the branch and worktree for later, reporting their locations and state.\n\nAt a detached HEAD, omit local merge; explain how the commits will be retained.\nPreserve request and keep worktrees. Remove a worktree only if this run created it,\nits commits are safe and the chosen completion path no longer needs it. Never delete\nan external workspace. If cleanup encounters uncommitted files, refuse forced removal\nand surface choices: preserve, commit intentionally, or explicitly authorize discard.\n\nDiscard is available only when explicitly requested, not as a suggested fourth menu\noption. Explain which commits and files would be lost and require the user to type\n`discard`. Confirm any destructive commands separately as required above. Do not\ninterpret a vague acknowledgement as the typed confirmation.\n","# Preserve work while using Git\n\nRead the repository's merge, release, signing and generated-file rules first. They\nwin over this guidance. Inspect status, branch, remotes and existing worktree metadata\nbefore changing the checkout. Establish who owns the workspace and what must survive.\n\n## Detect isolation before creating it\n\nDistinguish an ordinary checkout, an existing linked worktree, a submodule and an\nexternally managed detached HEAD. Inspect `git worktree list`, the Git directory and\n`git rev-parse --show-superproject-working-tree`; a `.git` file alone is ambiguous.\nUse the host's native isolation where available and respect the user's location\npreference. Reuse suitable existing isolation instead of nesting another worktree.\nA managed detached HEAD is not permission to switch branches or remove its workspace.\n\nFor a manually created local worktree, prefer the repository's existing convention.\nConfirm the directory is ignored with `git check-ignore` before creating it inside\nthe repository. If it is not ignored, obtain the appropriate ignore change first.\nCreate a named short-lived branch, install only the project's documented prerequisites\nand run its baseline checks. Report permission errors or a red baseline; ask how to\nproceed rather than bypassing permissions or treating existing failures as yours.\n\n## Commits and history\n\nKeep branches short-lived and integrate frequently under the repository's policy.\nMake atomic commits whose messages explain why the change exists, not just which\nfiles moved. Keep behaviour-preserving refactors in their own commits, separate from\nfeatures and fixes, so review and revert remain intelligible.\n\nBefore committing, inspect status and the staged diff. Stage only intended files;\nexclude secrets, scratch output, build artifacts and unrelated changes. Review\nnew files and generated output too. Change generation inputs rather than editing\nowned generated records; regenerate through the documented command. Run required\nhooks and checks, and inspect the resulting diff if formatting changes it.\n\nUse `git log`, `git show` and `git blame` to understand an unfamiliar constraint.\nFor a regression with a reproducible predicate, use `git bisect`: mark known good\nand bad revisions, run the same discriminating check at each step, and end with\n`git bisect reset`. Protect uncommitted work before moving history.\n\nFollow the repository's semantic-version policy: patch for compatible fixes, minor\nfor compatible additions, major for breaking changes unless its documented policy\ndiffers. Tags identify immutable releases; do not move a published tag. Let existing\nrelease tooling own version updates, generated changelogs and release notes.\n\n## Permission boundary\n\nObtain user confirmation before push or any use of `reset --hard`, `clean -f`,\n`branch -D`, `checkout .` or `restore .`. Explain the exact target and effect. A\nrequest to finish a feature is not blanket permission to destroy local work. Stop\non a permission failure rather than retrying through a bypass.\n\n## Finish a green branch\n\nUse `\u002Fskill:maestro-verify` before offering completion choices. Report failing tests\nand repair them before presenting a green finish. Offer:\n\n1. Merge locally, if repository rules allow it and HEAD is on an owned branch.\n2. Open a pull or merge request through `\u002Fskill:maestro-pr`.\n3. Keep the branch and worktree for later, reporting their locations and state.\n\nAt a detached HEAD, omit local merge; explain how the commits will be retained.\nPreserve request and keep worktrees. Remove a worktree only if this run created it,\nits commits are safe and the chosen completion path no longer needs it. Never delete\nan external workspace. If cleanup encounters uncommitted files, refuse forced removal\nand surface choices: preserve, commit intentionally, or explicitly authorize discard.\n\nDiscard is available only when explicitly requested, not as a suggested fourth menu\noption. Explain which commits and files would be lost and require the user to type\n`discard`. Confirm any destructive commands separately as required above. Do not\ninterpret a vague acknowledgement as the typed confirmation.\n",{"name":5,"description":7},"main","f33b1a1de12042270a260ffdddd74b67671a1d9a","manifests\u002Fcapabilities\u002Fpractice\u002Fmaestro-skills\u002Fskills\u002Fmaestro-git-workflow","https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro\u002Fmaestro-manifests","https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro","Automated guardrails for faster, better, more maintainable and more secure code. Our Northstar: never reached, always pursued.","2026-11-09 01:08:53",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add Orchestration-Maestro\u002Fmaestro-manifests --skill maestro-git-workflow",{"tool":36,"command":37},"bunx","bunx skills add Orchestration-Maestro\u002Fmaestro-manifests --skill maestro-git-workflow",{"tool":39,"command":40},"pnpm","pnpm dlx skills add Orchestration-Maestro\u002Fmaestro-manifests --skill maestro-git-workflow","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro\u002Fmaestro-manifests\u002Fblob\u002Fmain\u002Fmanifests\u002Fcapabilities\u002Fpractice\u002Fmaestro-skills\u002Fskills\u002Fmaestro-git-workflow\u002FSKILL.md",true,[],[45,52,57,62,67,72],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":18},"01M7DK0KB6JRRJRQPMXG075AQ6","audit","Fixture skill.","https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro\u002Fmaestro-manifests\u002Fblob\u002Fmain\u002Ftests\u002Fscorecard_cases\u002Fskill-without-name-takes-its-folder-name\u002Fmanifests\u002Fcapabilities\u002Fsecurity\u002Fscan\u002Fskills\u002Faudit\u002FSKILL.md",[],[],{"skillNo":53,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":18},"01M7DK0JAQG1J25DG064S7PR27","https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro\u002Fmaestro-manifests\u002Fblob\u002Fmain\u002Ftests\u002Fscorecard_cases\u002Fskill-without-name-takes-its-folder-name\u002Fmanifests\u002Fcapabilities\u002Fpractice\u002Freview\u002Fskills\u002Faudit\u002FSKILL.md",[],[],{"skillNo":58,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":18},"01M7DK0HBNY88V2B7PF5E4JWZS","https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro\u002Fmaestro-manifests\u002Fblob\u002Fmain\u002Ftests\u002Fscorecard_cases\u002Fskill-with-empty-name-takes-its-folder-name\u002Fmanifests\u002Fcapabilities\u002Fsecurity\u002Fscan\u002Fskills\u002Faudit\u002FSKILL.md",[],[],{"skillNo":63,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M7DK0G9CB5MFGRD73SNEXXYE","https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro\u002Fmaestro-manifests\u002Fblob\u002Fmain\u002Ftests\u002Fscorecard_cases\u002Fskill-with-empty-name-takes-its-folder-name\u002Fmanifests\u002Fcapabilities\u002Fpractice\u002Freview\u002Fskills\u002Faudit\u002FSKILL.md",[],[],{"skillNo":68,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M7DK0FA198RVD2KCEW9YDQ6K","https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro\u002Fmaestro-manifests\u002Fblob\u002Fmain\u002Ftests\u002Fscorecard_cases\u002Fskill-in-dot-folder-is-skipped\u002Fmanifests\u002Fcapabilities\u002Fpractice\u002Freview\u002Fskills\u002Faudit\u002FSKILL.md",[],[],{"skillNo":73,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M7DK0EAZVV9A5CN27PD2MTMB","https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro\u002Fmaestro-manifests\u002Fblob\u002Fmain\u002Ftests\u002Fscorecard_cases\u002Fskill-in-dot-folder-is-skipped\u002Fmanifests\u002Fcapabilities\u002Fpractice\u002Freview\u002Fskills\u002F.drafts\u002Faudit\u002FSKILL.md",[],[]]