commit-msg

What it does and when to use it

Generate a conventional commit message for staged NG-ZORRO changes. Use when asked for a commit message, a git commit title, or a summary of staged changes.

How it works

SKILL.md has no level-two headings · 17 lines, 186 words

---
name: commit-msg
description: Generate a conventional commit message for staged NG-ZORRO changes. Use when asked for a commit message, a git commit title, or a summary of staged changes.
---

# NG-ZORRO Commit Message

Generate a commit message from the change that will actually be committed. Inspect `git status --short`, `git diff --cached --stat`, `git diff --cached`, and recent commit subjects before drafting it. If nothing is staged, say so; include unstaged changes only when the user asks.

Follow `commitlint.config.js` and `CONTRIBUTING.md` as the authoritative format:

- use `type(scope): subject`, with an optional scope;
- choose one of `build`, `chore`, `ci`, `docs`, `feat`, `fix`, `perf`, `refactor`, `release`, `revert`, `style`, or `test`;
- use `module:<component>` for a component scope, or one of `showcase`, `release`, `packaging`, `changelog`, and `schematics` where applicable;
- write an imperative, lower-case subject without ending punctuation, keeping each line within 100 characters; and
- add a body or footer only when the user asks, the change needs motivation, or it carries a breaking-change or issue-closing reference.

Summarize the common intent of the entire staged set rather than listing files or copying the last commit. If the staged set has unrelated changes, point out the split before recommending a deliberately broad subject.

Return only the proposed subject by default. Explain the choice only when requested.

Versions

The database has no other skills named commit-msg.

Database snapshot: 13.11.2026 · package version c551aeb57857 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

• 96commit-message-generator
  Generate a clear, concise conventional commit message from staged code changes. Use when writing a commit message.
• 100conventional-commit
  Write a Conventional Commits message for the staged changes. Use when the user asks to commit, write a commit message, or summarize staged changes for git.
• 100commit
  Analyze staged changes and write a conventional commit message. Use when staged changes are ready to commit or a message needs wording.
• 96conventional-commit
  Write a Conventional Commits v1.0.0 message for the current changes. Use when writing or checking a commit message or PR title.
• 100at-commit
  Generate a Conventional Commits message from staged changes and wait for confirmation before committing. Use when the user asks to commit or generate a commit message.
• 100create-commit-message
  Generate a Conventional Commit message from staged git changes when the user asks to write a commit message, create a commit, or format a commit