[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699D36GQS9JD18SQTVN9PZS":3,"skill-same:01M699D36GQS9JD18SQTVN9PZS":67},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M699D36GQS9JD18SQTVN9PZS","commit",null,"Commit staged or unstaged changes with an AI-generated commit message that matches the repository's existing commit style. Use when the user asks to 'commit', 'commit changes', 'create a commit', 'save my work', or 'check in code'.","microsoft\u002Fvscode","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M6998NK2WED5M549DX06VBCH",195270,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode\u002Fblob\u002Fmain\u002Fsrc\u002Fvs\u002Fsessions\u002Fskills\u002Fcommit\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"message","when","check in","Existing","staged","changes","my","with","unstaged","style","commit changes","use","generated","check","work","repository","commit message","code","create","2026-11-10 10:12:30",false,"---\nname: commit\ndescription: Commit staged or unstaged changes with an AI-generated commit message that matches the repository's existing commit style. Use when the user asks to 'commit', 'commit changes', 'create a commit', 'save my work', or 'check in code'.\n---\n\u003C!-- Customize this skill and select save to override its behavior. Delete that copy to restore the built-in behavior. -->\n\n# Commit Changes\n\nHelp the user commit code changes with a well-crafted commit message derived from the diff, following the conventions already established in the repository.\n\n## Guidelines\n\n- **Never amend existing commits** without asking.\n- **Never force-push or push** without explicit user approval.\n- **Never skip pre-commit hooks** (do not use `--no-verify`).\n- **Never skip signing commits** (do not use `--no-gpg-sign`).\n- **Never revert, reset, or discard user changes** unless the user explicitly asked for that.\n- Check for obvious secrets or generated artifacts that should not be committed. If something looks risky - ask the user.\n- When in doubt about staging, convention, or message content — ask the user.\n\n## Workflow\n\n### 1. Discover the repository's commit convention\n\nRun the following to sample recent commits and the user's own commits:\n\n```\n# Recent repo commits (for overall style)\ngit log --oneline -20\n\n# User's recent commits (for personal style)\ngit log --oneline --author=\"$(git config user.name)\" -10\n```\n\nAnalyse the output to determine the commit message convention used in the repository (e.g. Conventional Commits, Gitmoji, ticket-prefixed, free-form). All generated messages **must** follow the detected convention.\n\n### 2. Check repository status\n\n```\ngit status --short\n```\n\n- If there are **no changes** (working tree clean, nothing staged), inform the user and stop.\n- If there are **staged changes**, proceed with those and do not stage any unstaged changes.\n- If there are **only unstaged changes**, stage everything (`git add -A`), and proceed with those.\n\n### 3. Generate the commit message\n\nObtain the full diff of what will be committed:\n\n```bash\ngit diff --cached --stat\ngit diff --cached\n```\n\nUsing the diff and the commit convention detected in step 1, draft a commit message with:\n\n- A **subject line** (≤ 72 characters) that summarises the change, following the repository's convention.\n- An optional **body** that explains *why* the change was made, only when the diff is non-trivial.\n- Reference issue\u002Fticket numbers when they appear in branch names or related context.\n- Focus on the intent of the change, not a file-by-file inventory.\n\n### 4. Commit\n\nConstruct the `git commit` command with the generated message.\n\nExecute the commit:\n\n```\ngit commit -m \"\u003Csubject>\" -m \"\u003Cbody>\"\n```\n\n### 5. Confirm\n\nAfter the commit:\n\n- Run `git status --short` to confirm the commit completed.\n- Run `git log --oneline -1` to show the new commit.\n- If pre-commit hooks changed files or blocked the commit, summarize exactly what happened.\n- If hooks rewrote files after the commit attempt, do not amend automatically. Tell the user what changed and ask whether they want you to stage and commit those follow-up edits.\n","\u003C!-- Customize this skill and select save to override its behavior. Delete that copy to restore the built-in behavior. -->\n\n# Commit Changes\n\nHelp the user commit code changes with a well-crafted commit message derived from the diff, following the conventions already established in the repository.\n\n## Guidelines\n\n- **Never amend existing commits** without asking.\n- **Never force-push or push** without explicit user approval.\n- **Never skip pre-commit hooks** (do not use `--no-verify`).\n- **Never skip signing commits** (do not use `--no-gpg-sign`).\n- **Never revert, reset, or discard user changes** unless the user explicitly asked for that.\n- Check for obvious secrets or generated artifacts that should not be committed. If something looks risky - ask the user.\n- When in doubt about staging, convention, or message content — ask the user.\n\n## Workflow\n\n### 1. Discover the repository's commit convention\n\nRun the following to sample recent commits and the user's own commits:\n\n```\n# Recent repo commits (for overall style)\ngit log --oneline -20\n\n# User's recent commits (for personal style)\ngit log --oneline --author=\"$(git config user.name)\" -10\n```\n\nAnalyse the output to determine the commit message convention used in the repository (e.g. Conventional Commits, Gitmoji, ticket-prefixed, free-form). All generated messages **must** follow the detected convention.\n\n### 2. Check repository status\n\n```\ngit status --short\n```\n\n- If there are **no changes** (working tree clean, nothing staged), inform the user and stop.\n- If there are **staged changes**, proceed with those and do not stage any unstaged changes.\n- If there are **only unstaged changes**, stage everything (`git add -A`), and proceed with those.\n\n### 3. Generate the commit message\n\nObtain the full diff of what will be committed:\n\n```bash\ngit diff --cached --stat\ngit diff --cached\n```\n\nUsing the diff and the commit convention detected in step 1, draft a commit message with:\n\n- A **subject line** (≤ 72 characters) that summarises the change, following the repository's convention.\n- An optional **body** that explains *why* the change was made, only when the diff is non-trivial.\n- Reference issue\u002Fticket numbers when they appear in branch names or related context.\n- Focus on the intent of the change, not a file-by-file inventory.\n\n### 4. Commit\n\nConstruct the `git commit` command with the generated message.\n\nExecute the commit:\n\n```\ngit commit -m \"\u003Csubject>\" -m \"\u003Cbody>\"\n```\n\n### 5. Confirm\n\nAfter the commit:\n\n- Run `git status --short` to confirm the commit completed.\n- Run `git log --oneline -1` to show the new commit.\n- If pre-commit hooks changed files or blocked the commit, summarize exactly what happened.\n- If hooks rewrote files after the commit attempt, do not amend automatically. Tell the user what changed and ask whether they want you to stage and commit those follow-up edits.\n",{"name":5,"description":7},"main","11ba54a90a0ff8720cf47c086f5a9948eef9cf2c","src\u002Fvs\u002Fsessions\u002Fskills\u002Fcommit",43791,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode","https:\u002F\u002Fcode.visualstudio.com","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-12 03:13:10",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add microsoft\u002Fvscode --skill commit",{"tool":59,"command":60},"bunx","bunx skills add microsoft\u002Fvscode --skill commit",{"tool":62,"command":63},"pnpm","pnpm dlx skills add microsoft\u002Fvscode --skill commit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode\u002Fblob\u002Fmain\u002Fsrc\u002Fvs\u002Fsessions\u002Fskills\u002Fcommit\u002FSKILL.md",true,[],[68,93,113,125,139,154],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":38},"01M70H0ANBKZAVEP1NVV4K28M3","sweeper-query","Answer natural-language questions about the VS Code Sweeper's published issue index (index-\u003Cname>.json for microsoft\u002Fvscode and the enrolled family repos) — which issues are agent-ready to implement or plan, what the sweeper proposed for an assignee or area, whether the sweeper knows a report as a duplicate, the highest-value open bugs in a lane — and, for one issue, the review's full record (evidence with file citations, fix brief, proposed comment). Use ONLY when the request explicitly names the sweeper — \"sweeper\", \"vscodesweeper\", \"sweeper-query\", a sweeper verdict, record, brief or index, an agent-ready issue — or asks what \"the sweeper\" found, proposed or knows. Do NOT use for general questions about issues, duplicates, priorities or ranking that do not mention the sweeper. Read-only; discovery only.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fsweeper-query\u002FSKILL.md",[],[75,76,77,78,79,20,80,81,82,83,84,85,86,87,88,89,90,91,92,36],"sweeper query","query","sweeper","review","fix","request","which","natural-language","ranking","duplicates","ready","only","read","plan","open","Citations","brief","issues",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":38},"01M699DRJS4YJCV600Q72SVVWE","update-skills","Create or update repository skills and instructions when major learnings are discovered during a session. Use when the user says \"learn!\", when a significant pattern or pitfall is identified, or when reusable domain knowledge should be captured for future sessions.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode\u002Fblob\u002Fmain\u002Fsrc\u002Fvs\u002Fsessions\u002Fskills\u002Fupdate-skills\u002FSKILL.md",[],[100,101,102,103,104,105,106,30,107,108,109,110,34,111,37,112,20],"update","update skills","for","pattern","domain","learnings","reusable","session","user","instructions","knowledge","learn","sessions",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":38},"01M699DPWHZ72B66P82EW31RNE","update-pr","Update the pull request for the current session. Use when the user wants to push new changes to an existing PR.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode\u002Fblob\u002Fmain\u002Fsrc\u002Fvs\u002Fsessions\u002Fskills\u002Fupdate-pr\u002FSKILL.md",[],[100,120,121,20,80,22,102,30,107,108,122,123,124,24],"pr","update pr","push","pull","pull request",{"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":131,"publishedAt":38},"01M699DJMR6CE1MH5XCJZ0GFQ0","sync","Sync the current session branch with its upstream branch, or publish the current session branch to a remote. Use when the user asks to sync a branch, pull latest changes, rebase onto upstream, push current branch, publish branch, or set upstream.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode\u002Fblob\u002Fmain\u002Fsrc\u002Fvs\u002Fsessions\u002Fskills\u002Fsync\u002FSKILL.md",[],[127,132,133,122,123,134,20,24,135,26,136,137,30,107,108,138],"SET","publish","rebase","latest","remote","upstream","branch",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":38},"01M699DGXHX6A2A72X57R6GGHJ","sync-upstream","Update a stale session branch by rebasing onto the latest origin. Use when the upstream has moved significantly and the session needs to catch up, resolving conflicts by preserving upstream changes and adapting session work to fit.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode\u002Fblob\u002Fmain\u002Fsrc\u002Fvs\u002Fsessions\u002Fskills\u002Fsync-upstream\u002FSKILL.md",[],[137,127,146,147,20,148,149,24,135,150,151,152,153,30,107,138,33,100],"sync upstream","fit","catch","catch up","origin","conflicts","stale","up",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":38},"01M699DEXYFWDGW0BAXJ5QQ377","merge","Merge changes from the topic branch to the merge base branch. Use when the user wants to merge their session's work back to the base branch.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode\u002Fblob\u002Fmain\u002Fsrc\u002Fvs\u002Fsessions\u002Fskills\u002Fmerge\u002FSKILL.md",[],[156,107,30,33,138,108,20,161,162,24],"back","base"]