Catalogskills.sh · parcadei

git-commits

Git Commit Rules

Review advisedVerified hub521 installs

Savant verdict: Review advised

Security analysis or source-hub review identified patterns requiring attention.

Live evaluation

Not evaluated yet. Workspaces can request a live evaluation.

Security assessment

Scan pending.

Structure

  • Description is very shortA description that says when to use the skill helps agents route to it.
  • No license declaredConfirm you may reuse this skill before importing it into your repository.
  • The source hub's security checks flagged this skillSocket: warn (1 alert: gptSecurity); Runlayer: warn (1/1 file flagged)

SKILL.md

---
name: git-commits
description: Git Commit Rules
user-invocable: false
---

# Git Commit Rules

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

## MUST Use /commit Skill

**DO NOT** run `git commit` directly. Instead:

```
Skill("commit")
```

The `/commit` skill:
1. Removes Claude attribution from commits
2. Generates reasoning.md capturing what was tried
3. Clears build attempts for next feature

## Why This Matters

- Regular `git commit` adds "Generated with Claude Code" and Co-Author lines
- The `/commit` skill removes these so commits appear user-authored
- Reasoning capture preserves build history for future sessions

## Trigger Words

When you see these in user prompts, use the commit skill:
- "commit", "push", "save changes"
- "push to github", "push changes"
- "commit and push"

## After Commit

The skill will prompt you to run:
```bash
bash "$CLAUDE_PROJECT_DIR/.claude/scripts/generate-reasoning.sh" <hash> "<message>"
```

Then push if requested:
```bash
git push origin <branch>
```