Menu
Write a commit message following the Conventional Commits specification with scope and body
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | conventional-commit |
| description | Write a commit message following the Conventional Commits specification with scope and body |
| compatibility | >=1.4 |
Skill metadata: version "1.1"; license MIT; tags [git, commit, conventional-commits, changelog, versioning]; compatibility ">=1.4"; recommended tools [codebase, runCommands].
Write a well-structured commit message following the Conventional Commits specification.
Read the staged changes — Run git diff --cached --stat to see which files changed, then git diff --cached for the full diff.
Determine the type — Choose the most appropriate type:
| Type | When to use |
|---|---|
feat | A new feature or capability |
fix | A bug fix |
docs | Documentation-only changes |
style | Formatting, whitespace, semicolons — no logic change |
refactor | Code change that neither fixes a bug nor adds a feature |
perf | Performance improvement |
test | Adding or correcting tests |
build | Build system or external dependency changes |
ci | CI configuration changes |
chore | Maintenance tasks that don't modify src or test files |
Determine the scope — Identify the primary area affected (e.g., auth, api, ci, docs). Use the directory name or module name. Omit scope if the change spans many areas.
Write the subject line — Format: <type>(<scope>): <imperative summary>
Write the body (if the change is non-trivial):
Fixes #123, Closes #456Add breaking change footer (if applicable):
! after the type/scope: feat(api)!: remove v1 endpointsBREAKING CHANGE: <description of what breaks and migration path>Present the message — Show the complete commit message for user review:
<type>(<scope>): <subject>
<body>
<footer>
Wait for approval — Present the message and wait. Do not run git commit until the user approves or modifies the message.
Execute — Once the user approves, run:
git commit -m "<subject>" -m "<body>"
For multi-line messages with footers, use a heredoc or a temporary file to avoid shell escaping issues:
git commit -F - <<'EOF'
<type>(<scope>): <subject>
<body>
<footer>
EOF
Confirm the commit was created: git log --oneline -1
VS Code 1.110+ supports git.addAICoAuthor (enabled by default), which automatically appends a Co-authored-by: GitHub Copilot trailer to commits made with AI assistance. If this setting is enabled, the trailer is added automatically — you do not need to include it manually in the commit message.
To check or change the setting: search for git.addAICoAuthor in VS Code Settings.
! marker and BREAKING CHANGE: footergit log --oneline -1 confirms the commit was createdSet up and manage GitHub Actions workflows that use Copilot coding agents for automated PR handling and issue resolution
Inspect active GitHub Actions workflows before commit or push, run matching local checks for staged or unpushed files, ask which missing tools to install via askQuestions, and fix in-scope issues so the Commit agent can proceed.
Create an Architectural Decision Record (ADR) to document a significant design or technology choice
Audit VS Code extensions against the current project stack and recommend keep/add/remove actions
Diagnose and fix a failing CI pipeline or GitHub Actions workflow
Triage a GitHub issue by classifying severity, labelling waste category, proposing next action, and drafting a structured response