Git Push & Format Skill

Description

Formats git commit messages according to Conventional Commits specification and pushes changes to the remote repository. Use this when the user asks to commit changes, save progress, or upload code.

Triggers

"Запушь изменения" (Push changes)
"Сделай коммит" (Make a commit)
"Сохрани в гит" (Save to git)
"Сделай пуш" (Make a push)
"Запушь" (Push)

Format (Conventional Commits)

When writing a git commit message, you MUST follow this format: <type>[optional scope]: <description>

Allowed Types

feat: A new feature
fix: A bug fix
docs: Documentation only changes
style: Changes that do not affect the meaning of the code (white-space, formatting, etc)
refactor: A code change that neither fixes a bug nor adds a feature
perf: A code change that improves performance
test: Adding missing tests or correcting existing tests
chore: Changes to the build process or auxiliary tools and libraries

Instructions for Agent

Analyze the user's request or recent file changes to determine the type and description.
Construct the commit message string (e.g., "fix(auth): correct token validation").
Execute the bash script below, passing the generated message as an argument.

Execution

Run the following command (replace .YOUR_MESSAGE. with the formatted string):

/bin/bash .agent/skills/git-push/scripts/push_changes.sh "YOUR_MESSAGE"

Example Usage

If user says "I fixed the login bug", you execute: /bin/bash .agent/skills/git-push/scripts/push_changes.sh "fix(auth): resolve login error"

1.6 KiB Raw Blame History