# Commit

> |

- **Type:** Skill
- **Install:** `agentstack add skill-dynobox-dynobox-commit`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [dynobox](https://agentstack.voostack.com/s/dynobox)
- **Installs:** 0
- **Category:** [AI & ML](https://agentstack.voostack.com/c/ai-and-ml)
- **Latest version:** 0.1.0
- **License:** Apache-2.0
- **Upstream author:** [dynobox](https://github.com/dynobox)
- **Source:** https://github.com/dynobox/dynobox/tree/main/.agents/skills/commit
- **Website:** https://dynobox.xyz

## Install

```sh
agentstack add skill-dynobox-dynobox-commit
```

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

## About

# Commit

This skill prepares safe, focused git commits using the repository's
Conventional Commit style.

If the requested commit is for an npm publish, version bump, git tag, release
changelog entry, or publish readiness workflow, use the `release` skill instead.

## Before you start

Inspect the repository state:

```bash
git status --short
git diff
git diff --staged
git log -5 --oneline
```

Do not commit unless the user explicitly asked to commit. If the user only asked
for a message suggestion or review, do not stage or commit files.

Never amend a commit unless the user explicitly asks. Never push unless the user
explicitly asks.

## Inspect changes

Identify which files belong to the requested commit and which files may be
unrelated user work.

Before staging, check for likely secrets or accidental artifacts:

- `.env` files
- credentials, tokens, keys, or npm auth files
- debug logs or npm error logs
- generated tarballs or temporary archives
- unrelated build outputs

If the working tree contains unrelated changes, stage only the relevant files
with explicit paths. Do not use `git add -A` unless all changed files clearly
belong to the requested commit.

## Changelog decision

Update `CHANGELOG.md` only when the change is user-facing or release-relevant.

Usually update the changelog for:

- New user-facing CLI behavior
- SDK authoring API changes
- Bug fixes users would notice
- Packaging changes that affect installs or publishes

Usually do not update the changelog for:

- Tests only
- Internal refactors
- Lint or formatting only
- Documentation-only changes
- WIP changes that are not ready to announce

If unsure, ask whether the change should be added to `[Unreleased]`. For release
version sections, use the `release` skill instead.

## Verification

Run verification that matches the change scope before committing when practical:

```bash
pnpm test
```

For package-specific changes, prefer scoped verification where appropriate:

```bash
pnpm --filter  test
pnpm --filter  typecheck
```

If verification is skipped, include the reason in the final response.

## Commit message

Use Conventional Commit style with a scope when appropriate:

```text
(): 
```

Common types:

- `feat` for new behavior
- `fix` for bug fixes
- `docs` for documentation-only changes
- `test` for tests-only changes
- `refactor` for behavior-preserving code changes
- `chore` for repository maintenance

Common scopes in this repo:

- `cli`
- `sdk`
- `runner-local`
- `evaluators`
- `release`
- `docs`

Examples:

```bash
git commit -m "fix(cli): bundle private runtime packages"
git commit -m "docs(release): document npm publish process"
git commit -m "test(cli): cover config loading failures"
```

Prefer a concise message that explains why the change exists, not a mechanical
list of edited files.

## Stage and commit

Stage relevant files explicitly:

```bash
git add  
```

Commit with the selected message:

```bash
git commit -m ""
```

If hooks or formatting modify files, inspect the result with `git status --short`
and create a new commit attempt after staging the hook changes. Do not amend
unless the user explicitly asked for an amend.

## After commit

Verify the commit succeeded:

```bash
git status --short
git log -1 --oneline
```

Report:

- The commit hash and message.
- Any verification run.
- Any files intentionally left uncommitted.
- Whether the branch was pushed, only if the user asked for a push.

## Source & license

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

- **Author:** [dynobox](https://github.com/dynobox)
- **Source:** [dynobox/dynobox](https://github.com/dynobox/dynobox)
- **License:** Apache-2.0
- **Homepage:** https://dynobox.xyz

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:** yes
- **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-dynobox-dynobox-commit
- Seller: https://agentstack.voostack.com/s/dynobox
- 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%.