Skip to content
Agentmart
Submit a tool

making-commits

Use when ready to commit code changes.

Skill by nocksock

IndexedMIT★ 1
Write a review

Chalk Labs

Need help deploying making-commits?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

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.

We use your email only for this newsletter. Privacy

About

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.

No 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

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
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from nocksock

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get making-commits running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying making-commits?

CallGet help
Cite this page

making-commits skill. Agent Mart. https://agentmart.dev/skills/nocksock-making-commits (last updated 2026-10-24)