# Git Commit

> Create consistent commit messages

- **Type:** Skill
- **Install:** `agentstack add skill-jonathan0823-opencode-config-git-commit`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [Jonathan0823](https://agentstack.voostack.com/s/jonathan0823)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [Jonathan0823](https://github.com/Jonathan0823)
- **Source:** https://github.com/Jonathan0823/opencode-config/tree/main/skills/git-commit

## Install

```sh
agentstack add skill-jonathan0823-opencode-config-git-commit
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

## What I do

- Create commit messages based on conventional commits
- Commit message with "type(scope): description" format
- Suggests additional details for the commit body if needed
- Encourages single responsibility in commits
- Split to multiple commits if necessary following best practices and Single Responsibility Principle

1. **Commit Message Format**:
   - Use clear and concise commit messages.
   - Follow the format: `(): `
     - ``: chore, feat, fix, docs, style, refactor, test, perf, ci
     - ``: optional, specify the area of the codebase affected
     - ``: brief description of the change
   - Example: `feat(auth): add OAuth2 support`
2. **Descriptive Messages**:
   - Provide detailed descriptions in the commit body if necessary.
3. Single Responsibility:
   - Each commit only focuses on a single change or feature.
   - Avoid bundling unrelated changes in one commit.
   - Example: Instead of `fix and update UI`, use two separate commits: `fix(button): correct button alignment` and `feat(ui): update color scheme`.
4. Testing:
   - Ensure all tests pass before committing changes if applicable.
5. Linting:
   - Run linting tools to maintain code quality.

## When to use me

Use this when you are about to make a commit and want to ensure it follows conventional commit standards, and a brief description of the change.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [Jonathan0823](https://github.com/Jonathan0823)
- **Source:** [Jonathan0823/opencode-config](https://github.com/Jonathan0823/opencode-config)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-jonathan0823-opencode-config-git-commit
- Seller: https://agentstack.voostack.com/s/jonathan0823
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.