Token导航 LogoToken导航TokenDH.com
运维和基础设施敏感数据github未标认证来源可访问clear审计通过

conventional-commit常规提交

Agent Skill

conventional-commit 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

1,364

周安装

58

GitHub Stars

4

下载量

478
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:conventional-commit(常规提交)
来源仓库:https://github.com/trancong12102/agentskills
仓库路径:skills/conventional-commit
安装命令:
npx skills add https://github.com/trancong12102/agentskills --skill conventional-commit
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/trancong12102/agentskills --skill conventional-commit

简介

conventional-commit 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中整理协作事项。

  • 适用于围绕仓库状态、代码变更或团队协作进行信息梳理。
  • 通过 npx skills add 命令从 GitHub 仓库安装使用。
  • 安装前需确认权限范围、维护状态及是否触发联网或文件操作。
  • 建议结合原始 README 文档进一步验证具体用法和功能边界。

SKILL.md

Conventional Commit Generator

Generate commit messages following Conventional Commits 1.0.0.

Workflow

  1. Run git status and git diff HEAD to analyze changes
  2. Stage files: user-specified only, or git add -A for all
  3. Determine type and scope from changes
  4. Generate commit message incorporating user hints
  5. Commit using HEREDOC format to preserve formatting: git commit -m "$(cat <<'EOF' <type>(<scope>): <description> <body> <footer> EOF)"
  6. Output: <hash> <subject>

Scope Boundaries

DO: Analyze git changes, generate messages, stage files, commit

DO NOT: Modify code, push (unless asked), create branches, amend without request

Commit Format

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

[optional body]

[optional footer(s)]

Type Selection

ChangeTypeSemVer
New featurefeatMINOR
Bug fixfixPATCH
Performance improvementperfPATCH
Code restructuring (no behavior change)refactor-
Code style/formatting (no logic change)style-
Adding/updating teststest-
Documentation onlydocs-
Build system/dependenciesbuild-
CI/CD configurationci-
Reverts a previous commitrevert-
Other maintenance taskschore-
Note: Only feat and fix have SemVer implications. Breaking changes (any type with exclamation mark or BREAKING CHANGE footer) trigger MAJOR.

Subject Line

  • Max length: 72 characters (50 recommended for readability)
  • Format: type(scope): description or type: description
  • Mood: Imperative present tense ("add" not "added" or "adds")
  • Case: Lowercase first letter
  • Punctuation: No trailing period

Scope

Scope provides context about which part of the codebase is affected. Use a noun describing the module, component, or area.

Common scope patterns:

  • Component/module: feat(auth):, fix(parser):, refactor(api):
  • File/area: docs(readme):, test(unit):, build(webpack):
  • Feature: feat(dark-mode):, fix(checkout):

Body

  • Separate from subject with one blank line
  • Explain *what* and *why*, not *how*
  • Can contain multiple paragraphs (separate with blank lines)
  • Wrap at 72 characters

Footer

Footers follow git trailer format with :<space> or <space># separator.

Common footers:

  • BREAKING CHANGE: <description> - Breaking API change
  • Refs: #123 or Refs: JIRA-456 - Reference issues
  • Closes: #123 or Fixes: #123 - Close issues
  • Co-authored-by: Name <email> - Credit co-authors
  • Reviewed-by: Name <email> - Credit reviewers
  • Acked-by: Name - Acknowledgment
Note: Footer tokens use - instead of spaces (e.g., Reviewed-by not Reviewed by). Exception: BREAKING CHANGE allows space.

Breaking Changes

Two ways to indicate breaking changes (can use both for emphasis):

  1. Exclamation mark: Add exclamation mark before colon in subject feat(api)!: remove deprecated endpoints
  2. Footer: Add BREAKING CHANGE: or BREAKING-CHANGE: in footer feat(api): redesign authentication flow BREAKING CHANGE: OAuth tokens now expire after 1 hour instead of 24 hours.

Examples

Simple feature:

feat: add email notifications for new messages

Bug fix with scope:

fix(cart): prevent ordering with empty shopping cart

Documentation update:

docs(api): add authentication examples to README

Breaking change with body and footer:

feat(api)!: redesign user authentication endpoints

Migrate from session-based auth to JWT tokens for better scalability.
The new system supports refresh tokens and configurable expiration.

BREAKING CHANGE: /api/login now returns JWT instead of session cookie.
Clients must include Authorization header with Bearer token.
Refs: JIRA-1337

Revert commit:

revert: let us never again speak of the noodle incident

Refs: 676104e, a215868

Multi-scope change (use most significant):

feat(auth): add OAuth2 support with Google provider

Adds Google OAuth2 login flow with automatic account linking.

Co-authored-by: Jane Doe <jane@example.com>
Closes: #42

Anti-patterns

Avoid these common mistakes:

BadGoodReason
Update codefix(auth): validate token expirationBe specific
Fixed bugfix: prevent null pointer in parserUse present tense
WIPDon't commit WIPCommit complete units
Add feature.feat: add dark mode toggleNo trailing period
Added teststest: add unit tests for parserUse imperative mood
FEAT: Add...feat: add...Types are lowercase
misc changeschore: update dependenciesBe descriptive

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Claude Code

28.79%
按下载量换算138

OpenCode

22.79%
按下载量换算109

Codex

16.9%
按下载量换算81

Cursor

13.31%
按下载量换算64

Gemini CLI

7.54%
按下载量换算36

Antigravity

3.02%
按下载量换算14

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

来源信息

继续浏览同类 Skills