commit

Create a git commit following project conventions.

安装方式

默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。

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

直接命令不会经过审查 Prompt；运行前请先检查来源。

npx skills add https://github.com/agglayer/agglayer --skill commit

命令会保持在同一行。复制前请横向滚动并检查完整内容。

想先保存到本地？可下载 SkillsMP 当前能够提供的文件。

决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。

文件资源管理器

2 个文件

SKILL.md

来源说明 · 只读预览

name	commit
description	Create a git commit following project conventions.
disable-model-invocation	true

When creating a git commit:

<type>(<optional-scope>): <description>

[optional body]

[optional footer(s)]

Subject line: imperative mood, lowercase start, no trailing period.
Subject line max: 72 characters.
Body lines max: 72 characters, except long URLs, code blocks, or stack traces.
Allowed types: feat, fix, docs, chore, style, refactor, perf, test, build, ci, revert.
Scope: optional, should name the affected crate or area (e.g., prover, grpc, config).
Footer: CONFIG-CHANGE: for configuration changes (multi-line allowed). BREAKING-CHANGE: for breaking changes (multi-line allowed).

Run the verify skill before staging. All matching checks must pass before proceeding.
Review staged changes with git diff --cached.
Draft a commit message following the rules above.
Present the message for approval before committing.
Create the commit with git commit -S (GPG-sign). Repos enforce verified signatures; unsigned pushes are rejected. Do not push unless explicitly asked.