git-commit-message

Generate git commit messages in a specific bullet-point format with a conventional header.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "git-commit-message" with this command: npx skills add preetamnath/agent-skills/preetamnath-agent-skills-git-commit-message

Git Commit Message Generation

When asked to generate a git commit message, satisfy the following rules:

  1. Gather Context (read-only — do not stage anything):

    • Run git status to identify all modified, deleted, staged, and untracked files.
    • Run git diff to see all unstaged changes.
    • Run git diff --cached to see all already-staged changes.
    • Untracked files: Read the full content of new files.
    • Deleted files: Note the removal.
    • Combine all of the above to form a complete picture of what will be committed.
  2. Draft Message:

    • Create a conventional commit message based on the actual changes found.
    • Header: Start with a Conventional Commit header (e.g., feat:, fix:, refactor:) that captures the key change.
    • Body: Leave one empty line after the header, then a list of details.
    • Format: Use a simple bulleted list (-) for the details.
    • Style: Use the imperative mood (e.g., "Create", "Update", "Fix", "Refactor").
    • Quotes: NEVER use double quotes (") in the commit message content. Use single quotes (') instead if you need to quote something.
  3. Execute:

    • Construct the final command: git add . && git commit -m "YOUR_MESSAGE_HERE".
    • Output: Present the final command in a markdown code block (bash) so the user can copy/paste if they reject the tool.
    • Then, immediately execute the command.

Usage Example

Input: "Commit these changes."

Context: User has modified several files related to the layout.

Output:

git add . && git commit -m "refactor(learn): unify header layout and simplify access logic

- Create learn/layout.tsx shared layout file for learn routes
- Create LearnPagesHeader.tsx to consolidate title/breadcrumb and UserProfileDropDown.tsx across /learn and /learn/:slug routes
- Update code in UnpaidUserBanner.tsx and NoAccessToThisNote.tsx components
- Consolidate 'Paid User' and 'Valid Access Config' checks into unified logic blocks across pages
- Add JSDoc documentation to BreadcrumbLink.tsx, UserProfileDropdown.tsx and learn/layout.tsx"

Action: Agent then executes the command above.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Research

sentry-analysis

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

code-review

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

vercel-composition-patterns

React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.

Repository Source
85.9K23Kvercel
Automation

vercel-react-native-skills

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

Repository Source
60.2K23Kvercel