git-commit
Git Commit Skill
Overview
Group working-tree changes into Conventional Commits 1.0.0 units (one commit per logical unit), or rewrite recent non-conformant commit subjects in place.
Core principle: Match user intent to the right workflow — new commits vs. history rewrite — and never bypass safety with destructive flags.
Announce at start: "I'm using the git-commit skill to <commit / push / rewrite> these changes."
Commands
| Command | Skill | Action | Operates on |
|---|---|---|---|
/git-commit |
git-commit |
Group working-tree changes into Conventional Commits | Uncommitted (staged + unstaged) changes |
/git-commit-push |
git-commit-push |
Same as above, then git push (no --force) |
Uncommitted changes + remote |
/git-commit-rewrite |
git-commit-rewrite |
Rewrite recent non-Conformant commit subjects | Existing local history |
Choosing the Right Command
More from chann/skills
code-review
Use when the user asks to review code, review changes, review a commit, review a PR, audit code quality, check for security issues, or generate a code review report. Trigger on phrases like "review my changes", "코드 리뷰", "check my code", "review the last commit", "what do you think of this diff", "compare branches", "code audit" — even if they don't say "code review" explicitly. For persistent file output use `code-review-md` (markdown) or `code-review-html` (markdown + HTML).
10code-review-md
Use when the user asks to save a code review to a file, write a markdown review report, persist review findings, or generate a review file in `.reviews/`. Trigger on phrases like "review my changes and save", "write the code review", "리뷰 결과 파일로 저장", "마크다운 리뷰 보고서", "/code-review-md". For interactive (no-file) review use the `code-review` skill; for HTML output use `code-review-html`.
8code-review-html
Use when the user asks for a styled HTML code review report, a browser-readable review, or both markdown + HTML output. Trigger on phrases like "/code-review-html", "HTML 리뷰 보고서", "styled review report", "review with badges/sidebar". For markdown-only output use `code-review-md`; for in-conversation review use `code-review`.
8long-task
Use when the user asks to build a project end-to-end, run autonomous multi-hour or multi-day development, or orchestrate multi-milestone work without human intervention. Trigger phrases include "build this whole project", "implement this end-to-end", "do this autonomously", "run a long task", "long-running agent", "build it from scratch and don't ask", or the explicit `/long-task` command. Also use for lifecycle subcommands such as `/long-task status`, `/long-task pause`, `/long-task resume`, `/long-task clear`, and `/long-task complete`.
5git-commit-push
Use when the user asks to commit working-tree changes AND push to the remote. Trigger on phrases like "commit and push", "커밋하고 푸시해줘", "/git-commit-push", "push my commits". Runs the git-commit workflow, then `git push` (never `--force`). For commit-only use `git-commit`; for history rewrite use `git-commit-rewrite`.
5git-merge-to-dev
Use when the user asks to merge the current branch into the dev branch (`dev`, falling back to `develop`) and delete the merged source branch. Trigger on phrases like "merge to dev", "dev에 머지", "develop에 합쳐줘", "merge this into dev and delete it", "/git-merge-to-dev". Switches to dev/develop, merges the source branch, then runs `git branch -d` on the source. For `main` use `git-merge-to-main`; to bulk-clean already-merged branches use `git-branch-cleanup`.
5