commit-from-changes
Automates the generation of compliant Conventional Commit messages from current Git changes.
Install
mkdir -p .claude/skills/commit-from-changes && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15940" && unzip -o skill.zip -d .claude/skills/commit-from-changes && rm skill.zipInstalls to .claude/skills/commit-from-changes
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.
Usa esta skill para gerar uma mensagem de Conventional Commit a partir das alteracoes atuais de Git/GitHub e, opcionalmente, criar o commit.Key capabilities
- →Read `docs/commit-messages.md` for local commit message rules
- →Inspect Git changes using `git status --short` and `git diff`
- →Identify the main intention of changes for commit type selection
- →Choose commit type from `feat`, `fix`, or `docs`
- →Select an optional scope for easier commit localization
- →Format commit subject as `<type>[optional scope]: <description>`
How it works
The skill inspects Git changes, identifies the primary intention, selects an appropriate commit type and optional scope, and then formats a commit message according to Conventional Commit guidelines.
Inputs & outputs
When to use commit-from-changes
- →Generating commit messages
- →Formatting commits for CI/CD
- →Describing complex code changes
About this skill
Commit a partir das alteracoes
Gera uma mensagem de commit a partir das alteracoes atuais de Git, no formato do repositorio.
Fluxo de trabalho
- Le
docs/commit-messages.mdquando existir. Trata-o como a fonte local de verdade. - Inspeciona as alteracoes antes de escrever a mensagem:
- Corre
git status --short. - Da prioridade ao diff em stage com
git diff --cached --stategit diff --cached. - Se nada estiver em stage, inspeciona alteracoes fora de stage com
git diff --stategit diff. - Inclui ficheiros nao seguidos lendo os respetivos caminhos e conteudos relevantes.
- Corre
- Identifica a intencao principal da alteracao. Se existirem varias intencoes nao relacionadas, recomenda commits separados em vez de forcar uma mensagem vaga.
- Escolhe o tipo de commit:
feat: nova funcionalidade.fix: correcao de uma anomalia.docs: alteracoes apenas na documentacao.
- Escolhe um scope opcional apenas quando tornar o commit mais facil de localizar, como
readme,tickets,ci,docsoutests. - Escreve o assunto exatamente neste formato:
<type>[optional scope]: <description>
- Mantem a descricao curta, concreta e em portugues quando a documentacao do repositorio estiver em portugues.
- Acrescenta corpo apenas quando for util para explicar contexto, impacto ou decisao. Mantem-no conciso e separado do assunto por uma linha em branco.
- Acrescenta rodapes apenas quando aplicavel:
BREAKING CHANGE: <description>para quebras de compatibilidade.Resolve: #123para referencias a issues.
- Se o utilizador pedir para criar o commit, coloca em stage apenas os ficheiros pretendidos e depois corre
git commitcom a mensagem gerada. Nao coloques ficheiros nao relacionados em stage.
Saida
Quando estiveres apenas a gerar a mensagem, devolve apenas a mensagem de commit proposta num bloco text, seguida de uma nota curta se os ficheiros parecerem nao relacionados ou arriscados.
Regras
Nao inventes numeros de issues, quebras de compatibilidade ou scopes. Nao facas amend, reset, squash, rebase ou push salvo se o utilizador o pedir explicitamente.
When not to use it
- →When not generating Conventional Commit messages
- →When not working with Git/GitHub changes
- →When not needing to create a commit
Limitations
- →Does not invent issue numbers, breaking changes, or scopes
- →Does not perform `amend`, `reset`, `squash`, `rebase`, or `push` unless explicitly requested
- →Prioritizes staged changes over unstaged changes
How it compares
This workflow automates the generation of Conventional Commit messages based on actual Git changes, ensuring adherence to repository standards and reducing manual effort in crafting commit descriptions.
Compared to similar skills
commit-from-changes side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| commit-from-changes (this skill) | 0 | 1mo | 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.