Name: Conventional Commits
Author: crnvl96

name	conventional-commits
description	Ensure git commits follow a consistent format. Use when making git commits.
compatibility	Requires Git.

Infer from the prompt if the user provided specific file paths/globs and/or additional instructions.
Review git status and git diff to understand the current changes. Limit to argument-specified files if provided.
Optionally run git log -n 50 --pretty=format:%s to see commonly used scopes.
If there are ambiguous extra files, ask the user for clarification before committing.
Stage only the intended files, or all changes if no files specified.
Run git commit -m "<subject>", and -m "<body>" if needed.

<type>(<scope>): <summary>

<body>

Template rules:

type is required. Use feat for new features, fix for bug fixes. Other common types: docs, refactor, chore, test, perf.
scope is optional. Short noun in parentheses for the affected area (e.g. api, parser, ui, etc).
summary is required. Short, imperative, <= 72 chars, no trailing period.
body is optional. If needed, add a blank line after the subject and write short paragraphs.

Do not include breaking-change markers or footers.
Do not add sign-offs (no Signed-off-by).
Only commit, do not push.
If it is unclear whether a file should be included, ask the user which files to commit.

name	conventional-commits
description	Ensure git commits follow a consistent format. Use when making git commits.
compatibility	Requires Git.

Infer from the prompt if the user provided specific file paths/globs and/or additional instructions.
Review git status and git diff to understand the current changes. Limit to argument-specified files if provided.
Optionally run git log -n 50 --pretty=format:%s to see commonly used scopes.
If there are ambiguous extra files, ask the user for clarification before committing.
Stage only the intended files, or all changes if no files specified.
Run git commit -m "<subject>", and -m "<body>" if needed.

<type>(<scope>): <summary>

<body>

Template rules:

type is required. Use feat for new features, fix for bug fixes. Other common types: docs, refactor, chore, test, perf.
scope is optional. Short noun in parentheses for the affected area (e.g. api, parser, ui, etc).
summary is required. Short, imperative, <= 72 chars, no trailing period.
body is optional. If needed, add a blank line after the subject and write short paragraphs.

Do not include breaking-change markers or footers.
Do not add sign-offs (no Signed-off-by).
Only commit, do not push.
If it is unclear whether a file should be included, ask the user which files to commit.

conventional-commits