[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69BRNTFHGZ2CND9G3KWHPS7":3,"skill-same:01M69BRNTFHGZ2CND9G3KWHPS7":68},{"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":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":49,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M69BRNTFHGZ2CND9G3KWHPS7","performance-review",null,"Review Intelligent Terminal performance changes in local work, commit ranges, branches, or PRs. Use for renderer, text-buffer, VT, UI-thread, tab\u002Fpane, WTA, async, session, logging, allocation, event-amplification, benchmark, profiling, responsiveness, memory, and CI-cost changes.","microsoft\u002Fintelligent-terminal","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69BR4043X0X0KRBRZVGJP2V",2224,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fintelligent-terminal\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fperformance-review\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"performance review","review","performance","async","renderer","event","for","logging","ui","allocation","work","text","buffer","branches","local","ci","commit","benchmark","terminal","memory","2026-11-10 10:12:30",false,"---\nname: performance-review\ndescription: 'Review Intelligent Terminal performance changes in local work, commit ranges, branches, or PRs. Use for renderer, text-buffer, VT, UI-thread, tab\u002Fpane, WTA, async, session, logging, allocation, event-amplification, benchmark, profiling, responsiveness, memory, and CI-cost changes.'\n---\n\n# Performance Review\n\nInvestigate how a change affects typing, rendering, tab switching, WTA startup,\nsession refresh and repeated work. Establish the affected scenario and cost\nbefore recommending an optimization.\n\n## Review context\n\nEstablish the baseline and reviewed changes from the caller's local diff,\ncommit range, branch comparison or PR. Record the exact snapshot for mutable\nwork so later edits cannot be mistaken for reviewed evidence.\n\nIdentify changed files, affected components and callers. File and line counts\nhelp estimate effort; execution frequency, data growth and subsystem risk\ndetermine which paths merit deeper investigation. Caller-supplied scope and\nanalyzer output are discovery inputs, not proof of complete coverage.\nReview every relevant language independently of edit permissions. A Rust-only\nrepair allowlist does not exclude C++, XAML, rendering or UI-thread paths from\nsource review. State uninspected paths as coverage gaps.\n\nReview produces Markdown using the results template below. The caller owns\nexecution permissions, additional output formats, validation and delivery.\nReview-only is the default; authorized corrections follow the repair criteria.\n\n## Investigation\n\nInspect the complete patch and compare behavior with the baseline. Trace the\nchanged functions into repeated lifecycle and event paths: renderer and\nTerminalCore, text buffer, VT parser\u002Fadapter, UI thread, tab\u002Fpane ownership,\nWTA process pooling, tasks, locks, channels, session\u002Flog enumeration,\nallocations, copies and notification amplification.\n\nApply each rule when its trigger appears in the changes or affected callers.\nRecord the rule ID with its evidence.\n\n| Rule | Trigger | Investigation | Intentional cases |\n| --- | --- | --- | --- |\n| `PERF-REPEATED-WORK` | A loop, lookup, copy or enumeration changes on a repeated path. | Compare work as input grows; establish caller frequency and actual bounds. Inspect nested scans and collections used only for count or membership. | Fixed small bounds, one-time startup, required snapshots and amortized work. |\n| `PERF-UI-BLOCKING` | A UI callback or dispatcher path gains synchronous work. | Trace the executing thread, I\u002FO, waits and traversal through callees; identify the stalled interaction and its blocking cost. | Already-background work, bounded cheap callbacks and required thread affinity. |\n| `PERF-MVVM-AMPLIFICATION` | A property, binding, collection update or subscription changes. | Trace notifications to consumers; count expensive refreshes per logical change, including bulk updates and reentrancy. | Required individual notifications, cheap consumers and existing batching. |\n| `PERF-ASYNC-CONTENTION` | Lock scope, awaits, channels or synchronous work in a task changes. | Establish what survives suspension, who contends and how ordering affects progress; verify actual scopes. | Async-aware locks, released guards, intentional backpressure and non-suspending operations. |\n| `PERF-OWNER-LIFETIME` | Tabs, panes, tasks, subscriptions, helpers or pools have different lifetimes. | Trace repeated creation through teardown and cancellation; identify retained work or memory beyond its intended owner. | Resident pools, pre-warmed helpers, stash\u002Frestore and deliberately longer-lived bounded tasks. |\n\n## Analyzer and measurement evidence\n\nInspect each diagnostic in source before adopting it. Comparable results\nidentify revisions, tool versions, configuration, target and analyzed scope.\nSeparate new or worsened costs from unchanged baseline debt; moved lines alone\nare not new defects. Shared headers or callers can worsen behavior outside\nedited lines.\nCheck the actual implementation and version of library helpers before claiming\na cost difference; an owned return value can transfer an allocation rather than\nreuse it. Trace existing backoff, caps and cleanup before recommending them.\n\nAvailable repository entrypoints include the opt-in C++\n`PerformanceAnalysis=Extended` profile, `cargo wta-perf` and\n`cargo wta-perf-extended`. Use their definitions in the build configuration\nand Cargo aliases as the authority for checks and commands. Ordinary Cargo\nbuilds do not run Clippy.\n\nC++ project selection is provisional until evaluated MSBuild `ClCompile`\nmembership establishes translation-unit coverage. Successful prerequisite\nbuilds are not additional analyzer coverage. Unmapped sources, shared callers,\nheaders and unsupported languages remain explicit coverage gaps.\n\nInterpret warnings in context. `await_holding_lock` can warn after an explicit\ndrop; collections may preserve iterator or clone side effects; boxing a large\nfuture trades stack size for allocation. Group membership and machine-fix\navailability do not establish impact or behavioral safety.\n\nInspect existing evidence where relevant: `src\u002FConsolePerf.wprp`,\n`src\u002Ftools\u002FConsoleBench`, `test\u002Fe2e\u002FMeasure-PaneContext.ps1`,\n`build\u002Fscripts\u002FMeasure-AgentHookOverhead.ps1`, focused tests and duration\ntelemetry.\n\n| Evidence | What it establishes |\n| --- | --- |\n| Source \u002F complexity \u002F blocking \u002F lifetime proof | A concrete causal cost under stated execution and input bounds. |\n| Microbenchmark | Cost of the measured operation, not end-to-end improvement. |\n| End-to-end measurement | Impact on the measured user scenario and environment. |\n| Profile | Where measured work or resource use accumulates. |\n| Native test | Behavior covered by that test on the exact validated source. |\n| Missing, partial or failed analysis | A coverage gap or blocker, not a clean result. |\n\nSeparate application performance, responsiveness, memory growth and CI\nruntime\u002Fcost. Record the native OS, architecture, tooling and measurement\nconditions. Noisy measurements need at least three samples and their spread;\ncross-platform timings remain evidence for the platform actually measured.\n\n## Triage and repair\n\nClassify each finding as HIGH, MEDIUM or LOW before choosing its disposition.\nRank severity by demonstrated scenario impact, frequency or growth, not by\nhow easy a fix is. Do not promote a finding to HIGH to make it autofix-eligible.\nCollapse duplicate warnings for the same underlying defect.\n\n| Result | Disposition |\n| --- | --- |\n| HIGH, high confidence, measured regression or proven complexity\u002Fblocking\u002Flifetime defect on a relevant path | Propose the smallest behavior-preserving correction. |\n| Important defect with redesign, ordering\u002Flifetime uncertainty or unsupported validation | Manual handoff with evidence and missing proof. |\n| Plausible cost with uncertain impact or frequency | MEDIUM\u002FLOW advice with uncertainty and tradeoffs. |\n| Unrelated baseline debt, negligible bounded cost, intentional behavior or false positive | Explain the exclusion in check evidence. |\n\nEvery finding needs an introduced, unintended cost and its affected scenario.\nDo not fill finding rows with observations that conclude the work is negligible,\nunchanged or intentional; record those exclusions in checks instead. A source\nproof of blocking, repeated work or unbounded retention does not require a\nbenchmark, but an unexplored alternative implementation is not such proof.\n\nProof that work exists is not proof that it merits HIGH repair. Tie its growth,\nblocking or retention to the affected scenario's actual bounds\u002Ffrequency or\ndemonstrated impact. An unnecessary allocation or copy with no such context\nremains MEDIUM\u002FLOW advice, even if its local replacement is obvious. A separate\nHIGH defect in the same file does not authorize editing an advice-only finding.\n\nOnly HIGH findings are eligible for authorized autofix, and only when they are\nhigh-confidence, small and localized, behavior-preserving, and supported by\nrepository-specific evidence. Build and test are not prerequisites for committing\nan authorized proposal: the original reviewer owns validation and may revert\nthe proposed fix commit. Broad threading, caching, architecture,\ndependency or policy changes require separate design work.\nWhen committing is authorized, make one separate minimal commit per HIGH\nfinding and put its commit link in that finding's table row. Do not combine\nfindings or add unrelated cleanup.\n\nPreserve existing tests and intended semantics. Analyzer replacements need the\nsame proof as hand-written changes: a reference parameter can affect ABI or\ncoroutine lifetime, and reserved capacity can increase retained memory.\nInsufficient evidence or validation results in an unresolved handoff rather\nthan a broader edit. Report source changes and validation separately so a\nproposal cannot be mistaken for a verified improvement.\nWhen proposals are committed, include one notice below the findings table:\n\"Proposed fixes committed without build\u002Ftest. The original reviewer owns\nvalidation and may revert the fix commit.\" Do not repeat it for each finding.\n\n## Results template\n\nKeep the opening summary as prose. Use tables for findings and checks, ordered\nHIGH, MEDIUM, LOW; within a severity, show validated corrections, proposals,\nmanual handoffs and advice in that order. Include exact commands\u002Fresults and\nmissing evidence. With no actionable findings, use that plain statement\ninstead of placeholder rows.\n\n```markdown\n## Performance review\n\n\u003COne sentence describing the outcome and most important impact.>\n\n### Findings\n\n| Severity | Rule \u002F location | Finding and impact | Disposition | Commit | Validation |\n| --- | --- | --- | --- | --- | --- |\n| HIGH \u002F MEDIUM \u002F LOW | \u003Crule ID; path:line> | \u003Cscenario and evidenced cost> | Proposed fix commit \u002F Manual handoff \u002F Advice only | \u003Cactual commit link, or None> | \u003Cperformed check or Not built\u002Ftested> |\n\n\u003CFor committed proposals, put one shared build\u002Ftest ownership and rollback\nnotice here; omit it when nothing was committed.>\n\n### Checks performed\n\n| Check | Scope \u002F command | Result | Missing evidence |\n| --- | --- | --- | --- |\n| \u003Canalyzer or architecture rule> | \u003Cactual scope and command\u002Finspection> | Completed \u002F Failed \u002F Not run | \u003Cgap, or None> |\n```\n\n`Completed` records that a check ran; it does not imply no findings or measured\ngain. A validated correction names its exact source and completed validation.\nUnavailable or failed checks remain visible even when source review is complete.\n","# Performance Review\n\nInvestigate how a change affects typing, rendering, tab switching, WTA startup,\nsession refresh and repeated work. Establish the affected scenario and cost\nbefore recommending an optimization.\n\n## Review context\n\nEstablish the baseline and reviewed changes from the caller's local diff,\ncommit range, branch comparison or PR. Record the exact snapshot for mutable\nwork so later edits cannot be mistaken for reviewed evidence.\n\nIdentify changed files, affected components and callers. File and line counts\nhelp estimate effort; execution frequency, data growth and subsystem risk\ndetermine which paths merit deeper investigation. Caller-supplied scope and\nanalyzer output are discovery inputs, not proof of complete coverage.\nReview every relevant language independently of edit permissions. A Rust-only\nrepair allowlist does not exclude C++, XAML, rendering or UI-thread paths from\nsource review. State uninspected paths as coverage gaps.\n\nReview produces Markdown using the results template below. The caller owns\nexecution permissions, additional output formats, validation and delivery.\nReview-only is the default; authorized corrections follow the repair criteria.\n\n## Investigation\n\nInspect the complete patch and compare behavior with the baseline. Trace the\nchanged functions into repeated lifecycle and event paths: renderer and\nTerminalCore, text buffer, VT parser\u002Fadapter, UI thread, tab\u002Fpane ownership,\nWTA process pooling, tasks, locks, channels, session\u002Flog enumeration,\nallocations, copies and notification amplification.\n\nApply each rule when its trigger appears in the changes or affected callers.\nRecord the rule ID with its evidence.\n\n| Rule | Trigger | Investigation | Intentional cases |\n| --- | --- | --- | --- |\n| `PERF-REPEATED-WORK` | A loop, lookup, copy or enumeration changes on a repeated path. | Compare work as input grows; establish caller frequency and actual bounds. Inspect nested scans and collections used only for count or membership. | Fixed small bounds, one-time startup, required snapshots and amortized work. |\n| `PERF-UI-BLOCKING` | A UI callback or dispatcher path gains synchronous work. | Trace the executing thread, I\u002FO, waits and traversal through callees; identify the stalled interaction and its blocking cost. | Already-background work, bounded cheap callbacks and required thread affinity. |\n| `PERF-MVVM-AMPLIFICATION` | A property, binding, collection update or subscription changes. | Trace notifications to consumers; count expensive refreshes per logical change, including bulk updates and reentrancy. | Required individual notifications, cheap consumers and existing batching. |\n| `PERF-ASYNC-CONTENTION` | Lock scope, awaits, channels or synchronous work in a task changes. | Establish what survives suspension, who contends and how ordering affects progress; verify actual scopes. | Async-aware locks, released guards, intentional backpressure and non-suspending operations. |\n| `PERF-OWNER-LIFETIME` | Tabs, panes, tasks, subscriptions, helpers or pools have different lifetimes. | Trace repeated creation through teardown and cancellation; identify retained work or memory beyond its intended owner. | Resident pools, pre-warmed helpers, stash\u002Frestore and deliberately longer-lived bounded tasks. |\n\n## Analyzer and measurement evidence\n\nInspect each diagnostic in source before adopting it. Comparable results\nidentify revisions, tool versions, configuration, target and analyzed scope.\nSeparate new or worsened costs from unchanged baseline debt; moved lines alone\nare not new defects. Shared headers or callers can worsen behavior outside\nedited lines.\nCheck the actual implementation and version of library helpers before claiming\na cost difference; an owned return value can transfer an allocation rather than\nreuse it. Trace existing backoff, caps and cleanup before recommending them.\n\nAvailable repository entrypoints include the opt-in C++\n`PerformanceAnalysis=Extended` profile, `cargo wta-perf` and\n`cargo wta-perf-extended`. Use their definitions in the build configuration\nand Cargo aliases as the authority for checks and commands. Ordinary Cargo\nbuilds do not run Clippy.\n\nC++ project selection is provisional until evaluated MSBuild `ClCompile`\nmembership establishes translation-unit coverage. Successful prerequisite\nbuilds are not additional analyzer coverage. Unmapped sources, shared callers,\nheaders and unsupported languages remain explicit coverage gaps.\n\nInterpret warnings in context. `await_holding_lock` can warn after an explicit\ndrop; collections may preserve iterator or clone side effects; boxing a large\nfuture trades stack size for allocation. Group membership and machine-fix\navailability do not establish impact or behavioral safety.\n\nInspect existing evidence where relevant: `src\u002FConsolePerf.wprp`,\n`src\u002Ftools\u002FConsoleBench`, `test\u002Fe2e\u002FMeasure-PaneContext.ps1`,\n`build\u002Fscripts\u002FMeasure-AgentHookOverhead.ps1`, focused tests and duration\ntelemetry.\n\n| Evidence | What it establishes |\n| --- | --- |\n| Source \u002F complexity \u002F blocking \u002F lifetime proof | A concrete causal cost under stated execution and input bounds. |\n| Microbenchmark | Cost of the measured operation, not end-to-end improvement. |\n| End-to-end measurement | Impact on the measured user scenario and environment. |\n| Profile | Where measured work or resource use accumulates. |\n| Native test | Behavior covered by that test on the exact validated source. |\n| Missing, partial or failed analysis | A coverage gap or blocker, not a clean result. |\n\nSeparate application performance, responsiveness, memory growth and CI\nruntime\u002Fcost. Record the native OS, architecture, tooling and measurement\nconditions. Noisy measurements need at least three samples and their spread;\ncross-platform timings remain evidence for the platform actually measured.\n\n## Triage and repair\n\nClassify each finding as HIGH, MEDIUM or LOW before choosing its disposition.\nRank severity by demonstrated scenario impact, frequency or growth, not by\nhow easy a fix is. Do not promote a finding to HIGH to make it autofix-eligible.\nCollapse duplicate warnings for the same underlying defect.\n\n| Result | Disposition |\n| --- | --- |\n| HIGH, high confidence, measured regression or proven complexity\u002Fblocking\u002Flifetime defect on a relevant path | Propose the smallest behavior-preserving correction. |\n| Important defect with redesign, ordering\u002Flifetime uncertainty or unsupported validation | Manual handoff with evidence and missing proof. |\n| Plausible cost with uncertain impact or frequency | MEDIUM\u002FLOW advice with uncertainty and tradeoffs. |\n| Unrelated baseline debt, negligible bounded cost, intentional behavior or false positive | Explain the exclusion in check evidence. |\n\nEvery finding needs an introduced, unintended cost and its affected scenario.\nDo not fill finding rows with observations that conclude the work is negligible,\nunchanged or intentional; record those exclusions in checks instead. A source\nproof of blocking, repeated work or unbounded retention does not require a\nbenchmark, but an unexplored alternative implementation is not such proof.\n\nProof that work exists is not proof that it merits HIGH repair. Tie its growth,\nblocking or retention to the affected scenario's actual bounds\u002Ffrequency or\ndemonstrated impact. An unnecessary allocation or copy with no such context\nremains MEDIUM\u002FLOW advice, even if its local replacement is obvious. A separate\nHIGH defect in the same file does not authorize editing an advice-only finding.\n\nOnly HIGH findings are eligible for authorized autofix, and only when they are\nhigh-confidence, small and localized, behavior-preserving, and supported by\nrepository-specific evidence. Build and test are not prerequisites for committing\nan authorized proposal: the original reviewer owns validation and may revert\nthe proposed fix commit. Broad threading, caching, architecture,\ndependency or policy changes require separate design work.\nWhen committing is authorized, make one separate minimal commit per HIGH\nfinding and put its commit link in that finding's table row. Do not combine\nfindings or add unrelated cleanup.\n\nPreserve existing tests and intended semantics. Analyzer replacements need the\nsame proof as hand-written changes: a reference parameter can affect ABI or\ncoroutine lifetime, and reserved capacity can increase retained memory.\nInsufficient evidence or validation results in an unresolved handoff rather\nthan a broader edit. Report source changes and validation separately so a\nproposal cannot be mistaken for a verified improvement.\nWhen proposals are committed, include one notice below the findings table:\n\"Proposed fixes committed without build\u002Ftest. The original reviewer owns\nvalidation and may revert the fix commit.\" Do not repeat it for each finding.\n\n## Results template\n\nKeep the opening summary as prose. Use tables for findings and checks, ordered\nHIGH, MEDIUM, LOW; within a severity, show validated corrections, proposals,\nmanual handoffs and advice in that order. Include exact commands\u002Fresults and\nmissing evidence. With no actionable findings, use that plain statement\ninstead of placeholder rows.\n\n```markdown\n## Performance review\n\n\u003COne sentence describing the outcome and most important impact.>\n\n### Findings\n\n| Severity | Rule \u002F location | Finding and impact | Disposition | Commit | Validation |\n| --- | --- | --- | --- | --- | --- |\n| HIGH \u002F MEDIUM \u002F LOW | \u003Crule ID; path:line> | \u003Cscenario and evidenced cost> | Proposed fix commit \u002F Manual handoff \u002F Advice only | \u003Cactual commit link, or None> | \u003Cperformed check or Not built\u002Ftested> |\n\n\u003CFor committed proposals, put one shared build\u002Ftest ownership and rollback\nnotice here; omit it when nothing was committed.>\n\n### Checks performed\n\n| Check | Scope \u002F command | Result | Missing evidence |\n| --- | --- | --- | --- |\n| \u003Canalyzer or architecture rule> | \u003Cactual scope and command\u002Finspection> | Completed \u002F Failed \u002F Not run | \u003Cgap, or None> |\n```\n\n`Completed` records that a check ran; it does not imply no findings or measured\ngain. A validated correction names its exact source and completed validation.\nUnavailable or failed checks remain visible even when source review is complete.\n",{"name":5,"description":7},"main","983680af0e7cc89e8ca1a75b214952742ce92588",".github\u002Fskills\u002Fperformance-review",179,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fintelligent-terminal","https:\u002F\u002Fdevblogs.microsoft.com\u002Fcommandline\u002Fannouncing-intelligent-terminal-version-0-1\u002F","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-14 22:29:46",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add microsoft\u002Fintelligent-terminal --skill performance-review",{"tool":60,"command":61},"bunx","bunx skills add microsoft\u002Fintelligent-terminal --skill performance-review",{"tool":63,"command":64},"pnpm","pnpm dlx skills add microsoft\u002Fintelligent-terminal --skill performance-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fintelligent-terminal\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fperformance-review\u002FSKILL.md",true,[],[69,106,134,156,189,213],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":73,"licenseFileUrl":74,"sourceHtmlUrl":75,"categories":76,"keywords":85,"publishedAt":39},"01M69BS17H119AHC0VA6CGCG80","store-listing-localizer","Automate Microsoft Store (Partner Center) listing localization for Intelligent Terminal (Store ID 9NMQC2SSJX24). Use when asked to export\u002Fimport Store listings, localize release notes \u002F descriptions \u002F captions \u002F features into 80+ languages, update listingData CSV, or push Store listing translations without manually clicking through Partner Center. Drives Partner Center export\u002Fimport via the Playwright MCP and merges per-locale translations into the listingData CSV.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fintelligent-terminal\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fstore-listing-localizer\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fintelligent-terminal\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fstore-listing-localizer\u002FSKILL.md",[77,82],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000004","电子表格","SCENARIO","使用场景",{"categoryNo":83,"categoryName":84,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000023","Skill与智能体开发",[86,87,88,89,90,37,9,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105],"store listing localizer","listing","store","notes","playwright","update","release","release notes","MCP","Captions","localize","when","features","playwright mcp","listings","export","localization","locale","automate","import",{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":113,"publishedAt":39},"01M69BS54V1THPSKYAA7VFSBAY","upstream-sync","Periodically sync new commits from microsoft\u002Fterminal into this manually-forked intelligent-terminal repo by cherry-picking commit-by-commit onto a dated sync branch, auto-skipping revert pairs and empty commits, auto-resolving known take-upstream files, and stopping cleanly on genuine conflicts. The agent (you, reading this file) is the orchestrator — the PowerShell scripts are atomic operations you invoke one at a time. Use when the user asks to \"sync upstream\", \"pull from microsoft\u002Fterminal\", \"run upstream sync\", \"catch up to upstream\", or wires this into a scheduler (weekly\u002Fdaily). Designed to be safe under repeated unattended runs.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fintelligent-terminal\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fupstream-sync\u002FSKILL.md",[112],{"categoryNo":83,"categoryName":84,"taxonomyType":80,"taxonomyTypeDesc":81},[114,115,116,117,37,9,118,119,35,120,121,122,123,124,125,126,127,128,97,129,130,131,132,133],"upstream sync","sync","upstream","run","sync upstream","safe","weekly","branch","powershell","time","up","new","files","auto","invoke","you","one at a time","conflicts","catch","orchestrator",{"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":140,"publishedAt":39},"01M69BRY6Z1T250VCQDTQ8ZFMQ","release-notes","Generate user-facing release notes for Intelligent Terminal. Use when asked to write release notes, changelog, what-is-new summary, or prepare a release. Compares git commits between releases, looks up PR-linked issues and community contributors, then outputs formatted notes with \"Verbed + Impact + Scenario\" style bullets, issue references, and contributor thanks.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fintelligent-terminal\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Frelease-notes\u002FSKILL.md",[],[89,92,93,141,142,37,143,144,145,124,146,125,147,148,97,149,150,151,152,153,154,155],"pr","generate","git","prepare","community","issues","impact","contributor","references","changelog","releases","write","scenario","issue","contributors",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":169,"publishedAt":39},"01M69BRV95KH26NCNHGKX4BGTJ","pr-integration-test","Design, implement, and validate Intelligent Terminal integration tests for a target pull request or regression. Use when asked to add PR integration tests, convert a bug fix into E2E coverage, prove existing behavior still works, map tests to the release checklist, or verify E2E reports mark checklist cases complete.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fintelligent-terminal\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fpr-integration-test\u002FSKILL.md",[162,165,168],{"categoryNo":163,"categoryName":164,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":166,"categoryName":167,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":83,"categoryName":84,"taxonomyType":80,"taxonomyTypeDesc":81},[170,141,171,172,173,174,175,37,92,176,177,178,179,180,181,182,183,97,184,185,186,187,188],"test","pr integration test","integration test","integration","integration tests","pull request","validate","design","implement","coverage","regression","release checklist","fix","map","reports","request","bug","add","pull",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":196,"publishedAt":39},"01M69BRR7XQK0K0S4Z2Y81GX20","pr-accessibility","Review and repair native Windows WinUI, XAML, C++, UI Automation, keyboard, focus, screen-reader, high-contrast, scaling, settings, tab, pane, and agent-card accessibility changes. Use for accessibility analysis of Intelligent Terminal UI pull requests and focused local accessibility checks.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fintelligent-terminal\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fpr-accessibility\u002FSKILL.md",[195],{"categoryNo":83,"categoryName":84,"taxonomyType":80,"taxonomyTypeDesc":81},[141,197,198,199,200,201,202,37,203,20,204,205,33,206,207,208,209,210,211,27,188,212],"accessibility","pr accessibility","xaml","windows","pull requests","winui","automation","scaling","card","analysis","keyboard","focus","native","screen","contrast","repair",{"skillNo":214,"name":215,"nameZh":6,"description":216,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":217,"categories":218,"keywords":220,"publishedAt":39},"01M69BRJ5CFMPN7NBQR9FVA17E","ghaw-pr-security","Review Intelligent Terminal pull requests for C++\u002FWinRT, COM, WTA, ACP, session MCP, hooks, terminal mutation, path, diagnostic, packaging, and GitHub Actions security regressions. Use for evidence-based immutable-diff review and structured HIGH\u002Fmedium\u002Flow findings.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fintelligent-terminal\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fghaw-pr-security\u002FSKILL.md",[219],{"categoryNo":83,"categoryName":84,"taxonomyType":80,"taxonomyTypeDesc":81},[141,221,222,201,223,37,224,94,20,225,226,227,228,229,230,188,231,232,233,25,234,235],"security","ghaw pr security","github","acp","packaging","actions","hooks","github actions","mutation","path","evidence","c++","diff","session","diff review"]