commit

Creates one validated local Git commit for the complete repository diff without pushing.

7|5|Updated Jul 22, 2025
One-click install
npx skills add https://github.com/nebius/nebius-ps-services --skill commit-nebius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/nebius/nebius-ps-services/tree/main/skills/commit
Command: npx skills add https://github.com/nebius/nebius-ps-services --skill commit-nebius

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) components.

What problem does it solve? Committing changes across a monorepo is error-prone: partial staging misses files in sibling project folders, secrets slip into commits, and hooks or crashes leave the repository in an ambiguous state. This Skill performs one safe, whole-repository local commit with explicit authorization, staged validation, and exact recovery semantics. ## Core Features & Use Cases - Whole-repo staging: Always runs git add -A from the Git root so multi-project changes are committed together, never narrowed by the current directory. - Safety gates: Stops on detached HEAD, in-progress merge/rebase, unresolved conflicts, obvious secrets, and default-branch commits without explicit authorization. - Transactional execution: Uses a temporary-index preview, one-shot claim token, repository lock, and drift revalidation so interrupted or hook-modified commits become STALE or REVIEW_REQUIRED instead of corrupting state. - Use Case: After editing files across several services in a monorepo, invoke $commit Add retry logic to services to stage everything, validate the staged diff, and create one local commit with normal hooks enabled. ## Quick Start Ask the agent to run $commit with an optional commit message to stage and commit the entire current repository diff locally.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I commit all changes across a monorepo at once?

Invoke $commit with an optional message; it runs git add -A from the repository root so staged, unstaged, and untracked changes in every project folder are included. The current working directory never narrows the commit scope.

What is the difference between $commit and $commit-push?

$commit creates only a local commit and never pushes, opens PRs, or touches remotes. $commit-push reuses the same local transaction as its commit phase and then performs the separately authorized push.

Can I commit directly on the default branch with git?

This Skill stops on the known local default branch unless you explicitly authorize it with $commit on <branch> or $commit on the default branch. It never fetches over the network just to discover the default branch.

Why did my commit stop with a STALE or REVIEW_REQUIRED status?

STALE means repository state drifted or a hook failed before any commit, requiring a fresh explicit $commit. REVIEW_REQUIRED means a hook altered the committed tree; the actual commit must be reviewed and acknowledged before the claim completes.

Does the commit skill run git hooks or bypass them?

Commit hooks run normally; the Skill never uses --no-verify or --allow-empty. A failed hook that creates no commit marks the claim STALE, and a hook that changes the tree triggers a review flow instead of amending.

When should I not use this git commit skill?

Do not use it for pushing, pull requests, branch operations, rebases, or Agentic SDLC checkpoints, which belong to commit-push, worktree, or sdlc-commit. It also refuses partial pathspec staging and stops on secrets or incoherent diffs.