[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B9P8EXVVVKPMVJXWAFFF28":3,"skill-same:01M7B9P8EXVVVKPMVJXWAFFF28":47},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":46},"01M7B9P8EXVVVKPMVJXWAFFF28","analyze-session",null,"Opens a WinUI Profiler session file (.sqlite) and answers questions about a WinUI 3 app's performance from it with the winui-profiler tools: how the launch went, UI-thread ticks and slow ticks, regions of interest (navigations, flyouts and dialogs opening, focus changes), and the UI elements and composition visuals the events mention. Use it when someone asks why a WinUI app is slow to start or draws slowly, what a tick did, what happened around a navigation or to an element, or what a session holds, and for \u002Fwinui-profiler:analyze-session [session.sqlite | folder].","microsoft\u002Fmicrosoft-ui-xaml","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M6WZRE552HV7ZQFPSHT97PZA",8604,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fmicrosoft-ui-xaml\u002Fblob\u002Fmain\u002Ftools\u002FWinUIProfiler\u002Fskills\u002Fanalyze-session\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: analyze-session\ndescription: >-\n  Opens a WinUI Profiler session file (.sqlite) and answers questions about a\n  WinUI 3 app's performance from it with the winui-profiler tools: how the\n  launch went, UI-thread ticks and slow ticks, regions of interest\n  (navigations, flyouts and dialogs opening, focus changes), and the UI\n  elements and composition visuals the events mention. Use it when someone\n  asks why a WinUI app is slow to start or draws slowly, what a tick did, what\n  happened around a navigation or to an element, or what a session holds, and\n  for \u002Fwinui-profiler:analyze-session [session.sqlite | folder].\nuser-invocable: true\n---\n\n# Analyze a WinUI Profiler session\n\nThe WinUI Profiler app (`tools\u002FWinUIProfiler` in the microsoft-ui-xaml\nrepository) records one WinUI 3 process into a session file. Its processors\nstore each UI thread's ticks, the regions of interest, and the UI elements\nand composition visuals the events mention. The winui-profiler tools read\nthem, even while the app is still recording, and never change the file.\n\n## Pick the session\n\n`\u002Fwinui-profiler:analyze-session [target]` opens a session; the target is the\ntext after the command. A question, with or without the command, is about\nthe session file it names, or else the newest one.\n\n- **A `.sqlite` file:** call `sessions` with view `summary` and `sessionPath`\n  set to it. A file name alone means one in the sessions folder,\n  `%LOCALAPPDATA%\\WinUIProfiler\\Sessions`.\n- **Nothing:** call `sessions` with view `summary` and no `sessionPath`. It\n  reads the newest file in the sessions folder; say which file that is.\n- **A folder:** call `sessions` with view `list` and `folder`. Show the\n  sessions (file, process, coverage, start, how it ended, events), ask which\n  one to open, and stop.\n- **A `.etl` file:** the tools don't read traces. Say how to read it into a\n  session file (Getting a session, below), and stop.\n\nIf the session can't be read, give the tool's error, offer `sessions` with\nview `list`, and stop. Pass the file the summary read as `sessionPath` to\nevery later call, so that every answer comes from the same file: the newest\nfile changes when the app starts another recording.\n\nWhen the command only opened a session, reply briefly from its summary, then\nstop and call nothing else until the user asks a question:\n\n- the file, and the process (name and ID);\n- the coverage, and how the recording ended, or that it's still recording;\n- the time span, and the stored events, ticks, elements and visuals;\n- which analyses have data, and why the others don't;\n- the notes that limit answers, such as lost or deleted events;\n- two or three questions the session can answer, from the analyses it has.\n\n## Answer a question\n\n1. Call `sessions` with view `summary` first, once per session. Its\n   `analyses` say which tools and views have data and, when one hasn't, why;\n   its `notes` say what limits the answers.\n2. Call only the views the question needs, as the table below says. Lists are\n   capped by `limit`; a result with `nextOffset` continues from `offset`.\n3. Answer only from what the tools return. Give numbers with their units, and\n   the tick, region, thread or object they belong to.\n4. Say what was read: the file, the process and the time base. Pass on the\n   notes that change the answer: still recording, events lost or dropped, the\n   oldest events deleted, a session that starts at the connection.\n5. End with How I got this.\n\n| Question | Call |\n| --- | --- |\n| Which sessions are there? | `sessions`, view `list` |\n| What does the session hold? How long does it run? | `sessions`, view `summary` (its `uiThreads`) |\n| How did the launch go? | `launch`, view `milestones` |\n| How soon did the first frames draw? | `launch`, view `frames` |\n| Does the app draw slowly? | `frames`, view `summary`, then `slowest` |\n| What did one slow tick do? | `frames`, view `tick` with its `tickId` |\n| What happened when a page, flyout or dialog opened? | `frames`, view `regions`, then `rows` with its `regionId`, then `tick` for the tick it ends with |\n| When did layout passes, navigations or focus changes happen? | `frames`, view `rows` with `type` |\n| Which elements and visuals were there? | `objects`, view `types`, then `list` |\n| What happened to one element or visual? | `objects`, view `history` |\n\n## How I got this\n\nEnd every reply, including a session's summary, a list of sessions and an\nerror, with a section headed **How I got this**, which shows how the answer\ncame from the session file. The tools don't take SQL: each view runs fixed\nstatements, with the arguments' values written in, then sorts, groups,\ncounts and pages their rows in code. Each result says how: `queries` lists\nthe statements the call ran, each once, and `computed` says what the call\ndid with their rows.\n\n1. Name the session file, and say that each statement runs on it as is,\n   read-only, with `sqlite3 -readonly \u003Cfile>`. For `sessions` view `list`,\n   name the folder: its statement ran once on each file it lists that could\n   be read. The first time in a conversation that a statement you show reads\n   `InterestingRows`, `InterestingRowEvents` or `FrameList`, add that SQLite\n   3.54.0 and 3.54.1 can't run it (\"VIEWs and\u002For subqueries nested too\n   deep\"), but another version, such as 3.53, can.\n2. Then each call the answer used, in the order they were made: the tool, the\n   view and the arguments passed. Under it, each of its `queries` in order:\n   its `sql`, copied exactly, in a code block marked `sql`; after the block,\n   its `rows` (of all its runs), its `runs` when it ran more than once, and\n   its `files` when the result gives them. Then the call's `computed`, copied\n   exactly, after \"Then:\".\n3. Last, one or two sentences on how those results led to the answer.\n\nRules:\n\n- Copy each `sql` and `computed` exactly as the tool returned them. Never\n  write, shorten, reformat or reconstruct SQL, and never show a statement no\n  tool returned. Don't add to a `computed`: what you conclude from the\n  results goes in the last step.\n- A call whose `queries` is empty ran no SQL; say so. A call that failed\n  returns only its error: give the error, and don't guess what it ran.\n- Show a statement once per answer. When a later call ran it again, say\n  which call showed it. When an answer needed no new call, name the earlier\n  calls it came from.\n- The statements read the file as it was. A session still being recorded can\n  return more rows when one is run again.\n- If the user asks not to see the section, leave it out until they ask for it\n  again.\n\n## Reading the results\n\n- **Ticks.** A tick drew when XAML's frame counter moved on by the thread's\n  next tick, so whether the latest tick drew isn't known. That isn't proof\n  that a frame reached the screen: report tick durations and slow ticks, and\n  don't call frames dropped. Slow means more than 16.7 ms, a frame at 60 Hz;\n  the display's refresh rate isn't recorded.\n- **Tick times** are wall-clock time on the UI thread, not CPU time: a long\n  tick may have been waiting, and nothing in a session says on what. Events\n  on render and decode threads, and on threads that never tick, belong to no\n  tick.\n- **Types.** An element's type is the nearest built-in type, so an app's own\n  control shows as its base class, unless only a template, Loaded or render\n  event named it. A render event's name has no namespace, so one type can\n  have two rows, such as `TransitionRoot` and\n  `Microsoft.UI.Xaml.TransitionRoot` (`type` `TransitionRoot` lists both).\n  Objects no event gave a type are marked `typeUnknown`, which isn't a type\n  of its own. A freed object's address can be reused: `history` then lists\n  the objects that had it, and asks for one's `objectId`.\n- **Builds.** Ticks, regions and launch come from Microsoft-Windows-XAML in\n  every WinUI build. Current builds write the Microsoft-Windows-XAML-Profiler\n  events whenever a session enables the provider. Older builds wrote most of\n  them only with `XamlProfilerEnabled`, which WinUI's own build set for Debug\n  builds only, so a session of an older Release build has no visuals; its\n  elements come from the Microsoft-Windows-XAML events that name them. A\n  visual has a name, its owner element's label, only in older builds.\n- **Times** are in milliseconds from the origin `session.timeBase` gives: for\n  a live session, the start of the recording; for a trace, the process's\n  first event in it. It also says when the process was created, when known:\n  for a launch recorded from process start, or a trace with the kernel's\n  process events, as a WPR trace has. `launch` then gives\n  `msFromProcessStart`, unless the session starts at the connection, and\n  `measuredFrom` says what its frames count from.\n- **Length.** Each of the summary's `uiThreads` says when its first tick\n  started (`firstStartMs`) and its last finished tick ended (`lastEndMs`).\n  For a live session, `startedUtc` to `endedUtc` is how long the recording\n  ran. For a session read from a trace, they're when the trace was read, not\n  when it was recorded, which the file doesn't say.\n- **Limits.** One process per session. A session file is limited to 500 MB:\n  past it, the oldest events are deleted, and the summary says from which\n  event the file is complete.\n\n## What the tools can't answer\n\nThese aren't stored, so say so, and don't estimate them from other data:\n\n- the events' field values, and counts of raw events by provider;\n- GPU memory, CPU samples and call stacks, context switches and thread waits;\n- the XAML and composition trees;\n- the Launch tab's milestones from the marker configuration, such as an app's\n  own markers (a marker event fired on a UI thread shows only among its\n  tick's events, in the Other bucket; one fired on another thread doesn't);\n- other processes, such as the one that launched the app.\n\n## Getting a session\n\n- **Record it in the WinUI Profiler app.** The connection modes **Unpackaged\n  executable** and **Packaged application** launch the app after the session\n  starts; **Attach to process ID** starts at the connection, after most of\n  the launch. Recording live needs an elevated WinUI Profiler, or the local\n  Performance Log Users group. Sessions are saved in the sessions folder,\n  named `\u003Cdate>-\u003Ctime>-\u003Cprocess>-\u003Cpid>.sqlite`.\n- **Read a trace (.etl) into one,** which needs no elevation: in the app,\n  with the connection mode **Recorded trace (.etl)**, then **Open trace**, or\n  with the WinUI Profiler CLI's\n  `record \u003Ctrace.etl> --pid \u003Cpid> --out \u003Csession.sqlite>`.\n","# Analyze a WinUI Profiler session\n\nThe WinUI Profiler app (`tools\u002FWinUIProfiler` in the microsoft-ui-xaml\nrepository) records one WinUI 3 process into a session file. Its processors\nstore each UI thread's ticks, the regions of interest, and the UI elements\nand composition visuals the events mention. The winui-profiler tools read\nthem, even while the app is still recording, and never change the file.\n\n## Pick the session\n\n`\u002Fwinui-profiler:analyze-session [target]` opens a session; the target is the\ntext after the command. A question, with or without the command, is about\nthe session file it names, or else the newest one.\n\n- **A `.sqlite` file:** call `sessions` with view `summary` and `sessionPath`\n  set to it. A file name alone means one in the sessions folder,\n  `%LOCALAPPDATA%\\WinUIProfiler\\Sessions`.\n- **Nothing:** call `sessions` with view `summary` and no `sessionPath`. It\n  reads the newest file in the sessions folder; say which file that is.\n- **A folder:** call `sessions` with view `list` and `folder`. Show the\n  sessions (file, process, coverage, start, how it ended, events), ask which\n  one to open, and stop.\n- **A `.etl` file:** the tools don't read traces. Say how to read it into a\n  session file (Getting a session, below), and stop.\n\nIf the session can't be read, give the tool's error, offer `sessions` with\nview `list`, and stop. Pass the file the summary read as `sessionPath` to\nevery later call, so that every answer comes from the same file: the newest\nfile changes when the app starts another recording.\n\nWhen the command only opened a session, reply briefly from its summary, then\nstop and call nothing else until the user asks a question:\n\n- the file, and the process (name and ID);\n- the coverage, and how the recording ended, or that it's still recording;\n- the time span, and the stored events, ticks, elements and visuals;\n- which analyses have data, and why the others don't;\n- the notes that limit answers, such as lost or deleted events;\n- two or three questions the session can answer, from the analyses it has.\n\n## Answer a question\n\n1. Call `sessions` with view `summary` first, once per session. Its\n   `analyses` say which tools and views have data and, when one hasn't, why;\n   its `notes` say what limits the answers.\n2. Call only the views the question needs, as the table below says. Lists are\n   capped by `limit`; a result with `nextOffset` continues from `offset`.\n3. Answer only from what the tools return. Give numbers with their units, and\n   the tick, region, thread or object they belong to.\n4. Say what was read: the file, the process and the time base. Pass on the\n   notes that change the answer: still recording, events lost or dropped, the\n   oldest events deleted, a session that starts at the connection.\n5. End with How I got this.\n\n| Question | Call |\n| --- | --- |\n| Which sessions are there? | `sessions`, view `list` |\n| What does the session hold? How long does it run? | `sessions`, view `summary` (its `uiThreads`) |\n| How did the launch go? | `launch`, view `milestones` |\n| How soon did the first frames draw? | `launch`, view `frames` |\n| Does the app draw slowly? | `frames`, view `summary`, then `slowest` |\n| What did one slow tick do? | `frames`, view `tick` with its `tickId` |\n| What happened when a page, flyout or dialog opened? | `frames`, view `regions`, then `rows` with its `regionId`, then `tick` for the tick it ends with |\n| When did layout passes, navigations or focus changes happen? | `frames`, view `rows` with `type` |\n| Which elements and visuals were there? | `objects`, view `types`, then `list` |\n| What happened to one element or visual? | `objects`, view `history` |\n\n## How I got this\n\nEnd every reply, including a session's summary, a list of sessions and an\nerror, with a section headed **How I got this**, which shows how the answer\ncame from the session file. The tools don't take SQL: each view runs fixed\nstatements, with the arguments' values written in, then sorts, groups,\ncounts and pages their rows in code. Each result says how: `queries` lists\nthe statements the call ran, each once, and `computed` says what the call\ndid with their rows.\n\n1. Name the session file, and say that each statement runs on it as is,\n   read-only, with `sqlite3 -readonly \u003Cfile>`. For `sessions` view `list`,\n   name the folder: its statement ran once on each file it lists that could\n   be read. The first time in a conversation that a statement you show reads\n   `InterestingRows`, `InterestingRowEvents` or `FrameList`, add that SQLite\n   3.54.0 and 3.54.1 can't run it (\"VIEWs and\u002For subqueries nested too\n   deep\"), but another version, such as 3.53, can.\n2. Then each call the answer used, in the order they were made: the tool, the\n   view and the arguments passed. Under it, each of its `queries` in order:\n   its `sql`, copied exactly, in a code block marked `sql`; after the block,\n   its `rows` (of all its runs), its `runs` when it ran more than once, and\n   its `files` when the result gives them. Then the call's `computed`, copied\n   exactly, after \"Then:\".\n3. Last, one or two sentences on how those results led to the answer.\n\nRules:\n\n- Copy each `sql` and `computed` exactly as the tool returned them. Never\n  write, shorten, reformat or reconstruct SQL, and never show a statement no\n  tool returned. Don't add to a `computed`: what you conclude from the\n  results goes in the last step.\n- A call whose `queries` is empty ran no SQL; say so. A call that failed\n  returns only its error: give the error, and don't guess what it ran.\n- Show a statement once per answer. When a later call ran it again, say\n  which call showed it. When an answer needed no new call, name the earlier\n  calls it came from.\n- The statements read the file as it was. A session still being recorded can\n  return more rows when one is run again.\n- If the user asks not to see the section, leave it out until they ask for it\n  again.\n\n## Reading the results\n\n- **Ticks.** A tick drew when XAML's frame counter moved on by the thread's\n  next tick, so whether the latest tick drew isn't known. That isn't proof\n  that a frame reached the screen: report tick durations and slow ticks, and\n  don't call frames dropped. Slow means more than 16.7 ms, a frame at 60 Hz;\n  the display's refresh rate isn't recorded.\n- **Tick times** are wall-clock time on the UI thread, not CPU time: a long\n  tick may have been waiting, and nothing in a session says on what. Events\n  on render and decode threads, and on threads that never tick, belong to no\n  tick.\n- **Types.** An element's type is the nearest built-in type, so an app's own\n  control shows as its base class, unless only a template, Loaded or render\n  event named it. A render event's name has no namespace, so one type can\n  have two rows, such as `TransitionRoot` and\n  `Microsoft.UI.Xaml.TransitionRoot` (`type` `TransitionRoot` lists both).\n  Objects no event gave a type are marked `typeUnknown`, which isn't a type\n  of its own. A freed object's address can be reused: `history` then lists\n  the objects that had it, and asks for one's `objectId`.\n- **Builds.** Ticks, regions and launch come from Microsoft-Windows-XAML in\n  every WinUI build. Current builds write the Microsoft-Windows-XAML-Profiler\n  events whenever a session enables the provider. Older builds wrote most of\n  them only with `XamlProfilerEnabled`, which WinUI's own build set for Debug\n  builds only, so a session of an older Release build has no visuals; its\n  elements come from the Microsoft-Windows-XAML events that name them. A\n  visual has a name, its owner element's label, only in older builds.\n- **Times** are in milliseconds from the origin `session.timeBase` gives: for\n  a live session, the start of the recording; for a trace, the process's\n  first event in it. It also says when the process was created, when known:\n  for a launch recorded from process start, or a trace with the kernel's\n  process events, as a WPR trace has. `launch` then gives\n  `msFromProcessStart`, unless the session starts at the connection, and\n  `measuredFrom` says what its frames count from.\n- **Length.** Each of the summary's `uiThreads` says when its first tick\n  started (`firstStartMs`) and its last finished tick ended (`lastEndMs`).\n  For a live session, `startedUtc` to `endedUtc` is how long the recording\n  ran. For a session read from a trace, they're when the trace was read, not\n  when it was recorded, which the file doesn't say.\n- **Limits.** One process per session. A session file is limited to 500 MB:\n  past it, the oldest events are deleted, and the summary says from which\n  event the file is complete.\n\n## What the tools can't answer\n\nThese aren't stored, so say so, and don't estimate them from other data:\n\n- the events' field values, and counts of raw events by provider;\n- GPU memory, CPU samples and call stacks, context switches and thread waits;\n- the XAML and composition trees;\n- the Launch tab's milestones from the marker configuration, such as an app's\n  own markers (a marker event fired on a UI thread shows only among its\n  tick's events, in the Other bucket; one fired on another thread doesn't);\n- other processes, such as the one that launched the app.\n\n## Getting a session\n\n- **Record it in the WinUI Profiler app.** The connection modes **Unpackaged\n  executable** and **Packaged application** launch the app after the session\n  starts; **Attach to process ID** starts at the connection, after most of\n  the launch. Recording live needs an elevated WinUI Profiler, or the local\n  Performance Log Users group. Sessions are saved in the sessions folder,\n  named `\u003Cdate>-\u003Ctime>-\u003Cprocess>-\u003Cpid>.sqlite`.\n- **Read a trace (.etl) into one,** which needs no elevation: in the app,\n  with the connection mode **Recorded trace (.etl)**, then **Open trace**, or\n  with the WinUI Profiler CLI's\n  `record \u003Ctrace.etl> --pid \u003Cpid> --out \u003Csession.sqlite>`.\n",{"name":5,"description":7,"user-invocable":24},true,"main","a6cd9a3ba680d382198dccb4487a6e08504a25da","tools\u002FWinUIProfiler\u002Fskills\u002Fanalyze-session",965,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fmicrosoft-ui-xaml","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-14 21:05:35",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":24},[36,39,42],{"tool":37,"command":38},"npx","npx skills add microsoft\u002Fmicrosoft-ui-xaml --skill analyze-session",{"tool":40,"command":41},"bunx","bunx skills add microsoft\u002Fmicrosoft-ui-xaml --skill analyze-session",{"tool":43,"command":44},"pnpm","pnpm dlx skills add microsoft\u002Fmicrosoft-ui-xaml --skill analyze-session","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fmicrosoft-ui-xaml\u002Fblob\u002Fmain\u002Ftools\u002FWinUIProfiler\u002Fskills\u002Fanalyze-session\u002FSKILL.md",[],[48,82,108,125,150],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":62,"publishedAt":81},"01M6WZSNKGE3MCZSF9DQXZYYS9","test-suite-setup","Complete end-to-end setup and execution of the WinUI3 test suite locally. Delegates building to the build skill, then handles test payload creation, machine setup, and running all tests.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fmicrosoft-ui-xaml\u002Fblob\u002Fmain\u002Fsrc\u002F.github\u002Fskills\u002Ftest-suite-setup\u002FSKILL.md",[54,59],{"categoryNo":55,"categoryName":56,"taxonomyType":57,"taxonomyTypeDesc":58},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":60,"categoryName":61,"taxonomyType":57,"taxonomyTypeDesc":58},"01JBSEEDCAT000000000000023","Skill与智能体开发",[63,64,65,66,67,68,69,70,71,72,73,74,75,76,77,78,79,80],"test suite setup","suite","test suite","setup","test","creation","running","delegates","machine","complete","end","tests","build","machine setup","payload","build skill","execution","winui3","2026-11-10 10:12:30",{"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":88,"publishedAt":81},"01M6WZSH72TCPB5XBFYGAV8PXP","bt-build","Fast incremental C++\u002FMSBuild builds using bt. Use when the user wants to compile, build, check what's dirty, or query build dependencies in a repo that has .vcxproj files. Prefer bt over invoking MSBuild directly for inner-loop source changes (.cpp, .h, .idl, .xaml, .appxmanifest).","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fmicrosoft-ui-xaml\u002Fblob\u002Fmain\u002Fsrc\u002F.github\u002Fskills\u002Fbt-build\u002FSKILL.md",[],[89,75,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107],"bt build","bt","query","when","inner","changes","for","inner-loop","c++","files","use","check","repo","loop","compile","xaml","cpp","msbuild","shell",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":115,"publishedAt":81},"01M6WZSBKKYWVMMR5W8ZEWF3CP","test-on-vm","EXPERIMENTAL. Run locally built WinUI interaction tests on a Hyper-V VM through PowerShell Direct. Use when asked to run WinUI tests on a local VM.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fmicrosoft-ui-xaml\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftest-on-vm\u002FSKILL.md",[114],{"categoryNo":55,"categoryName":56,"taxonomyType":57,"taxonomyTypeDesc":58},[116,117,67,74,118,92,119,120,99,121,122,123,124],"test on vm","vm","hyper","interaction","local","direct","powershell","winui","run",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":139,"publishedAt":81},"01M6WZS8FC8VE4M3V4W8N299Z8","code-review","Review changes in microsoft\u002Fmicrosoft-ui-xaml. Use when reviewing code or pull requests in this repository.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fmicrosoft-ui-xaml\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcode-review\u002FSKILL.md",[131,134],{"categoryNo":132,"categoryName":133,"taxonomyType":57,"taxonomyTypeDesc":58},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":135,"categoryName":136,"taxonomyType":137,"taxonomyTypeDesc":138},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[140,141,142,143,94,144,145,99,146,147,148,104,92,149,9],"code","review","code review","review changes","requests","reviewing code","repository","ui","pull","pull requests",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":158,"publishedAt":81},"01M6WZS15NPKE3ER8TS8ARD8A7","code-coverage-calculation","EXPERIMENTAL. Calculate code coverage of a WinUI control or component (for example \"calculate coverage of control TitleBar\") by running only that component's tests on a local Hyper-V VM against the local build. Supports controls in Microsoft.UI.Xaml.Controls.dll and Microsoft.UI.Xaml.Controls.Tabular.dll, and dxaml types in Microsoft.ui.xaml.dll. Reports per-file and per-function line coverage that matches the ADO Code Coverage tab. Use for \"calculate\u002Fmeasure\u002Fget coverage of \u003Ccontrol>\", \"how much do \u003Ccontrol>'s tests cover\", or \"coverage before\u002Fafter my tests\" when you have a local build and a VM.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fmicrosoft-ui-xaml\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcode-coverage-calculation\u002FSKILL.md",[156,157],{"categoryNo":60,"categoryName":61,"taxonomyType":57,"taxonomyTypeDesc":58},{"categoryNo":135,"categoryName":136,"taxonomyType":137,"taxonomyTypeDesc":138},[140,159,160,161,162,163,164,165,166,167,104,147,168,169,170,92,171,172,120,173],"code coverage calculation","code coverage","coverage","calculation","calculate","how","only","reports","component","line","types","you","my","cover","get"]