[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69AGPFYNFG8Y89TV3820FZ4":3,"skill-same:01M69AGPFYNFG8Y89TV3820FZ4":61},{"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":32,"linkOnly":33,"markdownContent":34,"markdownBody":35,"frontMatter":36,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":42,"ownerHtmlUrl":43,"ownerBlogUrl":44,"ownerDescription":45,"updatedAt":46,"install":47,"resources":60},"01M69AGPFYNFG8Y89TV3820FZ4","finishing-a-development-branch",null,"Use this when you have completed some feature implementation and have written passing tests, and you are ready to create a PR.","microsoft\u002FFluidFramework","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69AG0BQKNGBJQ5YNG09HXXW",4949,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.agency\u002Fplugins\u002Fnori\u002Fskills\u002Ffinishing-a-development-branch\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31],"finishing a development branch","development","branch","pr","create","use","ready","implementation","feature implementation","tests","feature","you","when","2026-11-10 10:12:30",false,"---\nname: finishing-a-development-branch\ndescription: Use this when you have completed some feature implementation and have written passing tests, and you are ready to create a PR.\n---\n\n\u003Crequired>\n*CRITICAL* Add the following steps to your Todo list using TodoWrite:\n\n1. Use the Task tool to verify tests by using the project's test suite.\n\n```bash\n# Run project's test suite\nnpm test \u002F cargo test \u002F pytest \u002F go test .\u002F...\n```\n\n**If tests fail:**\n\n```\nTests failing (\u003CN> failures). Must fix before creating PR:\n\n[Show failures]\n\nCannot proceed until tests pass.\n```\n\n2. Confirm that there is some formatting\u002Flint\u002Ftypechecking in the project. If NONE of these exist, ask me if there was something that you missed.\n\n3. Use the Task tool to run any formatters and fix issues in a subagent.\n\n```bash\n# Node.js\u002FJavaScript\u002FTypeScript\nls package.json 2>\u002Fdev\u002Fnull && jq -r '.scripts | keys[]' package.json | grep -E 'format|lint'\n\n# Rust\nls rustfmt.toml .rustfmt.toml 2>\u002Fdev\u002Fnull\n\n# Python\nls .flake8 pyproject.toml setup.cfg 2>\u002Fdev\u002Fnull\n\n# Go\nls .golangci.yml .golangci.yaml 2>\u002Fdev\u002Fnull\n```\n\n4. Use the Task tool to run any linters and fix issues in a subagent.\n\n```bash\n# Node.js - check package.json scripts\nnpm run lint  # or: npm run lint:fix, npm run eslint\n\n# Rust\ncargo clippy --fix --allow-dirty --allow-staged\n\n# Python\nruff check --fix .\n# or: flake8 ., pylint .\n\n# Go\ngolangci-lint run --fix\n```\n\n5. Use the Task tool to run type checking and fix issues in a subagent.\n\n6. Use the nori-code-reviewer subagent to do a self review. You do *NOT* have to follow the subagent's suggestions. This is merely a way to get a fresh pair of eyes on the code.\n\n7. Run the test-scenario-hygiene skill in a subagent to do test review. You do *NOT* have to follow the subagent's suggestions. This is merely a way to get a fresh pair of eyes on the code.\n\n8. Confirm that you are not on the main branch. If you are, ask me before proceeding. NEVER push to main without permission.\n\n9. Push and create a PR.\n\n```bash\n# Push branch\ngit push -u origin \u003Cfeature-branch>\n\n# Create PR\ngh pr create --title \"\u003Ctitle>\" --body \"$(cat \u003C\u003C'EOF'\n## Summary\n? Generated with [Nori](https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fnori-ai)\n\n\u003C2-3 bullets of what changed>\n\n## Test Plan\n- [ ] \u003Cverification steps>\n\nShare Nori with your team: https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fnori-skillsets\nEOF\n)\"\n```\n\n10. Merge main and resolve conflicts if necessary.\n\n```bash\ngit fetch && git merge main\n```\n\n11. Make sure the PR branch CI succeeds.\n\n\u003Csystem-reminder> If you do not see any CI, this is likely because of merge conflicts. Go back to step 10. \u003C\u002Fsystem-reminder>\n\n```bash\n# Check if the PR CI succeeded\ngh pr checks\n\n# If it is still running, sleep and check again\nsleep 60 && gh pr checks\n```\n\nIf CI did not pass, examine why and fix the issue.\n\n- Make changes as needed, push a new commit, and repeat the process.\n\u003Csystem-reminder> It is *critical* that you fix any ci issues, EVEN IF YOU DID NOT CAUSE THEM. \u003C\u002Fsystem-reminder>\n\n12. If this was a change to a webapp, spin up the server and the ui in a demo localhost link and show me the link so that I can review the changes.\n\u003Csystem-reminder> If you are in a worktree, make sure you copy any gitignored env or config files that are necessary to start the server \u003C\u002Fsystem-reminder>\n\u003C\u002Frequired>\n","\u003Crequired>\n*CRITICAL* Add the following steps to your Todo list using TodoWrite:\n\n1. Use the Task tool to verify tests by using the project's test suite.\n\n```bash\n# Run project's test suite\nnpm test \u002F cargo test \u002F pytest \u002F go test .\u002F...\n```\n\n**If tests fail:**\n\n```\nTests failing (\u003CN> failures). Must fix before creating PR:\n\n[Show failures]\n\nCannot proceed until tests pass.\n```\n\n2. Confirm that there is some formatting\u002Flint\u002Ftypechecking in the project. If NONE of these exist, ask me if there was something that you missed.\n\n3. Use the Task tool to run any formatters and fix issues in a subagent.\n\n```bash\n# Node.js\u002FJavaScript\u002FTypeScript\nls package.json 2>\u002Fdev\u002Fnull && jq -r '.scripts | keys[]' package.json | grep -E 'format|lint'\n\n# Rust\nls rustfmt.toml .rustfmt.toml 2>\u002Fdev\u002Fnull\n\n# Python\nls .flake8 pyproject.toml setup.cfg 2>\u002Fdev\u002Fnull\n\n# Go\nls .golangci.yml .golangci.yaml 2>\u002Fdev\u002Fnull\n```\n\n4. Use the Task tool to run any linters and fix issues in a subagent.\n\n```bash\n# Node.js - check package.json scripts\nnpm run lint  # or: npm run lint:fix, npm run eslint\n\n# Rust\ncargo clippy --fix --allow-dirty --allow-staged\n\n# Python\nruff check --fix .\n# or: flake8 ., pylint .\n\n# Go\ngolangci-lint run --fix\n```\n\n5. Use the Task tool to run type checking and fix issues in a subagent.\n\n6. Use the nori-code-reviewer subagent to do a self review. You do *NOT* have to follow the subagent's suggestions. This is merely a way to get a fresh pair of eyes on the code.\n\n7. Run the test-scenario-hygiene skill in a subagent to do test review. You do *NOT* have to follow the subagent's suggestions. This is merely a way to get a fresh pair of eyes on the code.\n\n8. Confirm that you are not on the main branch. If you are, ask me before proceeding. NEVER push to main without permission.\n\n9. Push and create a PR.\n\n```bash\n# Push branch\ngit push -u origin \u003Cfeature-branch>\n\n# Create PR\ngh pr create --title \"\u003Ctitle>\" --body \"$(cat \u003C\u003C'EOF'\n## Summary\n? Generated with [Nori](https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fnori-ai)\n\n\u003C2-3 bullets of what changed>\n\n## Test Plan\n- [ ] \u003Cverification steps>\n\nShare Nori with your team: https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fnori-skillsets\nEOF\n)\"\n```\n\n10. Merge main and resolve conflicts if necessary.\n\n```bash\ngit fetch && git merge main\n```\n\n11. Make sure the PR branch CI succeeds.\n\n\u003Csystem-reminder> If you do not see any CI, this is likely because of merge conflicts. Go back to step 10. \u003C\u002Fsystem-reminder>\n\n```bash\n# Check if the PR CI succeeded\ngh pr checks\n\n# If it is still running, sleep and check again\nsleep 60 && gh pr checks\n```\n\nIf CI did not pass, examine why and fix the issue.\n\n- Make changes as needed, push a new commit, and repeat the process.\n\u003Csystem-reminder> It is *critical* that you fix any ci issues, EVEN IF YOU DID NOT CAUSE THEM. \u003C\u002Fsystem-reminder>\n\n12. If this was a change to a webapp, spin up the server and the ui in a demo localhost link and show me the link so that I can review the changes.\n\u003Csystem-reminder> If you are in a worktree, make sure you copy any gitignored env or config files that are necessary to start the server \u003C\u002Fsystem-reminder>\n\u003C\u002Frequired>\n",{"name":5,"description":7},"main","5e94cbfa27965a98428f7d26b69dd5b0a8abeb0d",".agency\u002Fplugins\u002Fnori\u002Fskills\u002Ffinishing-a-development-branch",590,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework","https:\u002F\u002Ffluidframework.com","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-14 08:12:05",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add microsoft\u002FFluidFramework --skill finishing-a-development-branch",{"tool":53,"command":54},"bunx","bunx skills add microsoft\u002FFluidFramework --skill finishing-a-development-branch",{"tool":56,"command":57},"pnpm","pnpm dlx skills add microsoft\u002FFluidFramework --skill finishing-a-development-branch","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.agency\u002Fplugins\u002Fnori\u002Fskills\u002Ffinishing-a-development-branch\u002FSKILL.md",true,[],[62,82,120,143,161,184],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":32},"01M6PJ5SAHYFZFWDG5Y4RW56EP","trigger-pipelines-for-copilot-pr","Trigger ADO pipelines for a Copilot-created PR by posting \u002Fazp run comments. Use when the user asks to trigger CI pipelines for a specific PR.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftrigger-pipelines-for-copilot-pr\u002FSKILL.md",[],[22,69,70,71,72,73,74,75,76,77,24,78,79,80,81,31],"trigger pipelines for copilot pr","for","trigger","copilot","pipelines","ado","posting","run","ci","number","URL","comments","user",{"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":101,"publishedAt":32},"01M6PJ5M4ZG7E78C4GM4041HEP","review","Review changes relative to a prior state, such as a diff, pull request, branch, commit, or working-tree changes. Use for change-focused code review and regression analysis. Do not use to assess an existing file, API, design, implementation, or other artifact without a comparison; if the request is ambiguous, ask whether the user wants a change review and what prior state to compare against.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Freview\u002FSKILL.md",[88,93,96],{"categoryNo":89,"categoryName":90,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":94,"categoryName":95,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":97,"categoryName":98,"taxonomyType":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[84,21,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,70,118,119],"regression","code review","design","ask","analysis","code","commit","api","change","artifact","request","pull","tree","as","do","diff","assess","ambiguous",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":129,"publishedAt":32},"01M6PJ5E3PCBDS319FFMHPFACN","review-pr-local","The authority on pulling a pull request — Azure DevOps or GitHub — into an isolated local worktree so a human can review it in their editor, and on posting human-controlled review comments back to the PR (ADO via the ado PR-thread MCP tools or the Azure DevOps REST API, GitHub via the gh CLI). Auto-detects the platform and all identifiers from the PR URL; not tied to any specific repository. The AI assists an interactive human review and only ever posts comments the human explicitly requests. If you find yourself checking out a PR branch over the user's own working tree, or posting AI-authored review prose the human did not ask for, invoke this skill instead.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Freview-pr-local\u002FSKILL.md",[126],{"categoryNo":127,"categoryName":128,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000023","Skill与智能体开发",[130,84,22,131,132,133,21,134,135,136,137,138,139,140,79,30,105,109,141,142],"local","review pr local","review pr","back","posts","only","MCP","authority","auto","invoke","azure devops","cli","worktree",{"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":32},"01M6PJ5AVZAS0AEBPCYJZ9ZMMD","policy-check","This skill should be used when the user asks to \"run policy check\", \"check policy\", \"policy-check\", or needs to validate package compliance. Provides guidance on running policy checks for specific packages or the entire repository.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fpolicy-check\u002FSKILL.md",[],[150,151,152,153,154,70,76,155,156,157,158,81,159,31,160],"policy check","policy","check","packages","compliance","repository","guidance","validate","package","running","entire",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":170,"publishedAt":32},"01M6PJ54H068MZF2WD2JDKCVDC","pipeline-test-triage","Triage test failures in an Azure DevOps pipeline run for Fluid Framework. Use when the user shares an ADO build\u002Fpipeline URL or build ID and wants failures analyzed, when they ask \"why did this pipeline fail\", \"summarize the test failures\", \"is this test flaky or a real bug\", \"compare these runs\", or wants bugs filed for genuine failures. Covers the Real Service End to End Tests pipeline as the worked example but applies to any FF test pipeline.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fpipeline-test-triage\u002FSKILL.md",[167],{"categoryNo":168,"categoryName":169,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000008","测试与质量",[171,172,173,174,175,176,177,178,140,79,105,76,179,180,181,182,74,115,183,70,31],"pipeline","test triage","pipeline test triage","pipeline test","test","triage","end","test pipeline","why","bug","but","framework","bugs",{"skillNo":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":188,"categories":189,"keywords":190,"publishedAt":32},"01M6PJ4ZJASDV2CGQTG1JWKBFE","fluid-release","Fluid Framework client release group — minor releases, patch releases, and post-release type test updates. Covers release prep, branching, version bumps, changelogs, release notes, and type test baselines. In autonomous mode, auto-detects state from the repo, attempts to execute, and falls back to a GitHub issue on failure. Triggers on \"release\", \"do the release\", \"release status\", version bump, release notes, changelog, release branch, or release engineering.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ffluid-release\u002FSKILL.md",[],[191,192,193,133,21,194,195,196,197,198,138,199,200,201,202,203,204,205,206,207],"release","fluid release","fluid","bump","mode","autonomous","release notes","release status","updates","patch","notes","changelog","release prep","releases","status","issue","branching"]