Stage, commit, and push changes to the current branch. Use when asked to commit changes, push code, or after completing a task.
Stage all changes, create a commit with a conventional commit message, and push to the remote.
git status to see what files have changedgit diff to understand the changes (both staged and unstaged)git log --oneline -5 to see recent commit message stylegit addDo NOT modify the git author or add Co-Authored-By headers. The commit should use the user's existing git configuration (their name and email from git config user.name and git config user.email).
Use conventional commits style observed in the repository:
feat: for new featuresfix: for bug fixeschore: for maintenance tasksrefactor: for code refactoringdocs: for documentation changesKeep subject line under 72 characters. Focus on the "why" rather than the "what".
Always use a HEREDOC to ensure proper formatting:
git commit -m "$(cat <<'EOF'
<type>: <description>
<optional body explaining why>
EOF
)"
--force or --no-verify unless explicitly requestedAfter committing, push to the current branch:
git push origin HEAD
If the branch doesn't have an upstream, use:
git push -u origin HEAD