commit

Create Git commits with project-convention messages and safety protocols.

Updated Aug 23, 2025
One-click install
npx skills add https://github.com/Locked-Inc/STAR --skill commit-locked-inc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/Locked-Inc/STAR/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/Locked-Inc/STAR --skill commit-locked-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you create Git commits that adhere to project conventions, ensuring code is saved safely and with clear, descriptive messages.

Core Features & Use Cases

  • Safe Committing: Prevents accidental staging of sensitive files and avoids destructive Git operations.
  • Convention Adherence: Drafts commit messages that summarize changes and follow project style.
  • Hook Failure Handling: Guides you through fixing pre-commit hook issues and creating new commits instead of amending.
  • Use Case: When you've finished implementing a new feature, use this Skill to stage your changes, write a clear commit message like "Add user authentication module", and commit your work without risking data loss or breaking the build.

Quick Start

Use the commit skill to create a new git commit with the message "feat: Implement user login endpoint".

Frequently Asked Questions about commit

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

FAQPage Schema
How do I create a git commit without accidentally staging sensitive files?

To create a git commit safely, specific files must be staged explicitly rather than using broad commands. This prevents accidental staging of sensitive files and avoids destructive git operations during version control.

What is the best way to format commit messages for project conventions?

Commit messages should summarize changes clearly while following existing project style conventions. Drafting descriptive messages ensures code history remains organized and understandable across the version control workflow.

How do I fix pre-commit hook failures when saving code to git?

When pre-commit hook failures occur while saving code to git, create a new commit instead of amending the failed one. This approach guides you through resolving hook issues without risking data loss.

Can I use destructive git commands like amend when committing changes?

Destructive git commands like amend should be avoided unless explicitly requested. Strict git safety rules require creating new commits to preserve history and prevent data loss during version control operations.

Does this git workflow support staging individual files instead of all changes?

Yes, the git workflow requires adherence to specific file staging protocols. By staging individual files explicitly, you control exactly what changes are saved to version control and prevent unwanted files from entering the repository.