[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FKXA54BS439STG92DZAGFS":3,"skill-same:01M6FKXA54BS439STG92DZAGFS":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},"01M6FKXA54BS439STG92DZAGFS","create-pr",null,"Create a pull request using the repository PR template. Use when asked to: create PR, open PR, push and create PR, submit PR, open pull request, send changes for review.","microsoft\u002Faspire","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M6FKTZ7ND1S9JN6JTVK7A7MD",6426,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcreate-pr\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"create pr","pr","create","when","review","send","request","changes","for","submit","use","submit pr","template","open","open pull request","repository","open pr","push","pull","pull request","2026-11-10 10:12:30",false,"---\nname: create-pr\ndescription: 'Create a pull request using the repository PR template. Use when asked to: create PR, open PR, push and create PR, submit PR, open pull request, send changes for review.'\n---\n\nYou are a specialized pull request creation agent for this repository.\n\nYour goal is to **create a PR** and always **use the repository PR template** at `.github\u002Fpull_request_template.md`.\n\n## Example requests\n\n- \"Create a PR for this change\"\n- \"Push and open a pull request\"\n- \"Submit a PR with these fixes\"\n- \"Open a PR against the release branch\"\n\n## Prerequisites\n\nBefore starting, verify:\n- `gh` CLI is available: run `gh --version`. If missing, tell the user to install it from https:\u002F\u002Fcli.github.com\u002F.\n- Authentication is configured: run `gh auth status`. If not authenticated, tell the user to run `gh auth login`.\n\n## Procedure\n\n### 1. Prepare the branch\n\n- Confirm the current branch name with `git branch --show-current`.\n- Ensure changes are committed (`git status` should show a clean working tree or only untracked files).\n- Push the branch with `git push -u origin \u003Cbranch-name>`. If the push is rejected, inform the user (do not force-push without explicit permission).\n\n### 2. Determine PR metadata\n\n- **Head branch**: current branch unless the user specifies otherwise.\n- **Base branch**: user-specified base when provided; otherwise infer from context (or use the repository default branch).\n- **Title**: concise summary of the change.\n- **Labels**: add labels only when they are clearly applicable. Use the `breaking-change` label when the PR breaks public APIs or fundamentally changes the behavior of an existing scenario. Do not use it for every behavior change, additive feature, routine bug fix, or implementation-only change. Examples from existing `breaking-change` issues include API shape\u002Fsemantics changes, obsoleting a public API, changing endpoint allocation\u002Fwait behavior, changing Docker Compose publish behavior, and disabling local auth for Azure resources.\n\n### 3. Detect non-trivial UI changes\n\nBefore building the PR body, check whether the diff includes **non-trivial UI changes** to any of these areas:\n\n- **Dashboard** (`src\u002FAspire.Dashboard\u002F`): changes to `.razor`, `.razor.cs`, `.css`, `.js`, or UI assets under `src\u002FAspire.Dashboard\u002Fwwwroot\u002F` (e.g., `img\u002F**`, `favicon.ico`) that alter layout, add\u002Fremove components, change interactive behavior, or modify visual appearance beyond minor text or spacing tweaks.\n- **CLI** (`src\u002FAspire.Cli\u002F`): changes to command output formatting, interactive prompts, table\u002Flist rendering, spinners, progress indicators, or colored output beyond simple message text changes.\n- **VS Code Extension** (`extension\u002F`): changes to webview panels, tree views, status bar items, quick pick UIs, editor decorations, contributed view configuration (`package.json`), or UI assets (`resources\u002F**`) beyond minor label text changes.\n\nA change is **non-trivial** if it does more than:\n- Fix a typo or update a string literal without altering layout\n- Adjust a single CSS property (e.g., margin, padding) without changing visual structure\n- Change a tooltip or aria-label\n\nIf non-trivial UI changes are detected, add a prominent `### Screenshots \u002F Recordings` subsection in the PR body (under `## Description`) with the following content:\n\n```markdown\n### Screenshots \u002F Recordings\n\n> **This PR includes UI changes.** Please add screenshots or screen recordings so reviewers can evaluate the visual changes without running locally.\n>\n> - For before\u002Fafter comparisons, place them side-by-side or label them clearly.\n> - For interactive changes (animations, transitions, new flows), prefer a short screen recording (GIF or video).\n> - If you cannot capture visuals now, note what scenario to test and mark this section as TODO.\n\n\u003C!-- Add screenshots\u002Frecordings here -->\n```\n\n### 4. Upload visual artifacts\n\nFor non-trivial UI changes, upload screenshots or recordings as GitHub user attachments. Do not commit them to the source branch unless explicitly requested.\n\nTo make a recording, use the `create-video` skill: it can record the change from this branch's own build, and its `web` rendition stays under GitHub's 10 MB attachment limit. A short pull request demo needs no narration or slides.\n\nBefore uploading, inspect every artifact for secrets, credentials, tokens, customer or confidential data, private URLs, and unintended personal information. Redact or regenerate any artifact that contains sensitive data, and do not upload it until the inspection passes. Treat uploads as permanent public data because this public repository exposes attachments to everyone and the attachment API has no deletion endpoint.\n\nCheck attachment support for the command that will write the PR: `gh pr create --help` for a new PR or `gh pr edit --help` for an existing PR. Use `--attach` only when that command advertises it. Prepare local Markdown references for step 5 to insert at the intended location in `pr-body.md`. Use a table for before\u002Fafter images when appropriate:\n\n```markdown\n| Before | After |\n| --- | --- |\n| ![Before](.\u002Fbefore.png) | ![After](.\u002Fafter.png) |\n```\n\nPlace an image-style reference to a video on its own line in its own paragraph so GitHub CLI rewrites it to a bare asset URL that renders as a player:\n\n```markdown\n![Screen recording](.\u002Fdemo.mp4)\n```\n\nPrepare one flag per referenced file and append the flags to the final `gh pr create` command in step 6 or `gh pr edit` command in step 7. GitHub CLI rewrites the local references to uploaded URLs; without references, it appends the attachments to the end of the body. For images, text after `#` is the alt text when the body does not already provide it. Videos do not support alt text and must omit the `#` suffix:\n\n```shell\n--attach '.\u002Fbefore.png#Before' --attach '.\u002Fafter.png#After' --attach '.\u002Fdemo.mp4'\n```\n\nIf the relevant command does not advertise `--attach`, do not upload the artifacts or call GitHub's undocumented attachment endpoint. Tell the user that their installed GitHub CLI version does not support attachment uploads for that command and ask them to upgrade it. Include the detected version from `gh --version` and link to the official upgrade instructions at https:\u002F\u002Fgithub.com\u002Fcli\u002Fcli#installation.\n\nAfter the upgrade, run `gh --version` and check the relevant command help again. Retry the upload only when `--attach` is advertised. If the user does not upgrade, continue without uploading and retain the TODO in the Screenshots \u002F Recordings section so the missing visual evidence is explicit.\n\n### 5. Build PR body from template\n\n- Read `.github\u002Fpull_request_template.md`.\n- Use the template structure as the PR body.\n- If step 4 prepared visual artifacts and `gh --attach` is available, replace the `\u003C!-- Add screenshots\u002Frecordings here -->` placeholder with the prepared local Markdown references before running the create or edit command. Do not leave the placeholder in the final body after a successful upload.\n- Fill known details in `## Description` with reviewer- and user-facing context:\n  - Lead with **why** the change matters: the user problem, scenario, or workflow it improves.\n  - Summarize the user-visible behavior before implementation details: what users can now do, see, configure, or call.\n  - Include implementation details only after the behavior summary, and keep them concise.\n  - Evaluate whether the change makes security assumptions or guarantees, and include details only when security review may be needed.\n  - Include relevant validation: tests, manual verification, screenshots, recordings, generated help, or sample output.\n- For infra-only or internal-only changes, such as CI, build infrastructure, repository automation, tests, docs-only maintenance, or skill\u002Fworkflow guidance, do not add user-facing usage artifacts, `### Breaking changes`, or `### Security considerations` unless the change also affects user-visible behavior, breaks a public API or established scenario, or requires security review.\n- When the change affects user-facing behavior, add a subsection such as `### User-facing usage` or `### Examples` under `## Description` with concrete usage examples. Prefer examples from the diff, tests, docs, generated output, or commands you actually ran. Do not invent usage; if the usage cannot be determined confidently, ask the user or state that an example is not available.\n- Include the most relevant user-facing artifacts by change type:\n  - **Dashboard\u002FUI changes**: include dashboard screenshots, preferably before\u002Fafter when visual behavior changes.\n  - **CLI changes**: include command-specific `--help` output, example invocations with named arguments\u002Foptions, and an asciinema recording link when practical.\n  - **Public API changes**: include a consumer-focused usage example for the new API.\n  - **Integration changes**: include both C# and TypeScript usage examples when applicable.\n  - **Configuration, template, or docs changes**: include before\u002Fafter snippets, generated output, or the command a user runs.\n- Include a `### Security considerations` subsection only when the security checklist would be marked as needing security review because the change makes security assumptions or guarantees. Call out any relevant implications, such as:\n  - New network listeners, outbound connections, exposed ports, proxying, or service discovery behavior.\n  - Files written to global, shared, profile, cache, or temporary directories.\n  - Script execution, generated commands, shell escaping, or script\u002Fcontent injection risks.\n  - Path construction, archive extraction, file uploads\u002Fdownloads, or path traversal risks.\n  - Untrusted user input, data deserialization, authentication\u002Fauthorization changes, secrets, credentials, certificates, tokens, or environment variables.\n  - Container execution, process spawning, permissions, or elevated privileges.\n- Do not add a `### Security considerations` subsection for changes that do not need security review; instead, keep the checklist answer aligned with that assessment.\n- If the PR uses the `breaking-change` label, include a short `### Breaking changes` subsection that explains who is affected, what existing API or scenario changes, and how users should update.\n- Example PR body snippet shapes. Treat these as formats only; replace every placeholder with exact screenshots, commands, APIs, generated output, and security facts from the PR:\n  - **Dashboard\u002FUI changes**:\n    ```markdown\n    ### User-facing usage\n    The dashboard now shows \u003Cnew state or action> on the \u003Cpage\u002Fpanel>, so users can \u003Coutcome> without \u003Cold workaround>.\n    Screenshot: ![Dashboard showing \u003Cfeature>](\u003Cuploaded screenshot URL>)\n    ```\n  - **CLI changes**:\n    ````markdown\n    ### User-facing usage\n    Users can run the command with named options:\n    ```bash\n    aspire \u003Ccommand> \u003Cresource> --name \u003Ccommand-name> --timeout 30s\n    ```\n    Command help:\n    ```text\n    Usage:\n      aspire \u003Ccommand> \u003Cresource> [options]\n    Options:\n      --name \u003Cname>        \u003Cdescribe option>\n      --timeout \u003Cvalue>    \u003Cdescribe option>\n    ```\n    Recording: \u003Casciinema URL, if available>\n    ````\n  - **Public API changes**:\n    ````markdown\n    ### User-facing usage\n    Consumers can configure \u003Cscenario> with the new API:\n    ```csharp\n    var resource = builder.Add\u003CIntegration>(\"resource\")\n                          .With\u003CNewCapability>(\"\u003Cvalue>\");\n    ```\n    ````\n  - **Integration changes**:\n    ````markdown\n    ### User-facing usage\n    C# AppHost:\n    ```csharp\n    var resource = builder.Add\u003CIntegration>(\"resource\")\n                          .With\u003CNewCapability>(\"\u003Cvalue>\");\n    ```\n    TypeScript AppHost:\n    ```typescript\n    const resource = builder.add\u003CIntegration>(\"resource\")\n      .with\u003CNewCapability>(\"\u003Cvalue>\");\n    ```\n    ````\n  - **Configuration, template, or docs changes**:\n    ````markdown\n    ### User-facing usage\n    Users enable the behavior with:\n    ```json\n    {\n      \"\u003CsettingName>\": \"\u003Cvalue>\"\n    }\n    ```\n    Generated output now includes `\u003Cobservable output>`.\n    ````\n  - **Security-review changes**:\n    ```markdown\n    ### Security considerations\n    This change \u003Copens a listener\u002Fwrites to a shared directory\u002Fexecutes generated commands\u002Faccepts untrusted input>. Security review is needed to confirm \u003Cspecific concern>, such as host binding, path normalization, command escaping, or secret handling.\n    ```\n  - **Breaking changes**:\n    ```markdown\n    ### Breaking changes\n    This changes \u003Cexisting API or scenario>. Users who currently \u003Cold usage> should update to \u003Cnew usage or migration guidance>.\n    ```\n- Fill checklist choices by selecting known answers and leaving only unknown choices unchecked.\n- Keep `Fixes # (issue)` unless a concrete issue number is provided.\n- Write the body to a temporary file named `pr-body.md` in the repo root.\n\n### 6. Create the PR\n\nSet `GH_PAGER` to `cat` to prevent interactive paging, then create the PR. The syntax differs by shell:\n\nIf the PR needs labels, add the matching label flags to the create command. For breaking public API changes or fundamental existing-scenario behavior changes, include `--label breaking-change`.\n\n**bash\u002FLinux\u002FmacOS:**\n```bash\nGH_PAGER=cat gh pr create \\\n  --base \u003Cbase-branch> \\\n  --head \u003Chead-branch> \\\n  --title \"\u003Cpr-title>\" \\\n  --body-file pr-body.md \\\n  --attach '.\u002Fbefore.png#Before' \\\n  --attach '.\u002Fafter.png#After'\n```\n\n**PowerShell\u002FWindows:**\n```powershell\n$env:GH_PAGER = \"cat\"\ngh pr create `\n  --base \u003Cbase-branch> `\n  --head \u003Chead-branch> `\n  --title \"\u003Cpr-title>\" `\n  --body-file pr-body.md `\n  --attach '.\u002Fbefore.png#Before' `\n  --attach '.\u002Fafter.png#After'\n```\n\nOmit the `--attach` lines when step 4 did not prepare visual artifacts. Attach videos without a `#` suffix.\n\n> **Why `GH_PAGER=cat`?** The `gh` CLI pipes long output through a pager (like `less`) by default, which blocks in non-interactive terminals. Setting it to `cat` disables paging so output prints directly.\n\n> **Shell differences:** `VAR=val command` is bash syntax for setting an env var for a single command. PowerShell requires a separate `$env:VAR = \"val\"` statement (persists for the session, which is harmless here).\n\n### 7. Handle existing PRs\n\nIf a PR already exists for the branch:\n- Do not create another.\n- If requested (or if the body is still mostly unfilled template text), update it:\n\n  **bash:** `GH_PAGER=cat gh pr edit \u003Cpr-number-or-url> --body-file pr-body.md --attach '.\u002Fbefore.png#Before' --attach '.\u002Fdemo.mp4'`\n\n  **PowerShell:** `$env:GH_PAGER = \"cat\"; gh pr edit \u003Cpr-number-or-url> --body-file pr-body.md --attach '.\u002Fbefore.png#Before' --attach '.\u002Fdemo.mp4'`\n\n- Omit the `--attach` flags when step 4 did not prepare visual artifacts. Attach videos without a `#` suffix.\n\n- If a label needs to be applied to an existing PR, use `gh pr edit \u003Cpr-number-or-url> --add-label \u003Clabel-name>`.\n\n- Return the existing PR URL.\n\n### 8. Clean up\n\nAfter you are completely finished creating or updating the PR (after step 6 and, if needed, step 7), delete the temporary body file:\n- **bash:** `rm pr-body.md`\n- **PowerShell:** `Remove-Item pr-body.md`\n\n## Error handling\n\n| Error | Action |\n|-------|--------|\n| `gh: command not found` | Tell the user to install `gh` from https:\u002F\u002Fcli.github.com\u002F |\n| `gh auth` not logged in | Tell the user to run `gh auth login` |\n| `git push` rejected | Inform the user; do not force-push without explicit permission |\n| PR already exists | Follow step 7 (Handle existing PRs) above |\n\n## Notes\n\n- Do not bypass the template with ad-hoc bodies.\n- Keep the body aligned with `.github\u002Fpull_request_template.md`.\n- If the user asks to preview before creating, show the prepared PR body first, then create after confirmation.\n- For checklist sections with Yes\u002FNo alternatives, prefer selecting exactly one option per question when information is known.\n- **After creating the PR**, if non-trivial UI changes were detected in step 3, verify that the screenshots or recordings from step 4 are present and rendered in the PR description. If capture or upload was not possible, alert the user with a message like: \"This PR includes non-trivial UI changes to [Dashboard\u002FCLI\u002FExtension], but screenshots or recordings could not be added. Please add them so reviewers can evaluate the visual changes without running locally.\" Include the PR URL so the user can edit it directly.\n","You are a specialized pull request creation agent for this repository.\n\nYour goal is to **create a PR** and always **use the repository PR template** at `.github\u002Fpull_request_template.md`.\n\n## Example requests\n\n- \"Create a PR for this change\"\n- \"Push and open a pull request\"\n- \"Submit a PR with these fixes\"\n- \"Open a PR against the release branch\"\n\n## Prerequisites\n\nBefore starting, verify:\n- `gh` CLI is available: run `gh --version`. If missing, tell the user to install it from https:\u002F\u002Fcli.github.com\u002F.\n- Authentication is configured: run `gh auth status`. If not authenticated, tell the user to run `gh auth login`.\n\n## Procedure\n\n### 1. Prepare the branch\n\n- Confirm the current branch name with `git branch --show-current`.\n- Ensure changes are committed (`git status` should show a clean working tree or only untracked files).\n- Push the branch with `git push -u origin \u003Cbranch-name>`. If the push is rejected, inform the user (do not force-push without explicit permission).\n\n### 2. Determine PR metadata\n\n- **Head branch**: current branch unless the user specifies otherwise.\n- **Base branch**: user-specified base when provided; otherwise infer from context (or use the repository default branch).\n- **Title**: concise summary of the change.\n- **Labels**: add labels only when they are clearly applicable. Use the `breaking-change` label when the PR breaks public APIs or fundamentally changes the behavior of an existing scenario. Do not use it for every behavior change, additive feature, routine bug fix, or implementation-only change. Examples from existing `breaking-change` issues include API shape\u002Fsemantics changes, obsoleting a public API, changing endpoint allocation\u002Fwait behavior, changing Docker Compose publish behavior, and disabling local auth for Azure resources.\n\n### 3. Detect non-trivial UI changes\n\nBefore building the PR body, check whether the diff includes **non-trivial UI changes** to any of these areas:\n\n- **Dashboard** (`src\u002FAspire.Dashboard\u002F`): changes to `.razor`, `.razor.cs`, `.css`, `.js`, or UI assets under `src\u002FAspire.Dashboard\u002Fwwwroot\u002F` (e.g., `img\u002F**`, `favicon.ico`) that alter layout, add\u002Fremove components, change interactive behavior, or modify visual appearance beyond minor text or spacing tweaks.\n- **CLI** (`src\u002FAspire.Cli\u002F`): changes to command output formatting, interactive prompts, table\u002Flist rendering, spinners, progress indicators, or colored output beyond simple message text changes.\n- **VS Code Extension** (`extension\u002F`): changes to webview panels, tree views, status bar items, quick pick UIs, editor decorations, contributed view configuration (`package.json`), or UI assets (`resources\u002F**`) beyond minor label text changes.\n\nA change is **non-trivial** if it does more than:\n- Fix a typo or update a string literal without altering layout\n- Adjust a single CSS property (e.g., margin, padding) without changing visual structure\n- Change a tooltip or aria-label\n\nIf non-trivial UI changes are detected, add a prominent `### Screenshots \u002F Recordings` subsection in the PR body (under `## Description`) with the following content:\n\n```markdown\n### Screenshots \u002F Recordings\n\n> **This PR includes UI changes.** Please add screenshots or screen recordings so reviewers can evaluate the visual changes without running locally.\n>\n> - For before\u002Fafter comparisons, place them side-by-side or label them clearly.\n> - For interactive changes (animations, transitions, new flows), prefer a short screen recording (GIF or video).\n> - If you cannot capture visuals now, note what scenario to test and mark this section as TODO.\n\n\u003C!-- Add screenshots\u002Frecordings here -->\n```\n\n### 4. Upload visual artifacts\n\nFor non-trivial UI changes, upload screenshots or recordings as GitHub user attachments. Do not commit them to the source branch unless explicitly requested.\n\nTo make a recording, use the `create-video` skill: it can record the change from this branch's own build, and its `web` rendition stays under GitHub's 10 MB attachment limit. A short pull request demo needs no narration or slides.\n\nBefore uploading, inspect every artifact for secrets, credentials, tokens, customer or confidential data, private URLs, and unintended personal information. Redact or regenerate any artifact that contains sensitive data, and do not upload it until the inspection passes. Treat uploads as permanent public data because this public repository exposes attachments to everyone and the attachment API has no deletion endpoint.\n\nCheck attachment support for the command that will write the PR: `gh pr create --help` for a new PR or `gh pr edit --help` for an existing PR. Use `--attach` only when that command advertises it. Prepare local Markdown references for step 5 to insert at the intended location in `pr-body.md`. Use a table for before\u002Fafter images when appropriate:\n\n```markdown\n| Before | After |\n| --- | --- |\n| ![Before](.\u002Fbefore.png) | ![After](.\u002Fafter.png) |\n```\n\nPlace an image-style reference to a video on its own line in its own paragraph so GitHub CLI rewrites it to a bare asset URL that renders as a player:\n\n```markdown\n![Screen recording](.\u002Fdemo.mp4)\n```\n\nPrepare one flag per referenced file and append the flags to the final `gh pr create` command in step 6 or `gh pr edit` command in step 7. GitHub CLI rewrites the local references to uploaded URLs; without references, it appends the attachments to the end of the body. For images, text after `#` is the alt text when the body does not already provide it. Videos do not support alt text and must omit the `#` suffix:\n\n```shell\n--attach '.\u002Fbefore.png#Before' --attach '.\u002Fafter.png#After' --attach '.\u002Fdemo.mp4'\n```\n\nIf the relevant command does not advertise `--attach`, do not upload the artifacts or call GitHub's undocumented attachment endpoint. Tell the user that their installed GitHub CLI version does not support attachment uploads for that command and ask them to upgrade it. Include the detected version from `gh --version` and link to the official upgrade instructions at https:\u002F\u002Fgithub.com\u002Fcli\u002Fcli#installation.\n\nAfter the upgrade, run `gh --version` and check the relevant command help again. Retry the upload only when `--attach` is advertised. If the user does not upgrade, continue without uploading and retain the TODO in the Screenshots \u002F Recordings section so the missing visual evidence is explicit.\n\n### 5. Build PR body from template\n\n- Read `.github\u002Fpull_request_template.md`.\n- Use the template structure as the PR body.\n- If step 4 prepared visual artifacts and `gh --attach` is available, replace the `\u003C!-- Add screenshots\u002Frecordings here -->` placeholder with the prepared local Markdown references before running the create or edit command. Do not leave the placeholder in the final body after a successful upload.\n- Fill known details in `## Description` with reviewer- and user-facing context:\n  - Lead with **why** the change matters: the user problem, scenario, or workflow it improves.\n  - Summarize the user-visible behavior before implementation details: what users can now do, see, configure, or call.\n  - Include implementation details only after the behavior summary, and keep them concise.\n  - Evaluate whether the change makes security assumptions or guarantees, and include details only when security review may be needed.\n  - Include relevant validation: tests, manual verification, screenshots, recordings, generated help, or sample output.\n- For infra-only or internal-only changes, such as CI, build infrastructure, repository automation, tests, docs-only maintenance, or skill\u002Fworkflow guidance, do not add user-facing usage artifacts, `### Breaking changes`, or `### Security considerations` unless the change also affects user-visible behavior, breaks a public API or established scenario, or requires security review.\n- When the change affects user-facing behavior, add a subsection such as `### User-facing usage` or `### Examples` under `## Description` with concrete usage examples. Prefer examples from the diff, tests, docs, generated output, or commands you actually ran. Do not invent usage; if the usage cannot be determined confidently, ask the user or state that an example is not available.\n- Include the most relevant user-facing artifacts by change type:\n  - **Dashboard\u002FUI changes**: include dashboard screenshots, preferably before\u002Fafter when visual behavior changes.\n  - **CLI changes**: include command-specific `--help` output, example invocations with named arguments\u002Foptions, and an asciinema recording link when practical.\n  - **Public API changes**: include a consumer-focused usage example for the new API.\n  - **Integration changes**: include both C# and TypeScript usage examples when applicable.\n  - **Configuration, template, or docs changes**: include before\u002Fafter snippets, generated output, or the command a user runs.\n- Include a `### Security considerations` subsection only when the security checklist would be marked as needing security review because the change makes security assumptions or guarantees. Call out any relevant implications, such as:\n  - New network listeners, outbound connections, exposed ports, proxying, or service discovery behavior.\n  - Files written to global, shared, profile, cache, or temporary directories.\n  - Script execution, generated commands, shell escaping, or script\u002Fcontent injection risks.\n  - Path construction, archive extraction, file uploads\u002Fdownloads, or path traversal risks.\n  - Untrusted user input, data deserialization, authentication\u002Fauthorization changes, secrets, credentials, certificates, tokens, or environment variables.\n  - Container execution, process spawning, permissions, or elevated privileges.\n- Do not add a `### Security considerations` subsection for changes that do not need security review; instead, keep the checklist answer aligned with that assessment.\n- If the PR uses the `breaking-change` label, include a short `### Breaking changes` subsection that explains who is affected, what existing API or scenario changes, and how users should update.\n- Example PR body snippet shapes. Treat these as formats only; replace every placeholder with exact screenshots, commands, APIs, generated output, and security facts from the PR:\n  - **Dashboard\u002FUI changes**:\n    ```markdown\n    ### User-facing usage\n    The dashboard now shows \u003Cnew state or action> on the \u003Cpage\u002Fpanel>, so users can \u003Coutcome> without \u003Cold workaround>.\n    Screenshot: ![Dashboard showing \u003Cfeature>](\u003Cuploaded screenshot URL>)\n    ```\n  - **CLI changes**:\n    ````markdown\n    ### User-facing usage\n    Users can run the command with named options:\n    ```bash\n    aspire \u003Ccommand> \u003Cresource> --name \u003Ccommand-name> --timeout 30s\n    ```\n    Command help:\n    ```text\n    Usage:\n      aspire \u003Ccommand> \u003Cresource> [options]\n    Options:\n      --name \u003Cname>        \u003Cdescribe option>\n      --timeout \u003Cvalue>    \u003Cdescribe option>\n    ```\n    Recording: \u003Casciinema URL, if available>\n    ````\n  - **Public API changes**:\n    ````markdown\n    ### User-facing usage\n    Consumers can configure \u003Cscenario> with the new API:\n    ```csharp\n    var resource = builder.Add\u003CIntegration>(\"resource\")\n                          .With\u003CNewCapability>(\"\u003Cvalue>\");\n    ```\n    ````\n  - **Integration changes**:\n    ````markdown\n    ### User-facing usage\n    C# AppHost:\n    ```csharp\n    var resource = builder.Add\u003CIntegration>(\"resource\")\n                          .With\u003CNewCapability>(\"\u003Cvalue>\");\n    ```\n    TypeScript AppHost:\n    ```typescript\n    const resource = builder.add\u003CIntegration>(\"resource\")\n      .with\u003CNewCapability>(\"\u003Cvalue>\");\n    ```\n    ````\n  - **Configuration, template, or docs changes**:\n    ````markdown\n    ### User-facing usage\n    Users enable the behavior with:\n    ```json\n    {\n      \"\u003CsettingName>\": \"\u003Cvalue>\"\n    }\n    ```\n    Generated output now includes `\u003Cobservable output>`.\n    ````\n  - **Security-review changes**:\n    ```markdown\n    ### Security considerations\n    This change \u003Copens a listener\u002Fwrites to a shared directory\u002Fexecutes generated commands\u002Faccepts untrusted input>. Security review is needed to confirm \u003Cspecific concern>, such as host binding, path normalization, command escaping, or secret handling.\n    ```\n  - **Breaking changes**:\n    ```markdown\n    ### Breaking changes\n    This changes \u003Cexisting API or scenario>. Users who currently \u003Cold usage> should update to \u003Cnew usage or migration guidance>.\n    ```\n- Fill checklist choices by selecting known answers and leaving only unknown choices unchecked.\n- Keep `Fixes # (issue)` unless a concrete issue number is provided.\n- Write the body to a temporary file named `pr-body.md` in the repo root.\n\n### 6. Create the PR\n\nSet `GH_PAGER` to `cat` to prevent interactive paging, then create the PR. The syntax differs by shell:\n\nIf the PR needs labels, add the matching label flags to the create command. For breaking public API changes or fundamental existing-scenario behavior changes, include `--label breaking-change`.\n\n**bash\u002FLinux\u002FmacOS:**\n```bash\nGH_PAGER=cat gh pr create \\\n  --base \u003Cbase-branch> \\\n  --head \u003Chead-branch> \\\n  --title \"\u003Cpr-title>\" \\\n  --body-file pr-body.md \\\n  --attach '.\u002Fbefore.png#Before' \\\n  --attach '.\u002Fafter.png#After'\n```\n\n**PowerShell\u002FWindows:**\n```powershell\n$env:GH_PAGER = \"cat\"\ngh pr create `\n  --base \u003Cbase-branch> `\n  --head \u003Chead-branch> `\n  --title \"\u003Cpr-title>\" `\n  --body-file pr-body.md `\n  --attach '.\u002Fbefore.png#Before' `\n  --attach '.\u002Fafter.png#After'\n```\n\nOmit the `--attach` lines when step 4 did not prepare visual artifacts. Attach videos without a `#` suffix.\n\n> **Why `GH_PAGER=cat`?** The `gh` CLI pipes long output through a pager (like `less`) by default, which blocks in non-interactive terminals. Setting it to `cat` disables paging so output prints directly.\n\n> **Shell differences:** `VAR=val command` is bash syntax for setting an env var for a single command. PowerShell requires a separate `$env:VAR = \"val\"` statement (persists for the session, which is harmless here).\n\n### 7. Handle existing PRs\n\nIf a PR already exists for the branch:\n- Do not create another.\n- If requested (or if the body is still mostly unfilled template text), update it:\n\n  **bash:** `GH_PAGER=cat gh pr edit \u003Cpr-number-or-url> --body-file pr-body.md --attach '.\u002Fbefore.png#Before' --attach '.\u002Fdemo.mp4'`\n\n  **PowerShell:** `$env:GH_PAGER = \"cat\"; gh pr edit \u003Cpr-number-or-url> --body-file pr-body.md --attach '.\u002Fbefore.png#Before' --attach '.\u002Fdemo.mp4'`\n\n- Omit the `--attach` flags when step 4 did not prepare visual artifacts. Attach videos without a `#` suffix.\n\n- If a label needs to be applied to an existing PR, use `gh pr edit \u003Cpr-number-or-url> --add-label \u003Clabel-name>`.\n\n- Return the existing PR URL.\n\n### 8. Clean up\n\nAfter you are completely finished creating or updating the PR (after step 6 and, if needed, step 7), delete the temporary body file:\n- **bash:** `rm pr-body.md`\n- **PowerShell:** `Remove-Item pr-body.md`\n\n## Error handling\n\n| Error | Action |\n|-------|--------|\n| `gh: command not found` | Tell the user to install `gh` from https:\u002F\u002Fcli.github.com\u002F |\n| `gh auth` not logged in | Tell the user to run `gh auth login` |\n| `git push` rejected | Inform the user; do not force-push without explicit permission |\n| PR already exists | Follow step 7 (Handle existing PRs) above |\n\n## Notes\n\n- Do not bypass the template with ad-hoc bodies.\n- Keep the body aligned with `.github\u002Fpull_request_template.md`.\n- If the user asks to preview before creating, show the prepared PR body first, then create after confirmation.\n- For checklist sections with Yes\u002FNo alternatives, prefer selecting exactly one option per question when information is known.\n- **After creating the PR**, if non-trivial UI changes were detected in step 3, verify that the screenshots or recordings from step 4 are present and rendered in the PR description. If capture or upload was not possible, alert the user with a message like: \"This PR includes non-trivial UI changes to [Dashboard\u002FCLI\u002FExtension], but screenshots or recordings could not be added. Please add them so reviewers can evaluate the visual changes without running locally.\" Include the PR URL so the user can edit it directly.\n",{"name":5,"description":7},"main","cec61ac9b795bbfd9913f0c7196689b0d7a215d7",".agents\u002Fskills\u002Fcreate-pr",1039,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire","https:\u002F\u002Faspire.dev","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-15 00:32:23",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add microsoft\u002Faspire --skill create-pr",{"tool":60,"command":61},"bunx","bunx skills add microsoft\u002Faspire --skill create-pr",{"tool":63,"command":64},"pnpm","pnpm dlx skills add microsoft\u002Faspire --skill create-pr","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcreate-pr\u002FSKILL.md",true,[],[69,106,129,142,160,184],{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":88,"publishedAt":39},"01M6FKZQPMA7VRA0PRBZRDFJTX","vscode-extension","Use when investigating, developing, debugging, testing, or reviewing Aspire VS Code extension behavior under extension\u002F, including extension UI, command, debugger, RPC, DCP, MCP, and CLI-integration issues or features.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fvscode-extension\u002FSKILL.md",[75,80,83],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":81,"categoryName":82,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":84,"categoryName":85,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,29,105,22],"vscode","vscode extension","extension","testing","MCP","cli","aspire","debugging","code","issues","rpc","ui","integration","debugger","command","behavior","features",{"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":115,"publishedAt":39},"01M6FKZJG81XP80SVWFBJVMDWN","update-container-images","Updates Docker container image tags used by Aspire hosting integrations. Queries registries for newer tags, uses LLM to determine version-compatible updates, and applies changes. Use this when asked to update container image versions.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fupdate-container-images\u002FSKILL.md",[112],{"categoryNo":113,"categoryName":114,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000016","图像与多媒体",[116,117,118,119,120,121,122,95,123,29,124,125,126,127,128,27,26,22],"container images","update","container","images","update container images","image","docker","integrations","version","hosting","queries","tags","updates",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":136,"publishedAt":39},"01M6FKZDY1MY0QA62EYSDG5NHW","test-management","Quarantines or disables flaky\u002Fproblematic tests using the QuarantineTools utility","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftest-management\u002FSKILL.md",[135],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},[137,138,139,140,141],"test","management","test management","tests","utility",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":39},"01M6FKZAQ428JX8F6NSA19XBQJ","startup-perf","Measures Aspire startup profiling with CLI self-profile capture and dashboard export traces.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstartup-perf\u002FSKILL.md",[],[149,150,151,94,152,95,153,154,155,156,157,158,159],"perf","startup","startup perf","dashboard","profiling","capture","profile","export","self","with","traces",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":166,"publishedAt":39},"01M6FKZ4W4J0ET0Q0C2Z30HYRV","reviewing-aspire-architecture","Use only when the user explicitly requests a deep Aspire architectural or pattern review of an existing PR or diff, or when a generic reviewer escalates a named Aspire-domain question it cannot resolve. Do not use for ordinary review, implementation, debugging, explanation, or design discussion—even when a PR is referenced—and never select it from changed file paths alone.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Freviewing-aspire-architecture\u002FSKILL.md",[],[167,95,168,169,23,20,96,170,171,172,173,29,174,175,176,177,178,179,180,181,27,182,183,22],"architecture","reviewing aspire architecture","design","file","select","reviewer","question","diff","never","only","do","domain","pattern","deep","paths","Existing","generic",{"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":191,"publishedAt":39},"01M6FKYZ44BEPJNV8VQ0X73CZR","pr-testing","Use when asked to test a microsoft\u002Faspire pull request, including CLI, hosting, dashboard, component, template, and VS Code extension changes. Also covers testing PRs that change CI infrastructure — GitHub Actions (workflows, actions, gh-aw agentic workflows, CI scripts under .github\u002F and eng\u002F) and Azure DevOps pipelines (eng\u002Fpipelines, eng\u002Fcommon).","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpr-testing\u002FSKILL.md",[190],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},[92,20,192,94,193,194,152,195,196,197,198,199,95,200,97,201,202,203,31,204,29,205,125,206,91,207,26,208],"pr testing","github","agentic","workflows","change","component","agentic workflows","azure devops","infrastructure","actions","ci","github actions","common","devops","pipelines","scripts","prs"]