How do I install the Zoonk Commit skill?

Run npx skillmds@latest add tomevault-io/zoonk-commit in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Zoonk Commit safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Zoonk Commit?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Zoonk Commit free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Zoonk Commit?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Zoonk Commit by tomevault-io — Agent Skill

Name: Zoonk Commit
Author: tomevault-io

File contents

Commit Messages

Format

type(scope): short message

Types

feat - new feature
fix - bug fix
refactor - code refactoring
chore - maintenance tasks (deps, config, tooling)

Scopes

Use the owning app or package name as scope when working in this monorepo.

Scope Selection Order

If the change is fully owned by one app in apps/<name>, use that app name.
If the change is fully owned by one package in packages/<name>, use that package name.
Only use an inferred scope like deps, ci, or agents when the change truly spans multiple workspaces or does not belong to a single app/package.
Do not pick a scope based on the kind of code changed (eg data) when the files clearly belong to one app/package. The workspace owner wins.

Inferred scopes (when change doesn't fit an app/package):

agents - CLAUDE.md, AGENTS.md, .claude/ folder
ci - GitHub workflows, CI/CD configuration
deps - dependency updates across multiple packages

Good Scope Choices

fix(player): improve belt progress contrast for changes in packages/player/...
fix(main): correct level page copy for changes in apps/main/...
fix(api): handle null response in auth for changes in apps/api/...

Avoid These Mistakes

fix(ui): improve belt progress contrast when the change is in packages/player
fix(data): update main progress query when the change is only in apps/main
fix(ui): restyle main level card when the change is only in apps/main

Examples

feat(main): add user profile page
fix(player): improve belt progress contrast
fix(api): handle null response in auth
refactor(db): use enum for status field
chore(deps): update react to v19
chore(agents): add commit skill
fix(ci): update node version in workflow

Rules

Use lowercase for entire message
No period at the end
Keep message under 72 characters
Use imperative mood ("add" not "added")

PR Titles

Use the same type(scope): short message format as the commit title.

PR Descriptions

Keep descriptions brief. Focus on what changed. No need to list verification commands run.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: zoonk-commitdescription: Guidelines for writing commit messages and PR descriptions. Use when creating commits, writing PR descriptions, or asking about commit format. Use when this capability is needed.---# Commit Messages## Format```type(scope): short message```## Types- `feat` - new feature- `fix` - bug fix- `refactor` - code refactoring- `chore` - maintenance tasks (deps, config, tooling)## ScopesUse the owning app or package name as scope when working in this monorepo.### Scope Selection Order1. If the change is fully owned by one app in `apps/<name>`, use that app name.2. If the change is fully owned by one package in `packages/<name>`, use that package name.3. Only use an inferred scope like `deps`, `ci`, or `agents` when the change truly spans multiple workspaces or does not belong to a single app/package.4. Do not pick a scope based on the kind of code changed (eg `data`) when the files clearly belong to one app/package. The workspace owner wins.**Inferred scopes** (when change doesn't fit an app/package):- `agents` - CLAUDE.md, AGENTS.md, `.claude/` folder- `ci` - GitHub workflows, CI/CD configuration- `deps` - dependency updates across multiple packages### Good Scope Choices- `fix(player): improve belt progress contrast` for changes in `packages/player/...`- `fix(main): correct level page copy` for changes in `apps/main/...`- `fix(api): handle null response in auth` for changes in `apps/api/...`### Avoid These Mistakes- `fix(ui): improve belt progress contrast` when the change is in `packages/player`- `fix(data): update main progress query` when the change is only in `apps/main`- `fix(ui): restyle main level card` when the change is only in `apps/main`## Examples```feat(main): add user profile pagefix(player): improve belt progress contrastfix(api): handle null response in authrefactor(db): use enum for status fieldchore(deps): update react to v19chore(agents): add commit skillfix(ci): update node version in workflow```## Rules- Use lowercase for entire message- No period at the end- Keep message under 72 characters- Use imperative mood ("add" not "added")# PR TitlesUse the same `type(scope): short message` format as the commit title.# PR DescriptionsKeep descriptions brief. Focus on what changed. No need to list verification commands run.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/zoonk) — claim your Tome and manage your conversions.

Frequently asked questions

Zoonk Commit