making-commits
Use when ready to commit code changes. Covers conventional commit format, commit sizing, GPG failures, and push safety. Other skills invoke this for commit mechanics.
- License 许可
- MIT
- 最近更新
- 2026-03-19
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- making-commits
- description
- Use when ready to commit code changes. Covers conventional commit format, commit sizing, GPG failures, and push safety. Other skills invoke this for commit mechanics.
02 资源文件 7
- 参考文档agents/openai.yaml327 B
- 参考文档evals/evals.json4.6 KB
- 参考文档evals/trigger-queries.json1.3 KB
- 参考文档references/defense-in-depth.md8.8 KB
- 参考文档references/examples.md2.0 KB
- 参考文档references/phases-and-rationalisations.md2.8 KB
- 参考文档references/root-cause-tracing.md8.5 KB
03 SKILL.md 正文
Making Commits
Commit mechanics when committing is allowed. For WHEN to commit, see COMMIT_PREFERENCE in deep-work-session.
Core principle: Small, focused commits. Verify first. Never push without asking.
Explicit Invocation
If user explicitly asks to commit (not via deep work session) with substantial changes (5+ files):
"I see substantial changes. Before committing, what's your preference?" Options: Single commit / Multiple commits (by logical unit) / Let me review what to include
Conventional Commit Format
type(scope): description # lowercase, imperative, <72 chars, no period
| Type | Use |
|---|---|
feat |
New feature |
fix |
Bug fix |
docs |
Documentation only |
refactor |
Neither fix nor feature |
test |
Tests |
chore |
Maintenance |
Commit Sizing
- One logical change per commit
- Break up: unrelated changes, bug+feature mixed, refactor+behavior mixed
- Keep together: test+implementation for same feature
Pre-Commit
- Verify - Run tests, build if applicable
- Review diff -
git diff --staged - No secrets - No API keys, passwords, credentials
- No debug code - No console.log, debugger
REQUIRED: superpowers:verification-before-completion for significant changes.
GPG Signing Failure
If gpg failed to sign the data:
Use question tool:
"GPG signing failed. How to proceed?" Options: Retry / Skip signing (--no-gpg-sign) / Abort
Never silently skip or retry.
Push Safety
Never push without explicit permission.
Use question tool before any push:
"Ready to push to [remote/branch]. Confirm?" Options: Yes, push / No, don't push
Force push: Warn about overwriting remote history, require explicit confirmation.
Never:
- Push automatically after commit
- Push to main/master without confirmation
- Force push without warning
- Push commits you didn't create
Quick Reference
| Situation | Action |
|---|---|
| GPG fails | Ask user (question tool) |
| Want to push | Ask user (question tool) |
| Large changeset | Break into smaller commits |
| Secrets in diff | Remove, never commit |
Integration
Delegating skills: writing-plans, subagent-driven-development, implementer-prompt
Required: verification-before-completion (before significant commits)
Preference system: COMMIT_PREFERENCE = WHETHER to commit; this skill = HOW
04 同仓库更多 Skills
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
writing good code
use this skill whenever you write code. it provides a process for creating good, composable apis.
write-review-elixir
Review Elixir code. ALWAYS use this skill before or after you added code written in elixir to ensure high code quality. Also use use this when asked to review existing elixir code.
whats-next
Answers what to do next, what to work on next, where we're at
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always