How does the skill determine the change type?

The skill analyzes specific file paths and the developer's intent; for example, changes to source code or config files are classified as 'behavior,' while documentation updates are often 'structure.'

What is the difference between a Behavior and Structure change?

A Behavior change affects observable output or infrastructure behavior (like a new feature or bug fix), while a Structure change is a refactor intended to preserve existing behavior while improving code maintainability.

Does this skill work with infrastructure-as-code?

Absolutely. It includes specific heuristics for infrastructure files (like Pulumi) to ensure infrastructure changes are properly flagged for CI verification.

Can this skill help optimize my CI/CD pipeline?

Yes, by identifying structure-only changes, the skill can recommend skipping resource-intensive build or audit steps that are unnecessary for non-functional updates.

Change Type Classifier

Name: Change Type Classifier
Author: nozomi-koborinai

bynozomi-koborinai

•

デプロイメントとDevOps

Classifies code modifications as behavior or structure changes to automate PR labeling and CI/CD verification workflows.

The Change Type skill streamlines the development lifecycle by analyzing code diffs and intent to distinguish between observable behavior changes and internal structural refactors. By inspecting file paths—such as application source, infrastructure code, or documentation—it provides precise recommendations for PR labels, local verification commands, and CI expectations. This ensures that developers apply the correct testing rigors to functional updates while optimizing workflows for maintenance-only changes, ultimately maintaining repository health and deployment clarity.

主な機能

01Repo-specific heuristic analysis for Astro and Pulumi projects

02Tailored local verification command suggestions to save time

03Context-aware PR label recommendations (change:behavior vs change:structure)

04Automated classification of functional vs. structural code changes

056 GitHub stars

06CI/CD execution guidance based on the impact of the change set

ユースケース

01Determining if a code change requires a full production build or just a linting check.

02Automating the labeling of Pull Requests for cleaner changelogs and release notes.

03Deciding whether to trigger infrastructure previews or application deployments based on file diffs.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add nozomi-koborinai/koborin-ai change-type

For use in Claude.ai and ChatGPT

Download Skill