commit

Generate git commit messages from staged changes with secret checks.

12.6k|1.5k|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/nearai/ironclaw --skill commit-nearai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/nearai/ironclaw/tree/main/skills/commit
Command: npx skills add https://github.com/nearai/ironclaw --skill commit-nearai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you turn staged git changes into clear, consistent commit messages without guessing wording or risking accidental secret commits.

Core Features & Use Cases

  • Staged-Change Aware Drafting: Inspects staged diffs and recent log entries to match your repository’s existing commit style.
  • Secret-Safety Guardrails: Warns if staged files look like they may contain secrets (for example, env files or credential artifacts).
  • Confirmation Before Commit: Presents a proposed commit message and requires confirmation before running git commit.

Quick Start

Ask your AI: “Create a git commit message for my staged changes and show the message for confirmation.”

Frequently Asked Questions about commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a git commit message from staged changes automatically?

The skill inspects your staged diffs and recent log entries to draft a git commit message that matches your repository's style, then presents the proposed message for your confirmation before executing the commit.

What is the best way to ensure staged files do not contain secrets before committing?

This skill applies secret-safety guardrails that specifically scan and warn if your staged changes look like they may contain env files or credential artifacts before you commit, preventing accidental secret exposure.

Can I match my existing git commit style when generating messages from diffs?

Yes, the skill inspects recent log entries alongside your staged diff content to ensure the generated message aligns with your repository's established wording and conventions, matching your existing git commit style.

Does the AI run the git commit automatically after analyzing the diff?

No, the AI requires explicit confirmation after showing you the proposed commit message, ensuring you maintain full control over the version control workflow before it runs the git commit.

What types of changes are supported when generating commit messages from diffs?

Generating commit messages from diffs supports committing features, bug fixes, refactors, documentation updates, and tests, correctly summarizing the staged snapshots for each of these specific change types.