Mas Code Standards
AUTO-MAS-Project/AUTO-MAS
A skill your agent uses when implementing, fixing, refactoring, or reviewing non-generated AUTO-MAS code, or when preparing code-style guidance, comments, docstrings, version notes, or Conventional…
Decide the correct change kind and semantically align branch names, PR titles, commit prefixes, and PR template types.
Install Change Kind Naming
$ npx skills add shm11C3/HardwareVisualizer --skill change-kind-naming -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install shm11C3/HardwareVisualizer change-kind-naming --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/shm11C3/HardwareVisualizer.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/change-kind-naming .claude/skills/change-kind-naming && rm -rf skills-srcUse ~/.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/
Install the "change-kind-naming" agent skill from https://github.com/shm11C3/HardwareVisualizer/tree/develop/.agents/skills/change-kind-naming into .claude/skills/change-kind-naming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "change-kind-naming", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/shm11C3/HardwareVisualizer/tree/develop/.agents/skills/change-kind-namingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add shm11C3/HardwareVisualizer --skill change-kind-naming -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install shm11C3/HardwareVisualizer change-kind-naming --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shm11C3/HardwareVisualizer.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/change-kind-naming .agents/skills/change-kind-naming && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "change-kind-naming" agent skill from https://github.com/shm11C3/HardwareVisualizer/tree/develop/.agents/skills/change-kind-naming into .agents/skills/change-kind-naming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "change-kind-naming", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add shm11C3/HardwareVisualizer --skill change-kind-naming -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install shm11C3/HardwareVisualizer change-kind-naming --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shm11C3/HardwareVisualizer.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/change-kind-naming .cursor/skills/change-kind-naming && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "change-kind-naming" agent skill from https://github.com/shm11C3/HardwareVisualizer/tree/develop/.agents/skills/change-kind-naming into .cursor/skills/change-kind-naming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "change-kind-naming", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/shm11C3/HardwareVisualizer.git --path .agents/skills/change-kind-naming--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add shm11C3/HardwareVisualizer --skill change-kind-naming -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install shm11C3/HardwareVisualizer change-kind-naming --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shm11C3/HardwareVisualizer.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/change-kind-naming .gemini/skills/change-kind-naming && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "change-kind-naming" agent skill from https://github.com/shm11C3/HardwareVisualizer/tree/develop/.agents/skills/change-kind-naming into .gemini/skills/change-kind-naming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "change-kind-naming", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install shm11C3/HardwareVisualizer change-kind-namingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add shm11C3/HardwareVisualizer --skill change-kind-naming -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/shm11C3/HardwareVisualizer.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/change-kind-naming .github/skills/change-kind-naming && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "change-kind-naming" agent skill from https://github.com/shm11C3/HardwareVisualizer/tree/develop/.agents/skills/change-kind-naming into .github/skills/change-kind-naming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "change-kind-naming", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add shm11C3/HardwareVisualizer --skill change-kind-naming -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install shm11C3/HardwareVisualizer change-kind-naming --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shm11C3/HardwareVisualizer.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/change-kind-naming .opencode/skills/change-kind-naming && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "change-kind-naming" agent skill from https://github.com/shm11C3/HardwareVisualizer/tree/develop/.agents/skills/change-kind-naming into .opencode/skills/change-kind-naming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "change-kind-naming", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
change-kind-naming- GitHub stars
- 183
- Token cost
- ~994 tokens
- SKILL.md length
- 513 words
- Files
- 1
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
Decide the correct change kind and semantically align branch names, PR titles, commit prefixes, and PR template types.
- Choosing Conventional Commit
- SKILL.md covers Quick Start, Classification Rules, Tie-Breakers and Naming Alignment, plus 2 more sections
- Calls git and gh
- Branch prefixes for fix
What it does
Change Kind Naming is an agent skill from shm11C3/HardwareVisualizer. Decide the correct change kind and semantically align branch names, PR titles, commit prefixes, and PR template types. Use when choosing Conventional Commit or branch prefixes for fix, refactor, chore, docs, feat, perf, test, or CI changes.
Its SKILL.md is about 990 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 Refactoring. The repository describes itself as: A cross-platform hardware monitor with real-time metrics, local history, and customizable dashboards. The licence is GPL-3.0.
When your agent uses it
- Choosing Conventional Commit
- Branch prefixes for fix
Example prompts
- “/change-kind-naming”
What it can do on your machine
Read from SKILL.md and the folder at commit b23baca. 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
Shell commands in SKILL.md call:
gitgh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.
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
Change Kind Naming loads about 994 tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 513 words of instructions outside code blocks.
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 shm11C3/HardwareVisualizer at commit b23baca, republished under its GPL-3.0 licence (© shm11C3). 513 words, ~994 tokens.
Download SKILL.mdSave it as
.claude/skills/change-kind-naming/SKILL.md (or your agent's skills folder).- name
- change-kind-naming
- description
- Decide the correct change kind and semantically align branch names, PR titles, commit prefixes, and PR template types. Use when choosing Conventional Commit or branch prefixes for fix, refactor, chore, docs, feat, perf, test, or CI changes.
Change Kind Naming
Quick Start
Before committing, pushing, or opening a PR, classify the actual change type and make these four surfaces agree semantically under the repository's allowed branch prefixes:
- commit subject prefix
- PR title prefix
- branch prefix
- PR template "Type of Change"
If they disagree, stop and fix the naming before publishing.
Classification Rules
Use fix only when the change corrects externally observable broken behavior, user-facing wrong output, a failing workflow, data loss, security exposure, or a regression.
Use refactor when the change preserves behavior but improves internal structure, terminology, names, boundaries, generated bindings, or code organization.
Use feat when the change adds a new user-visible capability or supported workflow.
Use docs when the shipped code behavior does not change and the diff is documentation-only.
Use test when the diff only adds or changes tests.
Use ci when the diff only changes CI/CD automation.
Use chore for maintenance that is not product behavior, architecture, docs, tests, or CI.
Tie-Breakers
Prefer fix over refactor when the old state caused a real user or integration failure.
Prefer refactor over fix when the old state was confusing, inconsistent, or poorly named but still worked.
Prefer feat over refactor when users can now do something they could not do before.
Prefer docs over refactor when only docs changed, even if the docs clarify architecture.
Prefer the highest-impact type when one PR intentionally mixes types. If the mixed change is accidental, split it.
Show full SKILL.md (274 more words)Show less
Naming Alignment
Use branch prefixes that match the final classification:
feat/...feature/...fix/...docs/...perf/...refactor/...chore/...
This repository's CI does not allow test/... or ci/... branches. For a
test-only or CI-only change, use a chore/... branch while keeping the more
precise test: or ci: Conventional Commit and PR title. Select Other in the
PR template. Alignment is semantic here; it does not require the branch and
commit prefix strings to be identical.
Do not use:
test/...ci/...codex/...claude/...
In repositories that define branch rules, such as this repository's
CONTRIBUTING.md, the repository rule wins over generic agent defaults.
Never use tool-dependent prefixes such as codex/... or claude/...
when the project requires change-kind branch prefixes.
Use the same Conventional Commit prefix in the commit subject and PR title:
refactor: rename hardware archive retention settingIn the PR template, check the matching Type of Change. Do not leave Bug fix checked for a refactor: PR.
Pre-Publish Checklist
Run this before git commit, git push, or gh pr create:
- Does the change fix broken behavior? If no, avoid
fix. - Does the change preserve behavior while renaming or reorganizing? Use
refactor. - Do branch, commit, PR title, and PR template all agree?
- Does the PR body explain compatibility separately from behavior?
- If the branch prefix is wrong and the PR is already open, prefer renaming before review starts. If renaming would close or disrupt the PR, weigh whether updating title/body/commit is enough.
Example
Renaming refreshIntervalDays to retentionDays while preserving compatibility is refactor, not fix, because the old setting worked but used misleading terminology.
Use:
- branch:
refactor/hardware-archive-retention-naming - commit:
refactor: rename hardware archive retention setting - PR title:
refactor: rename hardware archive retention setting - PR type:
Refactoring
© shm11C3, GPL-3.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/change-kind-naming of shm11C3/HardwareVisualizer.
Open the folder on GitHubat commit b23baca
Compare with similar skills
Change Kind Naming 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Change Kind Naming this skillshm11C3/HardwareVisualizer | 183 | — | ~994 | Automated safety check: Pass | GPL-3.0 | |
| Mas Code StandardsAUTO-MAS-Project/AUTO-MAS | 711 | — | ~2.5k | Automated safety check: Pass | AGPL-3.0 | |
| Adk Reviewgoogle/adk-python | 22k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Conventional CommitterCaoMeiYouRen/caomei-auth | 220 | — | ~309 | Automated safety check: Pass | MIT | |
| Commit Smartdavila7/claude-code-templates | 33k | — | ~821 | Automated safety check: Pass | MIT | |
| Checkpointcodewithmukesh/dotnet-claude-kit | 756 | — | ~817 | Automated safety check: Notes | MIT |
Similar skills
- Official
Adk Review
google/adk-python
Reviews the uncommitted changes in an adk-python working tree and reports correctness, design, public-API stability, test, sample and documentation gaps as a prioritized findings report, fixing them…
Conventional Committer
CaoMeiYouRen/caomei-auth
需要生成 Conventional Commit 提交消息并执行单次提交时使用。适用于 feat、fix、docs、refactor、test、build、ci、chore 等常规提交场景。先检查质量门，再分析 diff，再生成符合 commitlint 预期的消息。
Commit Smart
davila7/claude-code-templates
Analyze staged/unstaged changes and create semantic conventional commits with context about WHY, not just WHAT.
Checkpoint
codewithmukesh/dotnet-claude-kit
Mid-session save point: create a descriptive git commit and a brief handoff note, then keep working.
Guidelines
akash-network/node
Behavioral guidelines to reduce common LLM coding mistakes. An agent skill from akash-network/node.
More from shm11C3/HardwareVisualizer
Capture Project Learning
shm11C3/HardwareVisualizer
Turn a HardwareVisualizer maintainer correction, repeated failure, surprising invariant, or costly investigation into an evidence-backed learning record and the right durable guardrail.
Gh AI Review Triage
shm11C3/HardwareVisualizer
Triage and optionally address AI-generated GitHub PR review feedback from Copilot, CodeRabbit, or similar bots.
Deliver Pull Request
shm11C3/HardwareVisualizer
Deliver a focused HardwareVisualizer change as a pull request, then address its CI and review feedback to completion.
Hardwarevisualizer Design Review
shm11C3/HardwareVisualizer
Review or shape HardwareVisualizer product and architecture changes against the maintainer's design principles.
Verify Identity Contracts
shm11C3/HardwareVisualizer
Verify the id/key contract between backend producers and frontend consumers before implementing any change that joins, selects, persists, or attributes entities keyed by backend-produced ids (GPUs…
Related
Categories
Questions about Change Kind Naming
What does Change Kind Naming do?
Decide the correct change kind and semantically align branch names, PR titles, commit prefixes, and PR template types. Change Kind Naming is an agent skill from shm11C3/HardwareVisualizer. Decide the correct change kind and semantically align branch names, PR titles, commit prefixes, and PR template types.
When should I use Change Kind Naming?
Change Kind Naming fits situations like: choosing Conventional Commit; branch prefixes for fix.
How do I install Change Kind Naming in Claude Code?
Run `npx skills add shm11C3/HardwareVisualizer --skill change-kind-naming -a claude-code`. Or copy the skill folder (.agents/skills/change-kind-naming in shm11C3/HardwareVisualizer) into .claude/skills/change-kind-naming in your project. Claude Code loads it when a task matches its description.
How do I install Change Kind Naming in Codex?
Run `npx skills add shm11C3/HardwareVisualizer --skill change-kind-naming -a codex`. Or copy the skill folder (.agents/skills/change-kind-naming in shm11C3/HardwareVisualizer) into .agents/skills/change-kind-naming in your project. Codex loads it when a task matches its description.
Can I use Change Kind Naming 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 shm11C3/HardwareVisualizer --skill change-kind-naming -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/change-kind-naming, .gemini/skills/change-kind-naming, .github/skills/change-kind-naming and .opencode/skills/change-kind-naming in your project.
What does Change Kind Naming need to run?
Going by SKILL.md and its folder, Change Kind Naming needs the command-line tools its instructions call (git and gh).
Does Change Kind Naming access the network?
SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Change Kind Naming 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 Change Kind Naming use?
Change Kind Naming is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Change Kind Naming use?
About 994 tokens (SKILL.md is roughly 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 Change Kind Naming?
Skills that share tags, products or a category with Change Kind Naming: Mas Code Standards (AUTO-MAS-Project/AUTO-MAS, 711 stars), Adk Review (google/adk-python, 22k stars), Conventional Committer (CaoMeiYouRen/caomei-auth, 220 stars) and Commit Smart (davila7/claude-code-templates, 33k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Change Kind Naming?
shm11C3 (a GitHub user) maintains it in shm11C3/HardwareVisualizer, which has 183 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 11, 2026.
Source: shm11C3/HardwareVisualizer on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.