New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Commit Scope

by Devolutions in Devolutions/IronRDP

Derive and validate the canonical scope for IronRDP Conventional Commit and pull-request titles.

Apache-2.0Auto-check passedDevelopment

Install Commit Scope

skills CLI
$ npx skills add Devolutions/IronRDP --skill commit-scope -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Devolutions/IronRDP commit-scope --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Devolutions/IronRDP.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/commit-scope .claude/skills/commit-scope && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
commit-scope
GitHub stars
3.2k
Token cost
~854 tokens
SKILL.md length
338 words
Files
1
Skills in repo
8
Repo updated
First seen
Licence
Apache-2.0

At a glance

Derive and validate the canonical scope for IronRDP Conventional Commit and pull-request titles.

  • Works in 7 steps: Scope the contract or behavior being… → When another component owns the change,… → Prefer the component defining the… → …
  • Checking a commit
  • SKILL.md covers Canonical scopes, Selection rules and Tests
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Commit Scope is an agent skill from Devolutions/IronRDP. 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.

Its SKILL.md is about 850 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Commit messages and Pull requests. It works with Rust. The repository describes itself as: Rust implementation of the Microsoft Remote Desktop Protocol (RDP). The licence is Apache-2.0.

When your agent uses it

  • Checking a commit
  • Especially when several crates
  • Product surfaces intersect

Example prompts

  • “/commit-scope”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Scope the contract or behavior being changed, not every touched path.
  2. When another component owns the change, ignore supporting tests, documentation, generated files, manifests, lockfiles, and call-site…
  3. Prefer the component defining the behavior over components that merely consume it.
  4. Split independent contract changes when practical.
  5. Omit the scope when an indivisible change has multiple equal owners.
  6. Never combine scopes or invent a catch-all scope; explain secondary effects in the body.
  7. Add a new scope only for a distinct contract that does not fit an existing aggregate.

What it can do on your machine

Read from SKILL.md and the folder at commit 2c08bda. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Commit Scope loads about 854 tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 338 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~63
When it runs · the whole SKILL.md, loaded when a task matches
~854

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Devolutions/IronRDP at commit 2c08bda, republished under its Apache-2.0 licence (© Devolutions). 338 words, ~854 tokens.

Download SKILL.mdSave it as .claude/skills/commit-scope/SKILL.md (or your agent's skills folder).
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.

Commit scope

Choose at most one optional scope for <type>[optional scope][!]: <description>.

Canonical scopes

text
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.

Selection rules

  1. Scope the contract or behavior being changed, not every touched path.
  2. When another component owns the change, ignore supporting tests, documentation, generated files, manifests, lockfiles, and call-site adaptations.
  3. Prefer the component defining the behavior over components that merely consume it.
  4. Split independent contract changes when practical.
  5. Omit the scope when an indivisible change has multiple equal owners.
  6. Never combine scopes or invent a catch-all scope; explain secondary effects in the body.
  7. Add a new scope only for a distinct contract that does not fit an existing aggregate.

Use the component scope with any applicable type:

text
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.

Tests

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).

© Devolutions, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/commit-scope of Devolutions/IronRDP.

Open the folder on GitHubat commit 2c08bda

Compare with similar skills

Commit Scope next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Commit Scope compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Commit Scope this skillDevolutions/IronRDP3.2k—~854Automated safety check: PassApache-2.0
Rocketmq Rust PR Submittermxsm/rocketmq-rust1.5k—~1.4kAutomated safety check: PassApache-2.0
PRboundless-xyz/boundless193—~1.2kAutomated safety check: PassApache-2.0
PR Finalize Reviewmicrosoft/garnet12k—~3.1kAutomated safety check: PassMIT
Git Workflow and Versioningaddyosmani/agent-skills102k2 repos~3.5kAutomated safety check: NotesMIT
React Router Pull Request Creatorremix-run/react-router57k—~2.5kAutomated safety check: PassMIT

Similar skills

  • Rocketmq Rust PR Submitter

    mxsm/rocketmq-rust

    A skill your agent uses when the user asks to prepare, submit, publish, or optimize a pull request for the rocketmq-rust project, especially when the PR title or commit message must follow the [ISSUE

    1.5k GitHub stars~1.4k tokensUpdated today
    DevelopmentAuto-check passed

  • PR

    boundless-xyz/boundless

    Create or update a pull request for the current git changes.

    193 GitHub stars~1.2k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

  • PR Finalize Review

    microsoft/garnet

    Official

    Checks that a pull request's title and description match its implementation and reviews the code for Garnet best practices, reporting findings without posting them.

    12k GitHub stars~3.1k tokensUpdated today
    DevelopmentAuto-check passed

  • Git Workflow and Versioning

    addyosmani/agent-skills

    Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.

    102k GitHub starsUsed in 2 repos~3.5k tokens
    DevelopmentAuto-check: notes

  • React Router Pull Request Creator

    remix-run/react-router

    Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.

    57k GitHub stars~2.5k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Verdaccio Pull Request Workflow

    verdaccio/verdaccio

    Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.

    18k GitHub stars~1.9k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from Devolutions/IronRDP

All 8 skills in this repo

  • Ironrdp Activex Mstsc Testing

    Devolutions/IronRDP

    Test IronRDP ActiveX in the real mstsc.exe child launched by MsRdpEx, including the native credential bridge, shell behavior, resize handling, clipboard startup, and bounded UI stress.

    3.2k GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed

  • Release Prep

    Devolutions/IronRDP

    Reviews and finalizes a release-plz "chore(release): prepare for publishing" PR for the IronRDP workspace.

    3.2k GitHub stars~2.2k tokensUpdated yesterday
    Auto-check passed

  • New Crate

    Devolutions/IronRDP

    Create and integrate a new Rust crate in the IronRDP workspace.

    3.2k GitHub stars~236 tokensUpdated yesterday
    Auto-check passed

  • Public Dependency

    Devolutions/IronRDP

    Add or change Rust crate dependencies while preserving IronRDP's public-dependency markers.

    3.2k GitHub stars~265 tokensUpdated yesterday
    Auto-check passed

  • Code Review

    Devolutions/IronRDP

    Review IronRDP pull requests and diffs using focused protocol, compression, prose, and skeptical passes.

    3.2k GitHub stars~539 tokensUpdated yesterday
    Auto-check passed

  • Crate Readme Writer

    Devolutions/IronRDP

    Write or substantially revise a Rust crate's README.md as a concise, user-facing design document.

    3.2k GitHub stars~455 tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Commit Scope

What does Commit Scope do?

Derive and validate the canonical scope for IronRDP Conventional Commit and pull-request titles. Commit Scope is an agent skill from Devolutions/IronRDP. Derive and validate the canonical scope for IronRDP Conventional Commit and pull-request titles.

When should I use Commit Scope?

Commit Scope fits situations like: checking a commit; especially when several crates; product surfaces intersect.

How do I install Commit Scope in Claude Code?

Run `npx skills add Devolutions/IronRDP --skill commit-scope -a claude-code`. Or copy the skill folder (.agents/skills/commit-scope in Devolutions/IronRDP) into .claude/skills/commit-scope in your project. Claude Code loads it when a task matches its description.

How do I install Commit Scope in Codex?

Run `npx skills add Devolutions/IronRDP --skill commit-scope -a codex`. Or copy the skill folder (.agents/skills/commit-scope in Devolutions/IronRDP) into .agents/skills/commit-scope in your project. Codex loads it when a task matches its description.

Can I use Commit Scope in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Devolutions/IronRDP --skill commit-scope -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/commit-scope, .gemini/skills/commit-scope, .github/skills/commit-scope and .opencode/skills/commit-scope in your project.

What does Commit Scope need to run?

SKILL.md names no scripts, command-line tools or credentials: Commit Scope is instructions for the agent only.

Does Commit Scope access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Commit Scope safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Commit Scope use?

Commit Scope is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Commit Scope use?

About 854 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Commit Scope?

Skills that share tags, products or a category with Commit Scope: Rocketmq Rust PR Submitter (mxsm/rocketmq-rust, 1.5k stars), PR (boundless-xyz/boundless, 193 stars), PR Finalize Review (microsoft/garnet, 12k stars) and Git Workflow and Versioning (addyosmani/agent-skills, 102k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Commit Scope?

Devolutions (a GitHub organization) maintains it in Devolutions/IronRDP, which has 3,213 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 6, 2026.

Source: Devolutions/IronRDP on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.