skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
aircury/ai-framework119 installs

commit-changes

Analyses git changed files in the workspace and makes atomic, functional, and semantic commits using conventional commits format. Use when the user asks to commit changes, create commits from staged/unstaged files, or organise working tree changes into meaningful commits.

How do I install this agent skill?

npx skills add https://github.com/aircury/ai-framework --skill commit-changes
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill provides instructions for semantic Git commit automation. It uses standard Git commands and does not perform any network operations or external downloads.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

What does this agent skill do?

When committing changes, follow this workflow:

  1. Analyze the workspace: Run git status and git diff (staged and unstaged) to understand all changes.

  2. Group changes semantically: Identify logical units of work. Each commit must be atomic — one functional change per commit. Group related files that together implement a single concern.

  3. Write conventional commit messages: Use the format <type>(<scope>): <description> without a body. Allowed types:

    • feat: new feature
    • fix: bug fix
    • refactor: code restructuring without behavior change
    • docs: documentation only
    • style: formatting, whitespace, semicolons (no logic change)
    • test: adding or updating tests
    • chore: tooling, configs, dependencies
    • perf: performance improvement
    • ci: CI/CD changes
    • build: build system changes
    • revert: reverting a previous commit

  4. Commit rules:

    • One-line messages only — never use a commit body.
    • Never include commit bodies, trailers, co-author lines, AI/tool attribution, generated-by markers, bot signatures, or metadata implying AI involvement.
    • Use git add for specific files per commit, never git add . unless all changes belong to one commit.
    • After each commit, run git log -1 --format=%B and verify the final message contains no AI-related attribution or metadata, then run git status to verify success.

  5. Execution order: Stage and commit one group at a time. Do not skip ahead.

How can the creator link this skill?

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/aircury/ai-framework/commit-changes">View commit-changes on skillZs</a>