git-commit

Developer Tools

Gives your agent the ability to write professional, structured commit messages following conventional standards for clear version control history.

When to use

When you want to ensure consistent and meaningful commit history
When you need to categorize changes using standard types like feat or fix
When documenting complex changes with detailed descriptions and issue references

How to use

1
Stage the files you want to include in the commit
2
Describe the changes made and the reasoning behind them to the agent
3
Review the generated commit message for accuracy and formatting
4
Execute the commit command to save your changes to the repository

Example conversation

case

You

I added JWT authentication and updated the user model. Write a commit message for this.

Agent

I'll generate a conventional commit message for you. It will start with 'feat(auth): add JWT authentication', followed by a detailed body listing the implementation of token generation, validation middleware, and user model updates. I'll also include any relevant issue references like 'Closes #42'.

FAQ

Related Skills

conventional-commitDeveloper Tools

Gives your agent the ability to generate standardized, descriptive commit messages following the Conventional Commits specification for better project history and automation.

git-workflowDeveloper Tools

Gives your agent the ability to manage complete Git lifecycles, from branch creation and commits to complex merges and conflict resolution.

git-submoduleDeveloper Tools

Gives your agent the ability to manage external Git repositories as submodules within your main project for modular dependency management.

npm-git-installDeveloper Tools

Install npm packages directly from GitHub repositories using git URLs for private repos, specific branches, or unreleased versions.

using-git-worktreesDeveloper Tools

Gives your agent the ability to set up isolated git worktrees for feature development without switching branches in your main workspace.

git-commit

Developer Tools

Gives your agent the ability to write professional, structured commit messages following conventional standards for clear version control history.

When to use

When you want to ensure consistent and meaningful commit history
When you need to categorize changes using standard types like feat or fix
When documenting complex changes with detailed descriptions and issue references

How to use

1
Stage the files you want to include in the commit
2
Describe the changes made and the reasoning behind them to the agent
3
Review the generated commit message for accuracy and formatting
4
Execute the commit command to save your changes to the repository

Example conversation

case

You

I added JWT authentication and updated the user model. Write a commit message for this.

Agent

FAQ

Related Skills

conventional-commitDeveloper Tools

Gives your agent the ability to generate standardized, descriptive commit messages following the Conventional Commits specification for better project history and automation.

git-workflowDeveloper Tools

Gives your agent the ability to manage complete Git lifecycles, from branch creation and commits to complex merges and conflict resolution.

git-submoduleDeveloper Tools

Gives your agent the ability to manage external Git repositories as submodules within your main project for modular dependency management.

npm-git-installDeveloper Tools

Install npm packages directly from GitHub repositories using git URLs for private repos, specific branches, or unreleased versions.

using-git-worktreesDeveloper Tools

Gives your agent the ability to set up isolated git worktrees for feature development without switching branches in your main workspace.

Product

Community

git-commit

When to use

How to use

Example conversation

FAQ

Related Skills

Product

Community

git-commit

When to use

How to use

Example conversation

FAQ

Related Skills

Product

Community