# Git Commit

> Use when inspecting local git changes, drafting or validating Conventional Commit messages, checking type or scope choices, explaining breaking changes, or creating a focused commit from the actual diff.

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

## Install

```sh
agentstack add skill-narumiruna-skills-git-commit
```

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

## About

# Git Commit

Inspect the actual diff before writing the message. Prefer one coherent commit per intent, then map that intent to a Conventional Commits title and only add extra sections when they carry concrete information.

Read `references/conventional-commits.md` when the type is ambiguous, when you need trailers or breaking-change wording, or when the user asks for exact format details.

## Workflow

1. Inspect the exact commit contents.
   Start with `git status --short`. If the user asks for a commit, inspect `git diff --cached` first; inspect `git diff` too when unstaged changes might affect the commit boundary.
2. Define the commit boundary.
   Group files by one user-visible intent. If the diff mixes unrelated work, recommend splitting it into multiple commits instead of forcing one vague summary over several intents.
3. Choose the type and scope from behavior.
   Pick the lowercase Conventional Commits type that best matches the dominant behavior. Add a short noun-like scope only when it adds signal.
4. Write the title in the required format.
   Use `[optional scope][!]: `. Keep the description short, specific, and grounded in the diff.
5. Add body and footers only when they add concrete value.
   Use the body for why, constraints, or tradeoffs. Add footers only for real trailers or `BREAKING CHANGE:`.
6. Keep the message aligned with the selected diff.
   Do not describe unstaged changes, planned follow-up work, or unrelated cleanup that is not part of the commit.

## Decision Rules

- Prefer `feat` for a new capability and `fix` for incorrect behavior or regressions.
- Prefer `refactor` when behavior should stay the same, and `docs` when only documentation changes.
- Prefer no scope, body, or footer unless each one adds concrete signal.
- Prefer multiple commits over one vague summary when the diff contains unrelated work.
- If the user asks for validation, check both the structure and whether the wording matches the inspected diff.
- Follow repo git rules for staging and commit structure; this skill focuses on mapping the diff to the right message.
- Do not add, preserve, or generate any AI attribution trailers in commits, PRs, or messages, including `Co-authored-by`, `Generated-by`, `Created-by`, `Coding-Agent`, model names, tool names, or agent attribution footers.

## Reference

- `references/conventional-commits.md`: exact format, common types, footer rules, breaking-change wording, and examples.

## Source & license

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

- **Author:** [narumiruna](https://github.com/narumiruna)
- **Source:** [narumiruna/skills](https://github.com/narumiruna/skills)
- **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-narumiruna-skills-git-commit
- Seller: https://agentstack.voostack.com/s/narumiruna
- 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%.