[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69AGJ9D04F0D4R2JJGJK2N5":3,"skill-same:01M69AGJ9D04F0D4R2JJGJK2N5":66},{"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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":47,"ownerHtmlUrl":48,"ownerBlogUrl":49,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M69AGJ9D04F0D4R2JJGJK2N5","creating-debug-tests-and-iterating",null,"Use this skill when faced with a difficult debugging task where you need to replicate some bug or behavior in order to see what is going wrong.","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\u002Fcreating-debug-tests-and-iterating\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36],"debug","creating debug tests and iterating","tests","debugging","replicate","behavior","use","bug","task","with","you","Wrong","when","2026-11-10 10:12:30",false,"---\nname: creating-debug-tests-and-iterating\ndescription: Use this skill when faced with a difficult debugging task where you need to replicate some bug or behavior in order to see what is going wrong.\n---\n\n\u003Crequired>\n*CRITICAL* Add the following steps to your Todo list using TodoWrite:\n\n\u003Csystem-reminder>From this point on, ignore any existing tests until you have a working example validated through a new test file.\u003C\u002Fsystem-reminder>\n1. Write a script that interacts with the application *from the outside*. The script should not call any internals. It should only interact with the external interfaces.\n2. Check to see if you require authentication. If you do, ask me for credentials.\n\u003Csystem-reminder>Do NOT use mock mode or test harnesses. You should be testing the real thing.\u003C\u002Fsystem-reminder>\n3. Follow these steps in a loop until the bug is fixed:\n  - Add many logs to the application. You *MUST* do this on every loop.\n  - Run the debug script.\n  - Analyze the output: read logs, identify errors, do whatever you need to.\n  - Update the debug script.\n\u003Csystem-reminder>If you get stuck: did you add logs?\u003C\u002Fsystem-reminder>\n5. Identify and fix the issue at hand.\n6. Clean up all background jobs, and remove extraneous logs.\n7. Make sure other tests pass.\n\u003C\u002Frequired>\n\n# Debug Testing\n\nTo test different kinds of applications, write scripts that test the\napplication interfaces. Your testing should be as close to 'real' as possible.\n\n## Example\n\nIdentify the application boundary to be tested and the tools you need to test\nit.\n\n**CLI Tool:**\n\n```bash\n.\u002Fpath\u002Fto\u002Fcli.sh arg1 arg2\n```\n\n```python\nsubprocess.run([\".\u002Fpath\u002Fto\u002Fcli.sh\", \"arg1\", \"arg2\"])\n```\n\n```node\nexec('.\u002Fpath\u002Fto\u002Fcli.sh', (error, stdout, stderr) => {\n  if (error) {\n    console.error(`exec error: ${error}`);\n    return;\n  }\n  console.log(`stdout: ${stdout}`);\n  console.error(`stderr: ${stderr}`);\n});\n```\n\n**API:**\n\nStart the server:\n```bash\ncd backend && python server.py&\ncd frontend && npm run dev&\n```\n\nCall to the server using scripting language of choice.\n\nDo NOT get in a loop where you just keep running other tests. In this mode, you\nshould ignore other tests entirely until it works.\n\n# Emulators for testing\n\nWeb servers or web apps: use Playwright (read `.agency\u002Fplugins\u002Fnori\u002Fskills\u002Fwebapp-testing\u002FSKILL.md`)\nTUI tools: use tmux with screen capture\nCLI tools: use bash\n","\u003Crequired>\n*CRITICAL* Add the following steps to your Todo list using TodoWrite:\n\n\u003Csystem-reminder>From this point on, ignore any existing tests until you have a working example validated through a new test file.\u003C\u002Fsystem-reminder>\n1. Write a script that interacts with the application *from the outside*. The script should not call any internals. It should only interact with the external interfaces.\n2. Check to see if you require authentication. If you do, ask me for credentials.\n\u003Csystem-reminder>Do NOT use mock mode or test harnesses. You should be testing the real thing.\u003C\u002Fsystem-reminder>\n3. Follow these steps in a loop until the bug is fixed:\n  - Add many logs to the application. You *MUST* do this on every loop.\n  - Run the debug script.\n  - Analyze the output: read logs, identify errors, do whatever you need to.\n  - Update the debug script.\n\u003Csystem-reminder>If you get stuck: did you add logs?\u003C\u002Fsystem-reminder>\n5. Identify and fix the issue at hand.\n6. Clean up all background jobs, and remove extraneous logs.\n7. Make sure other tests pass.\n\u003C\u002Frequired>\n\n# Debug Testing\n\nTo test different kinds of applications, write scripts that test the\napplication interfaces. Your testing should be as close to 'real' as possible.\n\n## Example\n\nIdentify the application boundary to be tested and the tools you need to test\nit.\n\n**CLI Tool:**\n\n```bash\n.\u002Fpath\u002Fto\u002Fcli.sh arg1 arg2\n```\n\n```python\nsubprocess.run([\".\u002Fpath\u002Fto\u002Fcli.sh\", \"arg1\", \"arg2\"])\n```\n\n```node\nexec('.\u002Fpath\u002Fto\u002Fcli.sh', (error, stdout, stderr) => {\n  if (error) {\n    console.error(`exec error: ${error}`);\n    return;\n  }\n  console.log(`stdout: ${stdout}`);\n  console.error(`stderr: ${stderr}`);\n});\n```\n\n**API:**\n\nStart the server:\n```bash\ncd backend && python server.py&\ncd frontend && npm run dev&\n```\n\nCall to the server using scripting language of choice.\n\nDo NOT get in a loop where you just keep running other tests. In this mode, you\nshould ignore other tests entirely until it works.\n\n# Emulators for testing\n\nWeb servers or web apps: use Playwright (read `.agency\u002Fplugins\u002Fnori\u002Fskills\u002Fwebapp-testing\u002FSKILL.md`)\nTUI tools: use tmux with screen capture\nCLI tools: use bash\n",{"name":5,"description":7},"main","8809386f7af487f40be7dcbea5d0e4afc37efd0a",".agency\u002Fplugins\u002Fnori\u002Fskills\u002Fcreating-debug-tests-and-iterating",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":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add microsoft\u002FFluidFramework --skill creating-debug-tests-and-iterating",{"tool":58,"command":59},"bunx","bunx skills add microsoft\u002FFluidFramework --skill creating-debug-tests-and-iterating",{"tool":61,"command":62},"pnpm","pnpm dlx skills add microsoft\u002FFluidFramework --skill creating-debug-tests-and-iterating","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.agency\u002Fplugins\u002Fnori\u002Fskills\u002Fcreating-debug-tests-and-iterating\u002FSKILL.md",true,[],[67,88,123,146,164,186],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":37},"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",[],[74,75,76,77,78,79,80,81,82,83,30,84,85,86,87,36],"pr","trigger pipelines for copilot pr","for","trigger","copilot","pipelines","ado","posting","run","ci","number","URL","comments","user",{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":103,"publishedAt":37},"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",[94,99,102],{"categoryNo":95,"categoryName":96,"taxonomyType":97,"taxonomyTypeDesc":98},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":100,"categoryName":101,"taxonomyType":97,"taxonomyTypeDesc":98},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[90,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,76,121,122],"branch","regression","code review","design","ask","analysis","code","commit","api","change","artifact","request","pull","tree","as","do","diff","assess","ambiguous",{"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":132,"publishedAt":37},"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",[129],{"categoryNo":130,"categoryName":131,"taxonomyType":97,"taxonomyTypeDesc":98},"01JBSEEDCAT000000000000023","Skill与智能体开发",[133,90,74,134,135,136,104,137,138,139,140,141,142,143,85,34,108,112,144,145],"local","review pr local","review pr","back","posts","only","MCP","authority","auto","invoke","azure devops","cli","worktree",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":37},"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",[],[153,154,155,156,157,76,82,158,159,160,161,87,162,36,163],"policy check","policy","check","packages","compliance","repository","guidance","validate","package","running","entire",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":173,"publishedAt":37},"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",[170],{"categoryNo":171,"categoryName":172,"taxonomyType":97,"taxonomyTypeDesc":98},"01JBSEEDCAT000000000000008","测试与质量",[174,175,176,177,178,179,180,181,143,85,108,82,182,31,183,184,80,118,185,76,36],"pipeline","test triage","pipeline test triage","pipeline test","test","triage","end","test pipeline","why","but","framework","bugs",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":192,"publishedAt":37},"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",[],[193,194,195,136,104,196,197,198,199,200,141,201,202,203,204,205,206,207,208,209],"release","fluid release","fluid","bump","mode","autonomous","release notes","release status","updates","patch","notes","changelog","release prep","releases","status","issue","branching"]