jbvc/git-commit-message
Stage working tree changes and create a Conventional Commit (no push).
67
Quality
67%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Securityby
Passed
No known issues
- name:
- git-commit-message
- description:
- Stage working tree changes and create a Conventional Commit (no push).
- Run
git status --shortto review pending changes. - For each file, open a diff (
git diff -- path/to/file) and ensure no secrets or credentials are present. - Stage the files intentionally (
git add path/to/file). Avoidgit add .unless every change was reviewed. - Generate a Conventional Commit message (types: feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert).
- Commit subject ≤ 72 chars.
- Scope uses kebab-case (e.g.,
feat(marketing-skill): ...). - Use
.github/commit-template.txtfor Context / Testing / Reviewers sections.
- Run
git commitand paste the generated message + context from the template. - Show the resulting commit (
git log -1 --stat) and keep the commit hash handy. - Do not push in this command. Use
git/cp.mdwhen you're ready to publish.
- Workspace
- jbvc
- Visibility
- Public
- Created
- Last updated
- Publish Source
- CLI
- Badge
