主站 Developer Toolscommit-message

commit-message

Name: commit-message
Author: ctrsploit

Generate semantic commit messages and commit safely

123 Stars0 Installs更新于 189 days ago

Goal

Generate a clear, professional Git commit message based on staged changes.
Follow Conventional Commits with a concise, intent-focused subject line.
Keep commits atomic; suggest splitting when changes are unrelated.
Provide clear guidance for both English and Chinese-speaking developers.

Workflow

Analyze staged changes (files, logic, and config).
Check atomicity:
- If unrelated changes exist, propose split groupings.
- Otherwise, proceed with a single commit message.
Draft output using the template below.
If committing is requested, follow the commit execution protocol exactly.

Commit Message Format (Conventional Commits)

<type>(<scope>): <subject>

<body>

Title Line

Type: feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert
Scope: optional module or area (e.g., "vul/cve-2019-5736", "env", "pkg/runtime")
Subject: imperative mood, no period, 50-72 characters max
Example: feat(vul/cve-2019-5736): add exploit for runc escape

Body (Use Sparingly)

Prefer title-only when it is sufficient.
Use a short body only for complex or non-obvious changes.
Focus on intent/impact (why), not exhaustive details (what).
Wrap at 72 characters.

Common Types for This Project

feat: New vulnerability detection or exploit functionality
fix: Bug fixes in vulnerability checks or exploits
docs: Documentation updates for vulnerabilities or usage
test: Adding or updating tests for security checks
chore: Maintenance tasks, dependency updates
refactor: Code restructuring without functional changes
perf: Performance improvements in detection or exploitation

Examples

Good titles:

feat(env): add namespace detection capabilities
fix(vul/cve-2022-0492): resolve nil pointer dereference
docs(vul): update cve-2024-0132 usage instructions
test(pkg/syscall): add unit tests for seccomp detection

Output Template

Files staged. Generating commit message:
Chinese Summary: <A clear Chinese summary; may include key files/vars>
English Draft:
<type>(<scope>): <subject>

<optional body>

Commit Execution Protocol

Always use a file-based commit message.
Create .commit-message in the repo root using file editing tools.
The file content must match the English Draft exactly.
Commit with git commit -F .commit-message.
Delete .commit-message after commit completes.

Safety

Do not change git config.
Do not use force push, hard reset, or amend unless explicitly requested.
For this security-focused project, ensure commit messages accurately reflect security implications.
When dealing with vulnerability-related changes, be precise about the CVE or vulnerability reference.

Best Practices

Be specific about the vulnerability or security aspect in the scope
Use CVE identifiers in parentheses when applicable: fix(cve-2022-0492): ...
For multiple CVEs in one change, use the most relevant one in the scope
When adding new exploits, use feat type: feat(vul): add cve-2024-xxxx exploit
When updating existing security checks, use feat for new functionality, fix for corrections

安装指令

npx skills add ctrsploit/commit-message

下载解压包

下载 skill.zip

下载完整 Skill 目录，包含 SKILL.md 及所有相关文件

信息

Authorctrsploit

Categorydeveloper

Version@main

Last Updated189 days ago

在 GitHub 中查看

Related Skills

local-places

Search for places (restaurants, cafes, etc.) via Google Places API proxy on localhost.

246,840·openclaw

github

Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.

246,840·openclaw

skill-creator

Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.

246,840·openclaw

voice-call

Start voice calls via the OpenClaw voice-call plugin.

246,840·openclaw

notion

Notion API for creating and managing pages, databases, and blocks.

246,840·openclaw

gemini

Gemini CLI for one-shot Q&A, summaries, and generation.

246,840·openclaw

Category:developer

主站 Developer Toolscommit-message

commit-message

Generate semantic commit messages and commit safely

123 Stars0 Installs更新于 189 days ago

Goal

Generate a clear, professional Git commit message based on staged changes.
Follow Conventional Commits with a concise, intent-focused subject line.
Keep commits atomic; suggest splitting when changes are unrelated.
Provide clear guidance for both English and Chinese-speaking developers.

Workflow

Analyze staged changes (files, logic, and config).
Check atomicity:
- If unrelated changes exist, propose split groupings.
- Otherwise, proceed with a single commit message.
Draft output using the template below.
If committing is requested, follow the commit execution protocol exactly.

Commit Message Format (Conventional Commits)

<type>(<scope>): <subject>

<body>

Title Line

Type: feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert
Scope: optional module or area (e.g., "vul/cve-2019-5736", "env", "pkg/runtime")
Subject: imperative mood, no period, 50-72 characters max
Example: feat(vul/cve-2019-5736): add exploit for runc escape

Body (Use Sparingly)

Prefer title-only when it is sufficient.
Use a short body only for complex or non-obvious changes.
Focus on intent/impact (why), not exhaustive details (what).
Wrap at 72 characters.

Common Types for This Project

feat: New vulnerability detection or exploit functionality
fix: Bug fixes in vulnerability checks or exploits
docs: Documentation updates for vulnerabilities or usage
test: Adding or updating tests for security checks
chore: Maintenance tasks, dependency updates
refactor: Code restructuring without functional changes
perf: Performance improvements in detection or exploitation

Examples

Good titles:

feat(env): add namespace detection capabilities
fix(vul/cve-2022-0492): resolve nil pointer dereference
docs(vul): update cve-2024-0132 usage instructions
test(pkg/syscall): add unit tests for seccomp detection

Output Template

Files staged. Generating commit message:
Chinese Summary: <A clear Chinese summary; may include key files/vars>
English Draft:
<type>(<scope>): <subject>

<optional body>

Commit Execution Protocol

Always use a file-based commit message.
Create .commit-message in the repo root using file editing tools.
The file content must match the English Draft exactly.
Commit with git commit -F .commit-message.
Delete .commit-message after commit completes.

Safety

Do not change git config.
Do not use force push, hard reset, or amend unless explicitly requested.
For this security-focused project, ensure commit messages accurately reflect security implications.
When dealing with vulnerability-related changes, be precise about the CVE or vulnerability reference.

Best Practices

Be specific about the vulnerability or security aspect in the scope
Use CVE identifiers in parentheses when applicable: fix(cve-2022-0492): ...
For multiple CVEs in one change, use the most relevant one in the scope
When adding new exploits, use feat type: feat(vul): add cve-2024-xxxx exploit
When updating existing security checks, use feat for new functionality, fix for corrections