Skip to content

jeremylongshore/tons-of-skills-marketplace / plugins/devops/git-commit-smart/skills/generating-smart-commits

generating-smart-commits

Verified

Execute use when generating conventional commit messages from staged git changes. Trigger with phrases like "create commit message", "generate smart commit", "/commit-smart", or "/gc". Automatically analyzes changes to determine commit type (feat, fix, docs), identifies breaking changes, and formats according to conventional commit standards.

FileKindSize
SKILL.mdskill md4.0 KB
assets/README.mdmarkdown234 B
assets/commit_template.txtmarkdown3.7 KB
assets/example_diff.txtmarkdown4.1 KB
references/README.mdmarkdown59 B
scripts/README.mdmarkdown434 B
scripts/commit_analyzer.pyexecutablescript4.6 KB

assets/commit_template.txt

View on GitHub
# Commit Message Template

This template is designed to help you create a well-structured and informative commit message following the Conventional Commits standard. Please fill in the placeholders below with relevant information about your changes.

## Commit Type

Choose one of the following commit types that best describes the nature of your changes:

*   **feat**: A new feature
*   **fix**: A bug fix
*   **docs**: Documentation only changes
*   **style**: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
*   **refactor**: A code change that neither adds a feature nor fixes a bug
*   **perf**: A code change that improves performance
*   **test**: Adding missing tests or correcting existing tests
*   **build**: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
*   **ci**: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
*   **chore**: Other changes that don't modify src or test files
*   **revert**: Reverts a previous commit

**Placeholder:** `type(scope): description`

**Example:** `feat(auth): Implement user authentication`

## Scope (Optional)

The scope could be anything specifying the place of the commit change. For example `auth`, `user`, `profile`, etc.

*   If the change affects more than one scope, you can omit the scope entirely.
*   If the change is a global change, you can use `*` as the scope.

**Placeholder:** `(scope)`

**Example:** `(api)`

## Description

Write a concise and clear description of the changes made. Use the imperative, present tense: "change" not "changed" nor "changes".

**Placeholder:** `description`

**Example:** `Add support for JWT authentication`

## Body (Optional)

Provide a more detailed explanation of the changes made. This section is optional but highly recommended for complex changes. Use the imperative, present tense: "change" not "changed" nor "changes".

*   Explain the motivation for the change.
*   Describe the approach taken.
*   Include any relevant context or background information.

**Placeholder:**

```
Longer explanation of the commit, if necessary.

- Explain the problem and why this commit solves it.
- Provide context about the changes.
- Add any relevant details.
```

**Example:**

```
This commit introduces JWT authentication to improve the security of the API.

The previous authentication mechanism was based on simple API keys, which were vulnerable to brute-force attacks. JWTs provide a more secure and scalable solution.

The following steps were taken:

- Added the `jsonwebtoken` library as a dependency.
- Implemented a new `authenticate` middleware function.
- Updated the API endpoints to use the new middleware.
```

## Footer(s) (Optional)

Footers can be used to add metadata to the commit message, such as:

*   **BREAKING CHANGE**: If the commit introduces a breaking change, add a `BREAKING CHANGE:` footer with a description of the change.
*   **Closes**:  Referencing issue tracker ids.

**Placeholder:**

```
BREAKING CHANGE: Description of the breaking change.

Closes #123
Refs #456
```

**Example:**

```
BREAKING CHANGE: The API endpoint `/users` has been renamed to `/profiles`.

Closes #123
```

## Complete Example

```
feat(auth): Implement user authentication

This commit introduces JWT authentication to improve the security of the API.

The previous authentication mechanism was based on simple API keys, which were vulnerable to brute-force attacks. JWTs provide a more secure and scalable solution.

The following steps were taken:

- Added the `jsonwebtoken` library as a dependency.
- Implemented a new `authenticate` middleware function.
- Updated the API endpoints to use the new middleware.
```
rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).Stars: 198kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 198kUpdated Claude CodeCodexVerifiedInstall