AgentSkillsCN

conventional-commits

遵循Conventional Commits规范撰写提交信息。在提交更改、编写提交信息，或审查提交信息格式时使用。

SKILL.md
--- frontmatter
name: conventional-commits
description: Write commit messages following the Conventional Commits specification. Use when committing changes, writing commit messages, or reviewing commit message format.
metadata:
  version: '1.0'

Conventional Commits

All commits in this project must follow the Conventional Commits specification.

Format

code
<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Types

TypeWhen to use
featA new feature or capability
fixA bug fix
docsDocumentation changes only
choreMaintenance tasks, dependency updates, config changes
refactorCode restructuring without behavior change
testAdding or updating tests
perfPerformance improvements
ciCI/CD pipeline changes
styleFormatting changes (Prettier, whitespace)
buildBuild system or dependency changes

Rules

  • •Description: Imperative mood, lowercase, no period at end. Max 72 characters.
  • •Scope: Optional. Use module/feature name (e.g., feat(import):, fix(charts):).
  • •Body: Explain what and why, not how. Wrap at 72 characters.
  • •Breaking changes: Add ! after type/scope (e.g., feat!:) and include BREAKING CHANGE: footer.

Examples

code
feat(import): add EDF file parsing for ResMed AirSense 11

fix(charts): correct AHI rolling average calculation for gaps in data

docs: update glossary with flow limitation terminology

chore: upgrade vitest to 3.x

refactor(storage): extract chunk indexing into separate module

test(stats): add edge case tests for Kaplan-Meier with censored data

perf(viz): implement LTTB downsampling for time-series rendering

ci: add bundle size check to PR workflow