원클릭으로 Manus에서 모든 스킬 실행

시작하기

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 저장소 열기 Creator 저장소 보기

다운로드

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>"