Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/nocksock-making-commits
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/making-commits
What's inside
- Skill 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.
- License
- MIT
- Instructions
- 87 lines in SKILL.md · view on GitHub
Files (1)
- SKILL.md
SKILL.md (first lines)
# 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 1. **Verify** - Run tests, build if applicable 2. **Review diff** - `git diff --staged` 3. **No secrets** - No API keys, passwords, credentials 4. **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
From nocksock/superpowers, MIT.
More from nocksock/superpowers
- 0.432score
deep-work-session
nocksock
Use when user explicitly mentions 'deep work' or signals substantial work ('let's build/implement X').
SkillDFreshness: D★ 1Claude Code +9 - 0.432score
holistic-view
nocksock
Use this when given larger tasks, before starting the implementation, or during code reviews.
SkillDFreshness: D★ 1Claude Code +9 - 0.432score
jotai-atom-architecture
nocksock
Use when designing Jotai state architecture, setting up atom composition patterns, managing large objects, or debugging re-render issues - ensures proper atom…
SkillDFreshness: D★ 1Claude Code +9 - 0.432score
r3f-performance-optimization
nocksock
Use when optimizing React Three Fiber scenes, experiencing frame drops, high draw calls, or implementing 3D performance features - ensures systematic…
SkillDFreshness: D★ 1Claude Code +9 - 0.432score
component-authoring
nocksock
Use this when writing any kind of UI components in any language (heex, react, web components, and so on).
SkillDFreshness: D★ 1Claude Code +9 - 0.432score
session-handoff
nocksock
Use when approaching context limits (75-85%) to write comprehensive handoff documents for session continuity.
SkillDFreshness: D★ 1Claude Code +9 - 0.431score
code-cleanup
nocksock
Use when asked to clean up code, or after introducing a new larger feature.
SkillDFreshness: D★ 1Claude Code +9 - 0.423score
prioritise-todos
nocksock
Use this to rate and prioritise todos
SkillDFreshness: D★ 1Claude Code +9 - 0.423score
elixir-code
nocksock
ALWAYS use this skill, whenever you touch elixir code
SkillDFreshness: D★ 1Claude Code +9 - 0.423score
find-code-todos
nocksock
Use this to find todos in the source code
SkillDFreshness: D★ 1Claude Code +9 - 0.409score
brainstorming
nocksock
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior.
SkillDFreshness: D★ 1Claude Code +9 - 0.407score
finishing-a-development-branch
nocksock
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting…
SkillDFreshness: D★ 1Claude Code +9
Signals
- Stars
- 1
- Forks
- 0
- Open issues
- 0
- Last commit (this folder)
- Feb 5, 2026 (8 months ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- Repository
- github.com/nocksock/superpowers
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from nocksock
- 0.432score
r3f-performance-optimization
nocksock
Use when optimizing React Three Fiber scenes, experiencing frame drops, high draw calls, or implementing 3D performance features - ensures systematic…
SkillDFreshness: D★ 1Claude Code +9 - 0.432score
jotai-atom-architecture
nocksock
Use when designing Jotai state architecture, setting up atom composition patterns, managing large objects, or debugging re-render issues - ensures proper atom…
SkillDFreshness: D★ 1Claude Code +9 - 0.432score
deep-work-session
nocksock
Use when user explicitly mentions 'deep work' or signals substantial work ('let's build/implement X').
SkillDFreshness: D★ 1Claude Code +9 - 0.432score
holistic-view
nocksock
Use this when given larger tasks, before starting the implementation, or during code reviews.
SkillDFreshness: D★ 1Claude Code +9 - 0.432score
component-authoring
nocksock
Use this when writing any kind of UI components in any language (heex, react, web components, and so on).
SkillDFreshness: D★ 1Claude Code +9 - 0.432score
session-handoff
nocksock
Use when approaching context limits (75-85%) to write comprehensive handoff documents for session continuity.
SkillDFreshness: D★ 1Claude Code +9
Cite this page
making-commits skill. Agent Mart. https://agentmart.dev/skills/nocksock-making-commits (last updated 2026-10-24)