OpenSkillIndex← back to search
claude-code

Awesome-omni-skill zoonk-commit

Guidelines for writing commit messages and PR descriptions. Use when creating commits, writing PR descriptions, or asking about commit format.

install
source · Clone the upstream repo
git clone https://github.com/diegosouzapw/awesome-omni-skill
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skill "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/development/zoonk-commit-zoonk" ~/.claude/skills/diegosouzapw-awesome-omni-skill-zoonk-commit && rm -rf "$T"
manifest: skills/development/zoonk-commit-zoonk/SKILL.md
source content

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 app or package name as scope when working in a monorepo:

Apps: 

web
, 
mobile
, 
api
, 
admin
, 
docs

Packages: 

ui
, 
utils
, 
core
, 
db
, 
config

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
  • data
    - data layer changes spanning multiple packages

Examples

feat(web): add user profile page
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 Descriptions

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