From aiot-ai-agent-skills
AI-powered git workflow assistant. Generates conventional commit messages following Angular Commit Convention and runs pre-commit checks (lint, format, test). Use for: commit creation, atomic commit splitting, pre-commit validation, conventional commits, changelog generation, version bumping.
How this skill is triggered — by the user, by Claude, or both
Slash command
/aiot-ai-agent-skills:smart-commitThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Follow the [Angular Commit Convention](https://github.com/angular/angular/blob/main/CONTRIBUTING.md#commit):
Follow the Angular Commit Convention:
<type>(<scope>): <subject>
<body>
<footer>
| Type | Use When |
|---|---|
build | Build system or external dependencies |
ci | CI configuration |
docs | Documentation only |
feat | New feature |
fix | Bug fix |
perf | Performance improvement |
refactor | Neither fix nor feature |
style | Formatting, whitespace, semicolons |
test | Adding or correcting tests |
Subject: imperative present tense, no capital, no period, max 50 chars.
Scope: noun describing affected section (e.g., auth, api, core).
Body: explain what and why, wrap at 72 chars.
Footer: BREAKING CHANGE: or Fixes #123 / Closes #456.
Do NOT add "Co-Authored-By: Claude" or any AI attribution footer.
Split when: new construct, modification, config change, docs, refactor, bug fix, or test.
git status
git diff --cached --stat
git diff --cached
If no staged changes, offer to stage specific files.
Group changes into: new constructs, modifications, configuration, documentation, refactoring, bug fixes, tests. Each group becomes a separate commit.
## Auto-Commit Plan
I will create [N] commits in this order:
### Commit 1
**Message:** feat(auth): add user authentication endpoint
**Files:** [list]
After user confirmation, execute using HEREDOC:
git add [specific files]
git commit -m "$(cat <<'EOF'
<type>(<scope>): <subject>
<body if applicable>
<footer if applicable>
EOF
)"
git log --oneline -n [N]
git status
Analyze staged changes, categorize, identify split points, then output:
## Commit Split Recommendation
### Current staged changes span [N] logical units:
**Commit 1: `<type>: <description>`**
- Files: [list]
- Reason: [why separate]
### Suggested Execution Order:
1. [First commit - why first]
2. [Second commit - dependency]
### Commands to Execute:
[exact git commands]
See references/precommit.md for the full pre-commit workflow including language detection, tool tables, commands per language, auto-fix, and git hooks setup.
See references/edge-cases.md for handling: no staged changes, single file with multiple concerns, merge conflicts, uncommitted dependencies, sensitive files, WIP code, and commit examples.
git push --force without explicit confirmationnpx claudepluginhub aiotnetwork/aiotaiagentskills --plugin aiot-ai-agent-skillsGuides systematic git commits: checks staging status, reviews diffs, splits changes into atomic commits, formats conventional messages. Use before PRs or when committing code.
Guides git commits with atomic change analysis, conventional commit messages, and interactive staging options. Flags non-atomic commits and suggests splits for better maintainability.
Git commit workflow pipeline: atomic unit identification, commit ordering, quality gates, message validation, and post-commit verification. Invoke whenever task involves any interaction with git commits — committing changes, staging work, splitting diffs into atomic units, or preparing work for version control.