一键在 Manus 中运行任何 Skill

开始使用

commit-message

星标2

分支0

更新时间2026年1月14日 14:18

Generate conventional commit messages by analyzing repository changes following conventionalcommits.org specification

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

nicanac

nicanac/vibe-architect-central

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Commit Message Generator Skill

Generate conventional commit messages by analyzing repository changes following the Conventional Commits specification.

When to use this skill

Use this when you need to generate a commit message for staged or unstaged changes.
This is helpful for ensuring commit messages are standardized, descriptive, and follow best practices.
Triggered by user requests like:
- "Generate a commit message"
- "Create a commit for my changes"
- "What should my commit message be?"
- "Commit"

How to use it

Analyze Changes: Examine staged (git diff --cached) and unstaged (git diff) changes to understand the context.

Determine Commit Type: Select the appropriate type from the table below:

Type	Description
`feat`	New feature
`fix`	Bug fix
`docs`	Documentation only changes
`style`	Formatting, whitespace changes
`refactor`	Code restructuring without behavior change
`perf`	Performance improvement
`test`	Adding or correcting tests
`build`	Build system or dependency changes
`ci`	CI configuration changes
`chore`	Maintenance tasks
`revert`	Revert previous commit

Identify Scope: (Optional) Specify the affected codebase area (e.g., auth, api, ui).
Draft Message:
- Subject: Imperative mood, lowercase, no period (e.g., feat(auth): add login).
- Body: (Optional) Explain "what" and "why".
- Footer: (Optional) Breaking changes or issue references.

Output Format: Present the message in a code block, followed by the git command.

<type>(<scope>): <short description>

<optional body>

<optional footer>

Git Source:

git add . && git commit -m "<type>(<scope>): <description>" -m "<body>"

同仓库更多 Skills

同仓库

agent-browser

nicanac/vibe-architect-central

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

2026-01-192

antigravity-memory

nicanac/vibe-architect-central

Create and optimize MEMORY.md memory files or .agent/rules/ modular rules for Antigravity projects. Comprehensive guidance on file hierarchy, content structure, path-scoped rules, best practices, and anti-patterns. Use when working with MEMORY.md files, .agent/rules directories, setting up new projects, or improving Antigravity's context awareness.

2026-01-162

code-review-skill

nicanac/vibe-architect-central

Comprehensive code review following OWASP, SOLID, and best practices

2026-01-162

create-slash-commands

nicanac/vibe-architect-central

Expert guidance for creating Antigravity slash commands. Use when working with slash commands, creating custom commands, understanding command structure, or learning YAML configuration.

2026-01-162

create-subagents

nicanac/vibe-architect-central

Expert guidance for creating, building, and using Antigravity subagents and the Task tool. Use when working with subagents, setting up agent configurations, understanding how agents work, or using the Task tool to launch specialized agents.

2026-01-162

create-workflow

nicanac/vibe-architect-central

Expert guidance for creating Antigravity Workflows. Use when creating new workflows, understanding workflow structure, or learning YAML configuration.

2026-01-162

name	commit-message
description	Generate conventional commit messages by analyzing repository changes following conventionalcommits.org specification

Commit Message Generator Skill

Generate conventional commit messages by analyzing repository changes following the Conventional Commits specification.

When to use this skill

Use this when you need to generate a commit message for staged or unstaged changes.
This is helpful for ensuring commit messages are standardized, descriptive, and follow best practices.
Triggered by user requests like:
- "Generate a commit message"
- "Create a commit for my changes"
- "What should my commit message be?"
- "Commit"

How to use it

Analyze Changes: Examine staged (git diff --cached) and unstaged (git diff) changes to understand the context.

Determine Commit Type: Select the appropriate type from the table below:

Type	Description
`feat`	New feature
`fix`	Bug fix
`docs`	Documentation only changes
`style`	Formatting, whitespace changes
`refactor`	Code restructuring without behavior change
`perf`	Performance improvement
`test`	Adding or correcting tests
`build`	Build system or dependency changes
`ci`	CI configuration changes
`chore`	Maintenance tasks
`revert`	Revert previous commit

Identify Scope: (Optional) Specify the affected codebase area (e.g., auth, api, ui).
Draft Message:
- Subject: Imperative mood, lowercase, no period (e.g., feat(auth): add login).
- Body: (Optional) Explain "what" and "why".
- Footer: (Optional) Breaking changes or issue references.

Output Format: Present the message in a code block, followed by the git command.

<type>(<scope>): <short description>

<optional body>

<optional footer>

Git Source:

git add . && git commit -m "<type>(<scope>): <description>" -m "<body>"