git-automation
Automates staging, conventional commit generation, and pushing code under project rules.
Install
mkdir -p .claude/skills/git-automation && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15284" && unzip -o skill.zip -d .claude/skills/git-automation && rm skill.zipInstalls to .claude/skills/git-automation
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Automate git add, Conventional Commit generation, commit validation, and push for RLApp feature branches under existing Git Flow guardrails.Key capabilities
- →Automate `git add` for workspace changes
- →Validate commit messages against standards
- →Push changes to feature branches
- →Confirm active branch matches `feature/*`
How it works
The skill automates the git commit process by staging files, generating a Conventional Commit message, validating it, and pushing changes to the feature branch. It ensures adherence to Git Flow guardrails.
Inputs & outputs
When to use git-automation
- →Automate commit message
- →Staging changed files
- →Push feature branch changes
About this skill
Git Automation
Use this skill when the workspace is ready to be committed from a valid feature branch.
Procedure
- Open the git automation checklist.
- Confirm the active branch matches
feature/*. - Detect workspace changes and stop if there are none.
- Generate or refine a Conventional Commit subject.
- Validate the message and block on any violation.
- Run
git add .,git commit, andgit push origin <feature-branch>only after all checks pass.
Output
- Branch validation
- Changed assets reviewed
- Generated or validated commit message
- Automation result
- Residual risks
When not to use it
- →When the workspace has no changes to commit
- →When the active branch is not a feature branch
- →When the user does not want Conventional Commit messages
Limitations
- →Requires the workspace to be ready for commit
- →Requires the active branch to match `feature/*`
- →Blocks on any commit message validation violation
How it compares
This skill automates the entire commit and push process with built-in Conventional Commit generation and validation, providing a standardized and error-checked workflow unlike manual git commands.
Compared to similar skills
git-automation side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| git-automation (this skill) | 0 | 4mo | No flags | Beginner |
| resolve-conflicts | 81 | 8mo | Review | Intermediate |
| openspec-onboard | 10 | 6mo | Review | Beginner |
| codex-cli-bridge | 9 | 9mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
resolve-conflicts
antinomyhq
Use this skill immediately when the user mentions merge conflicts that need to be resolved. Do not attempt to resolve conflicts directly - invoke this skill first. This skill specializes in providing a structured framework for merging imports, tests, lock files (regeneration), configuration files, and handling deleted-but-modified files with backup and analysis.
openspec-onboard
studyzy
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
codex-cli-bridge
alirezarezvani
Bridge between Claude Code and OpenAI Codex CLI - generates AGENTS.md from CLAUDE.md, provides Codex CLI execution helpers, and enables seamless interoperability between both tools
skill-sync
KyleKing
Syncs Claude Skills with other AI coding tools like Cursor, Copilot, and Codeium by creating cross-references and shared knowledge bases. Invoke when user wants to leverage skills across multiple tools or create unified AI context.
github-workflow-automation
ruvnet
Advanced GitHub Actions workflow automation with AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management
git-advanced-workflows
wshobson
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.