[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6992A56ZVS4J4P403GDXN3F":3,"skill-same:01M6992A56ZVS4J4P403GDXN3F":62},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":38,"commitSha":39,"skillDirectory":40,"forksCount":41,"repositoryHtmlUrl":42,"repositoryHomepageUrl":43,"ownerHtmlUrl":44,"ownerBlogUrl":45,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M6992A56ZVS4J4P403GDXN3F","crosvm-contribution-workflow",null,"Skill to assist with the contribution workflow for crosvm. ALL agents making code changes MUST use this skill to run presubmit checks before committing.","google\u002Fcrosvm","google","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1342004?v=4","01M698VYEFDM0VJBZDYYJ2T83S","Google","01M69926BCXV63W79JPA18Y40G",1365,"BSD-3-Clause","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fcrosvm\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcrosvm_contribution_workflow\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32],"crosvm contribution workflow","workflow","contribution","run","code","use","with","for","changes","2026-11-10 10:12:30",false,"---\nname: crosvm-contribution-workflow\ndescription: Skill to assist with the contribution workflow for crosvm. ALL agents making code changes MUST use this skill to run presubmit checks before committing.\n---\n\n# Contribution Workflow Skill\n\nThis skill assists with the crosvm contribution workflow. ALL agents making code changes MUST use\nthis skill to verify their changes (by compiling and running tests) before proceeding to commit or\nrequesting review, even if the user does not explicitly ask to run tests.\n\n## Formatting and Presubmit Checks\n\nAll commands must be executed from the repository root directory.\n\n### Choosing the Right Test Method\n\nDepending on the scope of your changes, choose the appropriate method to verify your work. The\nrelevant checks must pass before you proceed to create a commit or request review.\n\n- **`.\u002Ftools\u002Fdev_container cargo check`**\n\n  - **Usage**: Use this during normal development iterations.\n  - **Description**: It attempts to compile the project with the default feature set. Fast and\n    useful for quick feedback on syntax and basic type checking.\n\n- **`tools\u002Fdev_container .\u002Ftools\u002Fpresubmit quick`**\n\n  - **Usage**: Run this as a minimum sanity check before creating a commit.\n  - **Description**: Performs a health check, runs unit tests on x86, and runs clippy lints.\n\n- **`tools\u002Fdev_container .\u002Ftools\u002Fpresubmit`**\n\n  - **Usage**: Run this when you have made changes that might affect multiple platforms or are more\n    substantial.\n  - **Description**: In addition to the quick checks, this performs cross-compilation and runs unit\n    tests for other targets. **Note: The default set does not cover all platforms (e.g., riscv).**\n\n- **`tools\u002Fdev_container .\u002Ftools\u002Fpresubmit clippy`**\n\n  - **Usage**: Run this to quickly check all platforms (including riscv) for cross-platform changes.\n  - **Description**: Runs clippy lints for all supported platforms. This is a relatively quick way\n    to ensure your changes don't break compilation on any platform.\n\n- **`tools\u002Fdev_container .\u002Ftools\u002Fpresubmit all`**\n\n  - **Usage**: Run this before final submission or for complex changes that require full validation.\n  - **Description**: This is the most thorough check. It runs all the above tests on all supported\n    platforms, including end-to-end (e2e) tests using QEMU. **Note: This takes a significant amount\n    of time.**\n\n### Commands\n\n#### 1. Auto-formatting\n\nAutomatically fixes code formatting. This also applies to Markdown files (`.md`) in addition to\nsource code.\n\n```bash\ntools\u002Fdev_container .\u002Ftools\u002Ffmt\n```\n\n#### 2. Running Checks\n\nUse one of the methods described above. Example for quick check:\n\n```bash\ntools\u002Fdev_container .\u002Ftools\u002Fpresubmit quick\n```\n\n> [!TIP] If your tests fail on presubmit and you need to debug the tests individually or inspect the\n> VM environment, please refer to the crosvm-testing [SKILL.md](..\u002Fcrosvm_testing\u002FSKILL.md).\n\n## Uploading Changes\n\nOnce your changes are verified and formatted, you can upload them to Gerrit for review.\n\nWe use a custom tool `.\u002Ftools\u002Fcl` for this. The basic command to upload is:\n\n```bash\n.\u002Ftools\u002Fcl upload\n```\n\n> [!TIP] For advanced usage of the CL tool, including rebasing downstream branches, checking CL\n> status, and pruning old branches, see the specialized crosvm-cl-tool\n> [SKILL.md](..\u002Fcrosvm_cl_tool\u002FSKILL.md).\n\n## Commit Message Guidelines\n\nRefer to these guidelines when writing commit messages for crosvm. You **must** only write a commit\nmessage AFTER ensuring all necessary tests pass.\n\n### 1. Subject Line\n\n- **Format**: Starts with a tag representing the component, followed by a colon and space, then the\n  description.\n  - Example: `devices: vhost: user: Add Connection type`\n- **Tags**: Usually the name of the crate modified (e.g., `devices:`, `base:`). Use paths for\n  specific components (e.g., `devices: vhost: user:`).\n- **Length**: No more than 50 characters, including tags.\n\n### 2. Body\n\n- **Content**: State the motivation followed by the impact\u002Faction.\n- **Wrapping**: Text must be wrapped to 72 characters.\n\n### 3. BUG Lines\n\n- **Format**: `BUG=b:\u003Cbug number>` for Google issue tracker, or `BUG=None`.\n- You can have multiple `BUG` lines.\n- **Tip**: If you do not know the bug number, ask the user for clarification.\n\n### 4. TEST Lines\n\n- **Format**: Describe how the change was tested in free form.\n- You can have multiple `TEST` lines.\n\n### 5. Change-Id\n\n- The gerrit commit message hook will insert this automatically if the commit-msg hook is installed.\n- **Important**: The `Change-Id` links the commit to a specific Gerrit change list (CL). Unless\n  explicitly requested by the user, **DO NOT** change or remove the `Change-Id` when cherry-picking,\n  rebasing, or amending commits.\n\n### Example Commit Message\n\n```\ndevices: vhost: user: vmm: Add Connection type\n\nThis abstracts away the cross-platform differences:\ncfg(any(target_os = \"android\", target_os = \"linux\")) uses a Unix\ndomain domain stream socket to connect to the vhost-user backend, and\ncfg(windows) uses a Tube.\n\nBUG=b:249361790\nTEST=tools\u002Fpresubmit all\n\nChange-Id: I47651060c2ce3a7e9f850b7ed9af8bd035f82de6\n```\n\n## End-to-End Contribution Journey\n\nHere is the typical sequence of steps for contributing a change:\n\n1. **Start a branch**:\n   ```bash\n   git checkout -b my-feature-branch --track origin\u002Fmain\n   ```\n1. **Make changes** and implement your feature or fix.\n1. **Format your code**:\n   ```bash\n   tools\u002Fdev_container .\u002Ftools\u002Ffmt\n   ```\n1. **Run presubmit checks**:\n   ```bash\n   tools\u002Fdev_container .\u002Ftools\u002Fpresubmit quick\n   ```\n   *(If tests fail and you need to debug individually or inspect the VM environment, refer to the\n   crosvm-testing [SKILL.md](..\u002Fcrosvm_testing\u002FSKILL.md)).*\n1. **Commit your changes** (following the [Commit Message Guidelines](#commit-message-guidelines)):\n   ```bash\n   git commit\n   ```\n1. **Upload the CL**:\n   ```bash\n   .\u002Ftools\u002Fcl upload\n   ```\n   *(Refer to the crosvm-cl-tool [SKILL.md](..\u002Fcrosvm_cl_tool\u002FSKILL.md) if you need to add\n   reviewers, trigger try jobs, or rebase).*\n","# Contribution Workflow Skill\n\nThis skill assists with the crosvm contribution workflow. ALL agents making code changes MUST use\nthis skill to verify their changes (by compiling and running tests) before proceeding to commit or\nrequesting review, even if the user does not explicitly ask to run tests.\n\n## Formatting and Presubmit Checks\n\nAll commands must be executed from the repository root directory.\n\n### Choosing the Right Test Method\n\nDepending on the scope of your changes, choose the appropriate method to verify your work. The\nrelevant checks must pass before you proceed to create a commit or request review.\n\n- **`.\u002Ftools\u002Fdev_container cargo check`**\n\n  - **Usage**: Use this during normal development iterations.\n  - **Description**: It attempts to compile the project with the default feature set. Fast and\n    useful for quick feedback on syntax and basic type checking.\n\n- **`tools\u002Fdev_container .\u002Ftools\u002Fpresubmit quick`**\n\n  - **Usage**: Run this as a minimum sanity check before creating a commit.\n  - **Description**: Performs a health check, runs unit tests on x86, and runs clippy lints.\n\n- **`tools\u002Fdev_container .\u002Ftools\u002Fpresubmit`**\n\n  - **Usage**: Run this when you have made changes that might affect multiple platforms or are more\n    substantial.\n  - **Description**: In addition to the quick checks, this performs cross-compilation and runs unit\n    tests for other targets. **Note: The default set does not cover all platforms (e.g., riscv).**\n\n- **`tools\u002Fdev_container .\u002Ftools\u002Fpresubmit clippy`**\n\n  - **Usage**: Run this to quickly check all platforms (including riscv) for cross-platform changes.\n  - **Description**: Runs clippy lints for all supported platforms. This is a relatively quick way\n    to ensure your changes don't break compilation on any platform.\n\n- **`tools\u002Fdev_container .\u002Ftools\u002Fpresubmit all`**\n\n  - **Usage**: Run this before final submission or for complex changes that require full validation.\n  - **Description**: This is the most thorough check. It runs all the above tests on all supported\n    platforms, including end-to-end (e2e) tests using QEMU. **Note: This takes a significant amount\n    of time.**\n\n### Commands\n\n#### 1. Auto-formatting\n\nAutomatically fixes code formatting. This also applies to Markdown files (`.md`) in addition to\nsource code.\n\n```bash\ntools\u002Fdev_container .\u002Ftools\u002Ffmt\n```\n\n#### 2. Running Checks\n\nUse one of the methods described above. Example for quick check:\n\n```bash\ntools\u002Fdev_container .\u002Ftools\u002Fpresubmit quick\n```\n\n> [!TIP] If your tests fail on presubmit and you need to debug the tests individually or inspect the\n> VM environment, please refer to the crosvm-testing [SKILL.md](..\u002Fcrosvm_testing\u002FSKILL.md).\n\n## Uploading Changes\n\nOnce your changes are verified and formatted, you can upload them to Gerrit for review.\n\nWe use a custom tool `.\u002Ftools\u002Fcl` for this. The basic command to upload is:\n\n```bash\n.\u002Ftools\u002Fcl upload\n```\n\n> [!TIP] For advanced usage of the CL tool, including rebasing downstream branches, checking CL\n> status, and pruning old branches, see the specialized crosvm-cl-tool\n> [SKILL.md](..\u002Fcrosvm_cl_tool\u002FSKILL.md).\n\n## Commit Message Guidelines\n\nRefer to these guidelines when writing commit messages for crosvm. You **must** only write a commit\nmessage AFTER ensuring all necessary tests pass.\n\n### 1. Subject Line\n\n- **Format**: Starts with a tag representing the component, followed by a colon and space, then the\n  description.\n  - Example: `devices: vhost: user: Add Connection type`\n- **Tags**: Usually the name of the crate modified (e.g., `devices:`, `base:`). Use paths for\n  specific components (e.g., `devices: vhost: user:`).\n- **Length**: No more than 50 characters, including tags.\n\n### 2. Body\n\n- **Content**: State the motivation followed by the impact\u002Faction.\n- **Wrapping**: Text must be wrapped to 72 characters.\n\n### 3. BUG Lines\n\n- **Format**: `BUG=b:\u003Cbug number>` for Google issue tracker, or `BUG=None`.\n- You can have multiple `BUG` lines.\n- **Tip**: If you do not know the bug number, ask the user for clarification.\n\n### 4. TEST Lines\n\n- **Format**: Describe how the change was tested in free form.\n- You can have multiple `TEST` lines.\n\n### 5. Change-Id\n\n- The gerrit commit message hook will insert this automatically if the commit-msg hook is installed.\n- **Important**: The `Change-Id` links the commit to a specific Gerrit change list (CL). Unless\n  explicitly requested by the user, **DO NOT** change or remove the `Change-Id` when cherry-picking,\n  rebasing, or amending commits.\n\n### Example Commit Message\n\n```\ndevices: vhost: user: vmm: Add Connection type\n\nThis abstracts away the cross-platform differences:\ncfg(any(target_os = \"android\", target_os = \"linux\")) uses a Unix\ndomain domain stream socket to connect to the vhost-user backend, and\ncfg(windows) uses a Tube.\n\nBUG=b:249361790\nTEST=tools\u002Fpresubmit all\n\nChange-Id: I47651060c2ce3a7e9f850b7ed9af8bd035f82de6\n```\n\n## End-to-End Contribution Journey\n\nHere is the typical sequence of steps for contributing a change:\n\n1. **Start a branch**:\n   ```bash\n   git checkout -b my-feature-branch --track origin\u002Fmain\n   ```\n1. **Make changes** and implement your feature or fix.\n1. **Format your code**:\n   ```bash\n   tools\u002Fdev_container .\u002Ftools\u002Ffmt\n   ```\n1. **Run presubmit checks**:\n   ```bash\n   tools\u002Fdev_container .\u002Ftools\u002Fpresubmit quick\n   ```\n   *(If tests fail and you need to debug individually or inspect the VM environment, refer to the\n   crosvm-testing [SKILL.md](..\u002Fcrosvm_testing\u002FSKILL.md)).*\n1. **Commit your changes** (following the [Commit Message Guidelines](#commit-message-guidelines)):\n   ```bash\n   git commit\n   ```\n1. **Upload the CL**:\n   ```bash\n   .\u002Ftools\u002Fcl upload\n   ```\n   *(Refer to the crosvm-cl-tool [SKILL.md](..\u002Fcrosvm_cl_tool\u002FSKILL.md) if you need to add\n   reviewers, trigger try jobs, or rebase).*\n",{"name":5,"description":7},"main","678337f67da6ca6d661ad97cf1e9926fa1b75cba",".agents\u002Fskills\u002Fcrosvm_contribution_workflow",191,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fcrosvm","https:\u002F\u002Fcrosvm.dev\u002Fbook\u002F","https:\u002F\u002Fgithub.com\u002Fgoogle","https:\u002F\u002Fopensource.google\u002F","Google ❤️ Open Source","2026-11-14 21:28:40",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add google\u002Fcrosvm --skill crosvm-contribution-workflow",{"tool":54,"command":55},"bunx","bunx skills add google\u002Fcrosvm --skill crosvm-contribution-workflow",{"tool":57,"command":58},"pnpm","pnpm dlx skills add google\u002Fcrosvm --skill crosvm-contribution-workflow","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fcrosvm\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcrosvm_contribution_workflow\u002FSKILL.md",true,[],[63,81,96],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":72,"publishedAt":33},"01M6992CHS0VHSRR8MGCTREB6X","crosvm-testing","Skill to assist with running tests and managing test VMs in the crosvm repository.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fcrosvm\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcrosvm_testing\u002FSKILL.md",[69],{"categoryNo":70,"categoryName":71,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[73,74,75,76,77,78,30,79,80],"testing","crosvm testing","repository","test","running tests","tests","vms","running",{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":33},"01M6992B6MYXZ96A8QKTW1CTKM","crosvm-dev-container","Skill to assist with using the `dev_container` tool for running builds, tests, and other tools in a consistent containerized environment.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fcrosvm\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcrosvm_dev_container\u002FSKILL.md",[],[88,89,90,91,80,78,31,92,30,93,94,95],"crosvm dev container","dev","dev container","container","containerized","environment","tool","Tools",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":33},"01M699292R6S94P3Q1J81FT2T1","crosvm-cl-tool","Skill to assist with using the `.\u002Ftools\u002Fcl` tool for managing and uploading Gerrit CLs in the crosvm repository.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fcrosvm\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcrosvm_cl_tool\u002FSKILL.md",[],[94,103,104,31,30,95,75],"crosvm cl tool","cl"]