commit
Use when creating git commits - enforces conventional commit format with correct type prefixes for release-triggering vs non-release changes
소스 정보
- 저장소
- sanity-io/cli
- 최근 소스 활동
- 2026년 4월 10일 15:17
- 감지된 SKILL.md 언어
- 영어
- 스타
- 11
- 포크
- 5
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- name
- commit
- description
- Use when creating git commits - enforces conventional commit format with correct type prefixes for release-triggering vs non-release changes
# Conventional Commits
## Format
```
<type>[(scope)]: <description>
```
- Type and description are **lowercase**
- No period at end
- Imperative mood: "add" not "added"
- Under 100 characters
- Scope is optional, use package or feature area (e.g., `init`, `deploy`, `cli-core`, `deps`, `ci`)
## Release-Triggering Types
These types generate changesets and trigger npm releases:
| Type | Bump | Use for |
| ---------------- | --------- | ---------------------------------------------------------- |
| `feat` | minor | New commands, flags, features |
| `fix` | patch | Bug fixes, crash fixes, incorrect output |
| `perf` | patch | Performance improvements |
| `revert` | patch | Reverting previous changes |
| `feat!` / `fix!` | **major** | Breaking changes (removed commands, changed flag behavior) |
## Non-Release Types
These do **not** trigger releases or changesets:
| Type | Use for |
| ---------- | ------------------------------------------ |
| `chore` | Tooling, build config, dependency updates |
| `refactor` | Code restructuring without behavior change |
| `test` | Adding or updating tests |
| `docs` | Documentation only |
| `style` | Formatting, whitespace |
| `build` | Build system changes |
| `ci` | CI/CD pipeline changes |
## Decision Guide
- Does it change what users experience? Use `feat` or `fix`
- Does it break existing behavior? Add `!` suffix (e.g., `feat!`)
- Is it internal-only with no user impact? Use `chore`, `refactor`, `test`, etc.
- Dependency updates? Use `chore(deps)` unless fixing a user-facing bug, then `fix(deps)`
## Examples from This Repo
```
feat: auto-generate changesets from PR descriptions
feat(embeddings): add projection validation using groq-js
feat(cli): inject __SANITY_STAGING__ global in staging builds
fix(init): strip filename before counting nested folders in import path
fix(deploy): stop spinner before returning from app lookup
refactor(cli-core): replace oclif ux.colorize with node:util styleText
refactor(cli): migrate from zod to zod/mini for smaller bundle size
chore: skip auto-generated changeset when one already exists
chore(ci): use squiggler-app bot as changeset commit author
chore(deps): update swc-tooling
```
GitHub에서 보기