commit

Original：🇺🇸 English

Not Translated

Create a git commit following project conventions.

4installs

Added on2026-04-11

NPX Install

npx skill4agent add agglayer/agglayer-ai-skills commit

When creating a git commit:

text

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