# Commit

> Create a git commit following project conventions.

- Skill: `agglayer/commit` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add agglayer/commit`
- Raw SKILL.md: https://api.skillmd.com/api/skills/agglayer/commit/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: agglayer (https://skillmd.com/u/agglayer)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/agglayer/commit

---


When creating a git commit:

- Use Conventional Commits format (see [Format](#format))
- Follow repository commit conventions

## Format

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

[optional body]

[optional footer(s)]
```

## Rules

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

## Steps

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

## Additional resources

- For complete convention details, see [conventional-commits](https://conventionalcommits.org/en/v1.0.0/)
- For usage examples, see [samples.md](examples/samples.md)