How do I install the Aif Commit skill?

Run npx skillmds add majiayu000/aif-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 Aif Commit safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Aif 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 Aif Commit free to use?

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

Who published Aif Commit?

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

Aif Commit by majiayu000 — Agent Skill

Name: Aif Commit
Rating: 4.666666666666667 (3 reviews)
Author: majiayu000

Aif Commit

Create conventional commit messages by analyzing staged changes. Generates semantic commit messages following the Conventional Commits specification. Use when user says "commit", "save changes", or "create commit".

majiayu000 356a95b 2 files · 3.8 KB Updated Sep 9, 2026 567 repo stars

File contents

Conventional Commit Generator

Generate commit messages following the Conventional Commits specification.

Workflow

Analyze Changes
- Run git status to see staged files
- Run git diff --cached to see staged changes
- If nothing staged, show warning and suggest staging
Determine Commit Type
- feat: New feature
- fix: Bug fix
- docs: Documentation only
- style: Code style (formatting, semicolons)
- refactor: Code change that neither fixes a bug nor adds a feature
- perf: Performance improvement
- test: Adding or modifying tests
- build: Build system or dependencies
- ci: CI configuration
- chore: Maintenance tasks
Identify Scope
- From file paths (e.g., src/auth/ → auth)
- From argument if provided
- Optional - omit if changes span multiple areas
Generate Message
- Keep subject line under 72 characters
- Use imperative mood ("add" not "added")
- Don't capitalize first letter after type
- No period at end of subject

Format

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

<body>

<footer>

Examples

Simple feature:

feat(auth): add password reset functionality

Bug fix with body:

fix(api): handle null response from payment gateway

The payment API can return null when the gateway times out.
Added null check and retry logic.

Fixes #123

Breaking change:

feat(api)!: change response format for user endpoint

BREAKING CHANGE: user endpoint now returns nested profile object

Behavior

When invoked:

Check for staged changes
Analyze the diff content
Propose a commit message
Ask for confirmation or modifications
Execute git commit with the message
After a successful commit, offer to push:
- Show branch/ahead status: git status -sb
- If the branch has no upstream, use: git push -u origin <branch>
- Otherwise: git push
- User choice:
  - Push now
  - Skip push

If argument provided (e.g., /aif-commit auth):

Use it as the scope
Or as context for the commit message

Important

Never commit secrets or credentials
Review large diffs carefully before committing
If staged changes contain unrelated work (e.g., a feature + a bugfix, or changes to independent modules), suggest splitting into separate commits:
1. Show which files/hunks belong to which commit
2. Ask for confirmation
3. Unstage all: git reset HEAD
4. Stage and commit each group separately using git add <files> + git commit
5. Offer to push only after all commits are done
NEVER add Co-Authored-By or any other trailer attributing authorship to the AI. Commits must not contain AI co-author lines

---name: aif-commitdescription: Create conventional commit messages by analyzing staged changes. Generates semantic commit messages following the Conventional Commits specification. Use when user says "commit", "save changes", or "create commit".--- # Conventional Commit Generator Generate commit messages following the [Conventional Commits](https://www.conventionalcommits.org/) specification. ## Workflow 1. **Analyze Changes** - Run `git status` to see staged files - Run `git diff --cached` to see staged changes - If nothing staged, show warning and suggest staging 2. **Determine Commit Type** - `feat`: New feature - `fix`: Bug fix - `docs`: Documentation only - `style`: Code style (formatting, semicolons) - `refactor`: Code change that neither fixes a bug nor adds a feature - `perf`: Performance improvement - `test`: Adding or modifying tests - `build`: Build system or dependencies - `ci`: CI configuration - `chore`: Maintenance tasks 3. **Identify Scope** - From file paths (e.g., `src/auth/` → `auth`) - From argument if provided - Optional - omit if changes span multiple areas 4. **Generate Message** - Keep subject line under 72 characters - Use imperative mood ("add" not "added") - Don't capitalize first letter after type - No period at end of subject ## Format ``` <type>(<scope>): <subject> <body> <footer> ``` ## Examples **Simple feature:** ``` feat(auth): add password reset functionality ``` **Bug fix with body:** ``` fix(api): handle null response from payment gateway The payment API can return null when the gateway times out. Added null check and retry logic. Fixes #123 ``` **Breaking change:** ``` feat(api)!: change response format for user endpoint BREAKING CHANGE: user endpoint now returns nested profile object ``` ## Behavior When invoked: 1. Check for staged changes 2. Analyze the diff content 3. Propose a commit message 4. Ask for confirmation or modifications 5. Execute `git commit` with the message 6. After a successful commit, offer to push: - Show branch/ahead status: `git status -sb` - If the branch has no upstream, use: `git push -u origin <branch>` - Otherwise: `git push` - User choice: - [ ] Push now - [ ] Skip push If argument provided (e.g., `/aif-commit auth`): - Use it as the scope - Or as context for the commit message ## Important - Never commit secrets or credentials - Review large diffs carefully before committing - If staged changes contain unrelated work (e.g., a feature + a bugfix, or changes to independent modules), suggest splitting into separate commits: 1. Show which files/hunks belong to which commit 2. Ask for confirmation 3. Unstage all: `git reset HEAD` 4. Stage and commit each group separately using `git add <files>` + `git commit` 5. Offer to push only after all commits are done - NEVER add `Co-Authored-By` or any other trailer attributing authorship to the AI. Commits must not contain AI co-author lines

Frequently asked questions