Airbrowser-mcp commit

Create conventional commit messages without co-author labels. Use when committing code changes or formatting git history.

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

Conventional Commit

Create conventional commit messages following the Conventional Commits specification. Never add co-author labels.

Format

<type>(<scope>): <subject>

<body>

Types

TypePurpose
feat
New feature
fix
Bug fix
refactor
Code restructuring (no behavior change)
docs
Documentation only
style
Formatting, whitespace (no code change)
test
Adding or fixing tests
chore
Build, CI, tooling, dependencies
perf
Performance improvement

Scope (optional)

Use the affected package or module as scope, matching this repo's conventions. Common scopes:

  • Package names:
    console-ui
    ,
    console-server
    ,
    cloud-router
    ,
    ai-engineer
    ,
    sheets-ui
  • Subsystems:
    billing
    ,
    scheduler
    ,
    auth
    ,
    mcp
  • Use the scope from recent commits when in doubt — run
    git log --oneline -20
    to check

Rules

  1. No co-author labels — never add
    Co-Authored-By
    lines
  2. Subject line: imperative mood, lowercase, no period, max 72 chars
  3. Body: explain why, not what. Wrap at 80 chars
  4. One logical change per commit — split unrelated changes
  5. Match the project's existing commit style (check recent history)

Steps

  1. Run
    git status
    and
    git diff --cached
    to see staged changes
  2. If nothing is staged, stage the relevant files (prefer specific files over
    git add -A
    )
  3. Analyze the changes and determine the appropriate type and scope
  4. Draft a concise commit message
  5. Create the commit using a HEREDOC for proper formatting:
    git commit -m "$(cat <<'EOF'
    type(scope): subject line here
    
    Optional body explaining why this change was made.
    EOF
    )"
    
  6. Run
    git status
    after to verify

Examples

feat(console-ui): add group chat with realtime subscriptions

fix(console-server): correct next_run calculation for scheduled reports

refactor(cloud-router): merge mcp server into main binary

chore: update ui-kit to v0.15.0 across packages

fix(ai-engineer): handle token limit exceeded in streaming response

perf(billing): batch usage dimension writes to reduce DB round-trips