How do I install the Change Type skill?

Run npx skillmds@latest add tomevault-io/change-type in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Change Type safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Change Type?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Change Type free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Change Type?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Change Type by tomevault-io — Agent Skill

Name: Change Type
Author: tomevault-io

Change Type

Classify a change set as behavior vs structure, then recommend the correct PR label (change:behavior or change:structure) and the appropriate local/CI checks. Use when the user asks whether a change is a behavior change or a structure change, what label to apply, or how CI/testing should differ based on change type. Use when this capability is needed.

tomevault-io 9afe86d 2 files · 3.1 KB Updated Sep 17, 2026

File contents

change-type

Classify the current work as either a Behavior Change or a Structure Change, then recommend:

PR label (change:behavior or change:structure)
local verification commands
what CI is expected to run

Trigger Examples

"Is this a Behavior Change or a Structure Change?"
"Which label should I apply: change:behavior or change:structure?"
"Can we skip build/audit for this refactor?"
"How should CI differ for behavior vs structure changes?"

Execution Flow

1. Inspect the change set

Identify changed files/paths
Identify intent (behavior vs refactor)
If any uncertainty remains, default to Behavior Change

2. Classify

Behavior Change if the change is externally observable (site output, infra behavior, CI behavior).

Structure Change if the change is intended to preserve external behavior while improving maintainability.

3. Apply repo-specific heuristics

Treat as Behavior Change if the diff touches any of:

app/src/content/docs/** (published content)
app/src/** (components/layouts/pages)
app/public/** or app/src/assets/** (published assets)
app/astro.config.mjs, app/nginx/**, app/Dockerfile
infra/src/** (Pulumi stacks)
.github/workflows/** (CI behavior)

Treat as Structure Change candidates if the diff touches only:

README.md, AGENTS.md, CLAUDE.md
.github/release.yml
other non-deployed repository documentation files

4. Recommend label + checks

Return:

Change type: behavior or structure
PR label: change:behavior or change:structure
Local checks
CI expectations

Recommended checks

App

Behavior:
- cd app && npm run lint && npm run build
Structure:
- cd app && npm run lint

Infra

Always (local static checks):
- cd infra && npm run build && npm run lint && npm run typecheck
Never run pulumi preview/pulumi up locally (CI only).

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: change-typedescription: Classify a change set as behavior vs structure, then recommend the correct PR label (change:behavior or change:structure) and the appropriate local/CI checks. Use when the user asks whether a change is a behavior change or a structure change, what label to apply, or how CI/testing should differ based on change type. Use when this capability is needed.---# change-typeClassify the current work as either a **Behavior Change** or a **Structure Change**, then recommend:- PR label (`change:behavior` or `change:structure`)- local verification commands- what CI is expected to run## Trigger Examples- "Is this a Behavior Change or a Structure Change?"- "Which label should I apply: change:behavior or change:structure?"- "Can we skip build/audit for this refactor?"- "How should CI differ for behavior vs structure changes?"## Execution Flow### 1. Inspect the change set- Identify changed files/paths- Identify intent (behavior vs refactor)- If any uncertainty remains, default to **Behavior Change**### 2. Classify**Behavior Change** if the change is externally observable (site output, infra behavior, CI behavior).**Structure Change** if the change is intended to preserve external behavior while improving maintainability.### 3. Apply repo-specific heuristicsTreat as **Behavior Change** if the diff touches any of:- `app/src/content/docs/**` (published content)- `app/src/**` (components/layouts/pages)- `app/public/**` or `app/src/assets/**` (published assets)- `app/astro.config.mjs`, `app/nginx/**`, `app/Dockerfile`- `infra/src/**` (Pulumi stacks)- `.github/workflows/**` (CI behavior)Treat as **Structure Change** candidates if the diff touches only:- `README.md`, `AGENTS.md`, `CLAUDE.md`- `.github/release.yml`- other non-deployed repository documentation files### 4. Recommend label + checksReturn:1. **Change type**: `behavior` or `structure`2. **PR label**: `change:behavior` or `change:structure`3. **Local checks**4. **CI expectations**## Recommended checks### App- Behavior: - `cd app && npm run lint && npm run build`- Structure: - `cd app && npm run lint`### Infra- Always (local static checks): - `cd infra && npm run build && npm run lint && npm run typecheck`- Never run `pulumi preview`/`pulumi up` locally (CI only).---> Converted and distributed by [TomeVault](https://tomevault.io/claim/nozomi-koborinai) — claim your Tome and manage your conversions.

Frequently asked questions