菜单
Derive and validate the canonical scope for IronRDP Conventional Commit and pull-request titles. Use whenever composing, reviewing, correcting, or checking a commit or PR title, especially when several crates or product surfaces intersect.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Devolutions/IronRDP --skill commit-scope命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Write or substantially revise a Rust crate's README.md as a concise, user-facing design document. Use whenever creating a crate README, documenting a planned crate, or defining a crate's purpose, role, or interface before implementation.
Create and integrate a new Rust crate in the IronRDP workspace. Use whenever adding, scaffolding, or initializing a crate under crates/, including requests that mention cargo new, a new library package, or registering a crate in the architecture.
Add or change Rust crate dependencies while preserving IronRDP's public-dependency markers. Use whenever adding, updating, renaming, removing, or changing features of a Cargo dependency, or when a public API starts or stops exposing dependency-owned types or traits.
基于 SOC 职业分类
正在显示 SKILL.md
| name | commit-scope |
| description | Derive and validate the canonical scope for IronRDP Conventional Commit and pull-request titles. Use whenever composing, reviewing, correcting, or checking a commit or PR title, especially when several crates or product surfaces intersect. |
Choose at most one optional scope for <type>[optional scope][!]: <description>.
meta core error pdu str bulk graphics config input connector session driver
svc dvc cliprdr rdpdr rdpsnd rdpeai displaycontrol rdpei echo egfx rdpeudp rdpeusb rdpemt rdcleanpath
tls mstsgu vmconnect
client viewer agent daemon rpc activex server web ffi replay
xtask fuzz release pr-automation agents
Most scopes match an ironrdp-* component after removing the prefix.
Use these aggregate mappings:
meta: the ironrdp meta crate.graphics: ironrdp-graphics and ironrdp-nscodec.config: ironrdp-cfg, ironrdp-propertyset, and ironrdp-rdpfile.input: ironrdp-input and ironrdp-ainput.driver: ironrdp-async, ironrdp-blocking, ironrdp-tokio, and ironrdp-futures.dvc: DRDYNVC infrastructure, the COM plugin, and the pipe proxy, but not specific dynamic channels.cliprdr, rdpdr, and rdpsnd: each protocol and its format or native support crates.rdpeai: MS-RDPEAI audio input protocol and related client capture wiring.server: ironrdp-acceptor and ironrdp-server.web: WASM bindings, the Rust web helper, and everything under web-client.ffi: the Rust FFI and generated or manual .NET bindings, but not ActiveX.replay: ironrdp-replay-client.fuzz: fuzz targets, harnesses, corpora, and fuzzing automation.release: changelog, packaging, publishing, and release automation.pr-automation: automated PR classification and review infrastructure.agents: agent instructions and reusable skills.Use the component scope with any applicable type:
fix(cliprdr): reject invalid file ranges
feat(driver): expose multitransport handoff
ci(release): sign binary artifacts
build(web): update frontend dependencies
Do not use types or cross-cutting aspects as scopes.
This excludes ci, test, docs, build, deps, perf, tooling, automation, workspace, protocol, channels, native, security, and api.
Use no scope for genuinely repository-wide changes.
Use test by default.
Use only test(core) for core-tier tests, generators, fuzzing, and fixtures, or test(extra) for extra-tier integration infrastructure.
Do not use component scopes with test.
A production change accompanied by tests keeps its production type and scope.
Outside the test type, core means ironrdp-core.
extra is valid only in test(extra).