Agent skill

Commit Scope

by Devolutions in Devolutions/devolutions-gateway

Select commit and PR scopes in the Devolutions Gateway repository.

Apache-2.0Auto-check passedDevelopment

Install Commit Scope

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

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

GitHub CLI
$ gh skill install Devolutions/devolutions-gateway 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/devolutions-gateway.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
161
Token cost
~864 tokens
SKILL.md length
393 words
Files
1
Skills in repo
19
Repo updated
First seen
Licence
Apache-2.0

At a glance

Select commit and PR scopes in the Devolutions Gateway repository.

  • Works in 4 steps: Inspect the diff and repository… → Read the ordered parsers in cliff.toml;… → For an included commit, trace… → …
  • Reviewing a Conventional Commit subject
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Especially for shared libraries

What it does

Commit Scope is an agent skill from Devolutions/devolutions-gateway. Select commit and PR scopes in the Devolutions Gateway repository. Use whenever composing or reviewing a Conventional Commit subject, especially for shared libraries, packaging, tests, documentation, CI, or changes spanning products.

Its SKILL.md is about 860 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. It works with Git. The repository describes itself as: A blazing fast relay server adaptable to different protocols and desired levels of traffic inspection. The licence is Apache-2.0.

When your agent uses it

  • Reviewing a Conventional Commit subject
  • Especially for shared libraries
  • Changes spanning products

Example prompts

  • “/commit-scope”

Workflow steps

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

  1. Inspect the diff and repository instructions.
  2. Read the ordered parsers in cliff.toml; the completed subject and footers determine whether git-cliff includes the commit.
  3. For an included commit, trace shared-code and packaging dependencies to every affected product. For Rust crates, inspect reverse…
  4. Add every applicable product scope

What it can do on your machine

Read from SKILL.md and the folder at commit 81a3141. 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 864 tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 393 words of instructions outside code blocks.

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

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/devolutions-gateway at commit 81a3141, republished under its Apache-2.0 licence (© Devolutions). 393 words, ~864 tokens.

Download SKILL.mdSave it as .claude/skills/commit-scope/SKILL.md (or your agent's skills folder).
name
commit-scope
description
Select commit and PR scopes in the Devolutions Gateway repository. Use whenever composing or reviewing a Conventional Commit subject, especially for shared libraries, packaging, tests, documentation, CI, or changes spanning products.

Devolutions Gateway commit scope

Choose scopes by affected deliverable, not file location or internal component.

  1. Inspect the diff and repository instructions.
  2. Read the ordered parsers in cliff.toml; the completed subject and footers determine whether git-cliff includes the commit.
  3. For an included commit, trace shared-code and packaging dependencies to every affected product. For Rust crates, inspect reverse dependencies. Count shipped normal dependencies; ignore dev-only use unless tests or developer behavior are the change.
  4. Add every applicable product scope:
ScopeArea
dgwDevolutions Gateway service, runtime, API, configuration, or product-specific tests/docs/build logic
installerDevolutions Gateway installers, packages, installation behavior, or installer-specific tests/docs/build logic
agentDevolutions Agent services, updater, runtime, or product-specific tests/docs/build logic
agent-installerDevolutions Agent installers, packages, installation behavior, or installer-specific tests/docs/build logic
jetsocatJetsocat runtime, packages, or product-specific tests/docs/build logic
webappAnything affecting the standalone Gateway web application

A shared component receives each product scope whose behavior changes. Merely bundling an updated runtime does not add installer or agent-installer; add those scopes only when installation or packaging behavior changes. Do not use internal component names such as jmux or pedm: JMUX changes commonly affect dgw,jetsocat; PEDM changes commonly affect agent and sometimes agent-installer.

For included commits, use only product scopes. Scopes containing openapi, npm, nuget, dotnet-*, or ts-* cause git-cliff to suppress the entry. The deps scope suppresses only exact chore(deps) and build(deps) subjects; do not use it with other included types or as part of a broader scope.

Show full SKILL.md (150 more words)Show less

Scopes are more flexible when git-cliff excludes the commit, whether by type, scope, or Changelog: ignore. Keep the semantic type: an npm package feature may use feat(npm): ... because the scope suppresses it. For chore, ci, style, refactor, and test, use a concise target when useful, such as openapi, deps, toolchain, package, agents, dependabot, miri, tokengen, or dotnet-utils; omit the scope if none helps. Prefer a precise current name over generic tools or dotnet. Use agents for agent instructions and reusable skills.

Use the established chore(release): prepare for <version> pattern when cutting a release.

For multiple products, separate scopes with commas and no spaces in this order: dgw,installer,agent,agent-installer,jetsocat,webapp.

Examples:

  • Shared code shipped by Gateway and Agent: fix(dgw,agent): ...
  • JMUX code shared by Gateway and Jetsocat: perf(dgw,jetsocat): ...
  • Standalone web application change: feat(webapp): ...
  • Gateway contract plus generated clients: feat(dgw): ...
  • Standalone npm package feature: feat(npm): ...
  • Generated clients only: chore(openapi): ...
  • Release preparation: chore(release): prepare for 2026.3.0

© 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/devolutions-gateway.

Open the folder on GitHubat commit 81a3141

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/devolutions-gateway161—~864Automated safety check: PassApache-2.0
React Router Release Notes Prepremix-run/react-router57k—~1.1kAutomated safety check: PassMIT
ToolJet Multi-Repo CommitToolJet/ToolJet41k—~1.3kAutomated safety check: PassAGPL-3.0
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
Verdaccio Pull Request Workflowverdaccio/verdaccio18k—~1.9kAutomated safety check: PassMIT

Similar skills

  • React Router Release Notes Prep

    remix-run/react-router

    Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.

    57k GitHub stars~1.1k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Commits changes across ToolJet's root repo and its server/ee and frontend/ee submodules, writing messages from the diffs and updating submodule pointers in order.

    41k GitHub stars~1.3k 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
  • 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
  • Commits changes in the Saleor codebase and works through pre-commit hook failures from ruff, mypy, the GraphQL schema check and the migrations check.

    23k GitHub stars~575 tokensUpdated yesterday
    DevelopmentAuto-check passed

More from Devolutions/devolutions-gateway

All 19 skills in this repo
  • Tessl Skill Linting

    Devolutions/devolutions-gateway

    Review, lint, create, edit, refine, optimize, compress, or validate any agent skill in this repository, including any SKILL.md.

    161 GitHub stars~740 tokensUpdated yesterday
    Auto-check passed
  • Build Agent Msi

    Devolutions/devolutions-gateway

    Build the Devolutions Agent Windows MSI installer locally. An agent skill from Devolutions/devolutions-gateway.

    161 GitHub stars~1.5k tokensUpdated yesterday
    Auto-check passed
  • Changelog To Jira

    Devolutions/devolutions-gateway

    Creates missing DGW Jira tickets from CHANGELOG.md entries and updates the file with the new ticket links.

    161 GitHub stars~2.7k tokensUpdated yesterday
    Auto-check passed
  • Commit And PR Conventions

    Devolutions/devolutions-gateway

    Follow the adopted commit and pull-request conventions. An agent skill from Devolutions/devolutions-gateway.

    161 GitHub stars~739 tokensUpdated yesterday
    Auto-check passed
  • Prepare Release

    Devolutions/devolutions-gateway

    Prepares a Devolutions Gateway / Devolutions Agent release commit: bumps the version, generates and inserts the changelog, creates Jira tickets, generates the ToolBox changelog, and produces the…

    161 GitHub stars~1.8k tokensUpdated yesterday
    Auto-check passed
  • Build Gateway Msi

    Devolutions/devolutions-gateway

    Build the Devolutions Gateway Windows MSI installer locally.

    161 GitHub stars~2.3k tokensUpdated yesterday
    Auto-check: warnings

Works with

Categories

Questions about Commit Scope

What does Commit Scope do?

Select commit and PR scopes in the Devolutions Gateway repository. Commit Scope is an agent skill from Devolutions/devolutions-gateway. Select commit and PR scopes in the Devolutions Gateway repository.

When should I use Commit Scope?

Commit Scope fits situations like: reviewing a Conventional Commit subject; especially for shared libraries; changes spanning products.

How do I install Commit Scope in Claude Code?

Run `npx skills add Devolutions/devolutions-gateway --skill commit-scope -a claude-code`. Or copy the skill folder (.agents/skills/commit-scope in Devolutions/devolutions-gateway) 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/devolutions-gateway --skill commit-scope -a codex`. Or copy the skill folder (.agents/skills/commit-scope in Devolutions/devolutions-gateway) 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/devolutions-gateway --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 864 tokens (SKILL.md is roughly 3.5k 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: React Router Release Notes Prep (remix-run/react-router, 57k stars), ToolJet Multi-Repo Commit (ToolJet/ToolJet, 41k stars), Git Workflow and Versioning (addyosmani/agent-skills, 102k stars) and React Router Pull Request Creator (remix-run/react-router, 57k 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/devolutions-gateway, which has 161 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 6, 2026.

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