How do I install the Auto Commit skill?

Run npx skillmds add majiayu000/auto-commit-2 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 Auto Commit safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

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

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

Who published Auto Commit?

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

Auto Commit by majiayu000 — Agent Skill

Name: Auto Commit
Rating: 4.5 (4 reviews)
Author: majiayu000

Auto Commit

Automatically commits changes using conventional commits format (feat:, fix:, docs:, chore:, refactor:, test:, style:). Use after completing bug fixes, feature implementations, or documentation updates. Triggered automatically via Stop hook.

majiayu000 f02a144 2 files · 2.6 KB Updated Sep 9, 2026 567 repo stars

File contents

Auto-Commit with Conventional Commits

Automatically stage and commit changes using the conventional commits specification.

Conventional Commits Format

<type>(<scope>): <description>

[optional body]

Commit Types

Type	When to Use
`feat`	New feature or functionality
`fix`	Bug fix
`docs`	Documentation only changes
`chore`	Maintenance (deps, configs, build)
`refactor`	Code restructuring without behavior change
`test`	Adding or modifying tests
`style`	Formatting, whitespace, linting
`perf`	Performance improvements
`ci`	CI/CD changes

Scope (Optional)

Add scope in parentheses for context:

feat(auth): add login endpoint
fix(api): handle null response
docs(readme): update install instructions

Commit Workflow

Check for changes: git status
If changes exist:
- Stage all: git add -A
- Review staged: git diff --staged
- Determine type from changes
- Write concise description (imperative mood)
- Commit with proper format

Message Guidelines

Use imperative mood: "add feature" not "added feature"
Keep first line under 72 characters
Don't end with period
Be specific but concise

Good Examples

feat(api): add user authentication endpoint
fix: resolve null pointer in payment processing
docs: update API usage examples
chore: upgrade dependencies to latest versions
refactor(db): extract query builder to separate module

Bad Examples

updated stuff          # Too vague
Fixed the bug.         # Don't end with period
Added new feature      # Wrong tense

Important

Only commit, do NOT push
Always use conventional commits format
Include scope when it adds clarity

---name: auto-commit-2description: Automatically commits changes using conventional commits format (feat:, fix:, docs:, chore:, refactor:, test:, style:). Use after completing bug fixes, feature implementations, or documentation updates. Triggered automatically via Stop hook.--- # Auto-Commit with Conventional Commits Automatically stage and commit changes using the conventional commits specification. ## Conventional Commits Format ``` <type>(<scope>): <description> [optional body] ``` ### Commit Types | Type | When to Use | |------|-------------| | `feat` | New feature or functionality | | `fix` | Bug fix | | `docs` | Documentation only changes | | `chore` | Maintenance (deps, configs, build) | | `refactor` | Code restructuring without behavior change | | `test` | Adding or modifying tests | | `style` | Formatting, whitespace, linting | | `perf` | Performance improvements | | `ci` | CI/CD changes | ### Scope (Optional) Add scope in parentheses for context: - `feat(auth): add login endpoint` - `fix(api): handle null response` - `docs(readme): update install instructions` ## Commit Workflow 1. Check for changes: `git status` 2. If changes exist: - Stage all: `git add -A` - Review staged: `git diff --staged` - Determine type from changes - Write concise description (imperative mood) - Commit with proper format ## Message Guidelines - Use imperative mood: "add feature" not "added feature" - Keep first line under 72 characters - Don't end with period - Be specific but concise ### Good Examples ``` feat(api): add user authentication endpoint fix: resolve null pointer in payment processing docs: update API usage examples chore: upgrade dependencies to latest versions refactor(db): extract query builder to separate module ``` ### Bad Examples ``` updated stuff # Too vague Fixed the bug. # Don't end with period Added new feature # Wrong tense ``` ## Important - Only commit, do NOT push - Always use conventional commits format - Include scope when it adds clarity

Frequently asked questions