---

name: git-pushing description: Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activates when user says "push changes", "commit and push", "push this", "push to github", or similar git workflow requests.

Git Push Workflow

Stage all changes, create a conventional commit, and push to the remote branch.

When to Use

Automatically activate when the user:

• Explicitly asks to push changes ("push this", "commit and push")
• Mentions saving work to remote ("save to github", "push to remote")
• Completes a feature and wants to share it
• Says phrases like "let's push this up" or "commit these changes"

Workflow

1. Check Status

Copygit status

2. Stage Changes

Copygit add -A

3. Create Conventional Commit

Use conventional commit format:

• feat: - New feature
• fix: - Bug fix
• docs: - Documentation changes
• chore: - Maintenance tasks
• refactor: - Code refactoring
• test: - Adding/fixing tests
• style: - Formatting changes

Example:

Copygit commit -m "feat: add user authentication flow"

4. Push to Remote

Copygit push -u origin main

Or for current branch:

Copygit push

Best Practices

• Review changes before committing: git diff
• Keep commits focused and atomic
• Write descriptive commit messages
• Use branch names that describe the work
• Push frequently to avoid large divergences