Git Commits

by parcadeid07ff4b06b62No license3.9K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 8 months ago

Git Commit Rules

AI-generated overview

Redirects git commit, push, and save requests to a separate /commit skill instead of running git commit directly.

What it does: This instruction-only skill defines rules for handling git commit, push, and save requests. It tells the agent not to run git commit directly and instead to invoke a separate /commit skill, which it says removes Claude attribution, generates a reasoning.md file, and clears build attempts. It also lists trigger words and describes follow-up steps such as running a reasoning-generation script and pushing to a branch.
When to use it: Use when a user asks to commit, push, or save changes to git, including phrases like "push to github" or "commit and push". It is meant to route those requests through the designated commit skill rather than a direct git commit.
Requirements: No scripts ship with this skill; it is instructions only. It references a separate /commit skill, a generate-reasoning.sh script under the project's .claude/scripts directory, and git with push access to a remote.

Git Commit Rules

When the user asks to commit, push, or save changes to git:

DO NOT run git commit directly. Instead:

The /commit skill:

When you see these in user prompts, use the commit skill:

The skill will prompt you to run:

Then push if requested:

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.