| name | caveman-commit-push |
| description | Safely commit current repository changes with a caveman-commit style Conventional Commit message and push the current branch. Use when the user says "커밋 푸시", "커밋/푸시", "commit push", "caveman commit push", or asks to commit and push with a terse commit message. |
Caveman Commit Push
Commit and push repository changes safely. Generate the commit message using
caveman-commit rules: terse, exact, Conventional Commits format.
Workflow
Use this skill from the repository root. Keep secrets and generated artifacts
out of commits.
- Inspect repository state:
git status --short
git branch --show-current
git diff --stat
- Identify commit candidates.
Include source, docs, scripts, tests, and skill files that match the user's
requested scope. Exclude ignored/generated/sensitive files such as:
.env
.env.*
.rummipoker_deploy.env
build/
rummipoker/
rummipoker.zip
*.log
Never run git add . blindly. Stage explicit paths only.
- Review enough diff to write a correct message:
git diff -- <paths>
git diff --cached --stat
git diff --cached --check
If the diff contains secrets, credentials, tokens, private keys, or unintended
generated artifacts, stop and report the exact file path without printing the
secret.
- Generate the commit message with
caveman-commit rules.
Subject:
<type>(<scope>): <imperative summary>
Rules:
- Types:
feat, fix, refactor, perf, docs, test, chore,
build, ci, style, revert
- Scope is optional.
- Prefer <=50 chars, hard cap 72.
- No trailing period.
- Body only for non-obvious why, breaking changes, migrations, security fixes,
or reverts.
- No AI attribution.
Examples:
fix(market): stabilize tab content height
docs(skills): add caveman commit push flow
- Stage explicit paths and commit:
git add <explicit paths>
git commit -m "<subject>"
For a required body:
git commit -m "<subject>" -m "<body>"
- Push the current branch:
git push
If the branch has no upstream:
git push -u origin "$(git branch --show-current)"
Do not force push. Do not run git reset --hard, git checkout --, or
destructive cleanup commands unless the user explicitly asks.
Reporting
Report in Korean with:
- Files committed.
- Commit message.
- Commit hash.
- Branch pushed.
- Push result.
If there is nothing to commit, say so and do not create an empty commit unless
the user explicitly asks.
