skills.rest
ebecerra-developer
ebecerra-developerCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

git-workflow

Automates git commit and push workflows using file-based commit messages.

Updated Mar 6, 2026
Search Tags:#git#workflow#version control#commit#push#commit message#heredoc
One-click install
npx skills add https://github.com/ebecerra-developer/ebecerra-web --skill git-workflow-ebecerra-developer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/ebecerra-developer/ebecerra-web/tree/main/.agents/skills/git-workflow
Command: npx skills add https://github.com/ebecerra-developer/ebecerra-web --skill git-workflow-ebecerra-developer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? The heredoc syntax git commit -m "$(cat <<'EOF'...)" fails in this environment, breaking multi-line commit messages. This Skill provides a reliable workaround by writing commit messages to a temporary file and committing with git commit -F. ## Core Features & Use Cases - Heredoc Workaround: Writes commit messages to a temporary file with the Write tool, then commits via git commit -F commit-msg.txt and cleans up the file. - Commit Conventions: Enforces Spanish-language, imperative-style messages ("Añadir X", "Corregir Y") with a Claude co-author trailer. - Safe Git Practices: Pushes immediately after each commit, favors frequent small commits, and forbids git add -A, --amend, and --no-verify. - Use Case: When finishing a feature change, stage specific files by name, write the Spanish commit message to a file, commit with -F, and push in one autonomous flow. ## Quick Start Commit my staged changes with a descriptive Spanish message and push them immediately using the file-based commit workflow.

Frequently Asked Questions about git-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I commit with a multi-line git message when heredoc fails?▼

Write the commit message to a temporary file such as commit-msg.txt, then run git commit -F commit-msg.txt and delete the file afterward. This avoids the heredoc syntax that fails in this environment.

Why does git commit -m with heredoc fail in some environments?▼

The heredoc pattern git commit -m "$(cat <<'EOF'...)" fails in certain shell or tool environments due to quoting and command substitution handling. Using git commit -F with a message file is a reliable alternative.

How do I add a co-author to a git commit message?▼

Append a Co-Authored-By trailer at the end of the commit message, for example Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>. GitHub recognizes this trailer and attributes the commit to both authors.

Why should I avoid git add -A when staging changes?▼

git add -A stages every modified file, which risks committing secrets, large binaries, or unintended files. Adding files by explicit name gives you control over exactly what enters each commit.

When is it safe to use git commit --amend?▼

Amending rewrites history and should only be done on explicit user request, especially after pushing. This workflow forbids --amend and --no-verify by default to keep history and hooks intact.

Related Skills

Explore More Software Engineering Skills→
tldrawtldraw
50.1k

commit-changes

Creates a conventional git commit for staged and unstaged working tree changes.

Official
Basic
greencmgreencm
1

land-and-deploy

Merge pull requests, run CI tests, and deploy to production with canary checks.

Community
Advanced
owenlamontowenlamont
1

python-lint-format

Automate Python code linting and formatting with pre-commit hooks.

Community
Advanced
paywherebpaywhereb

squash

Squash all branch commits into one via interactive git rebase.

Official
Intermediate