Compose a Conventional Commits message with type, scope, breaking changes, body, and footers.
Conventional Commits format
A structured commit message that powers automated changelogs and SemVer bumps. Fill the fields below and the message assembles live.
A new feature (SemVer MINOR)
The section of the codebase affected. Rendered as type(scope):
43 chars
header 54/72Use the imperative mood, lower-case, no trailing period — "add", not "added" or "adds".
Prefix the description with a themed emoji
Adds ! to the header and a BREAKING CHANGE: footer (SemVer MAJOR)
Free-form. A blank line separates it from the header. New lines are preserved.
Tokens use - instead of spaces. Values starting with # render with a space (e.g. Closes #123).
Commit message
54 col headerfeat(api): add cursor pagination to the users endpoint Support `?limit` and `?cursor` query params on GET /users. Responses now include a `nextCursor` field. Defaults to 20 items per page. Closes #128
Tip: paste this straight into git commit -F - or your editor. The first line becomes the commit subject.
