swain-push

Automate staging, committing, and pushing Git changes to a remote repository.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/cristoslc/tidegate --skill swain-push
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swain-push
Source: https://github.com/cristoslc/tidegate/tree/main/.agents/skills/swain-push
Command: npx skills add https://github.com/cristoslc/tidegate --skill swain-push

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the common Git workflow of staging all changes, creating a descriptive commit message based on the diff, committing the changes, and pushing them to the remote repository.

Core Features & Use Cases

  • Automated Git Workflow: Streamlines the process of saving and sharing code changes.
  • Intelligent Commit Messages: Generates conventional commit-style messages with summaries and author attribution.
  • Secret Handling: Identifies and excludes sensitive files from being committed.
  • Conflict Resolution Prompt: Guides the user on how to handle merge conflicts during a pull.
  • Use Case: After making several updates to a feature branch, you can use this Skill to quickly commit and push your work without manually typing each Git command.

Quick Start

Use the swain-push skill to stage, commit, and push your current Git changes.

Frequently Asked Questions about swain-push

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

FAQPage Schema
How do I automate staging, committing, and pushing Git changes?

To automate staging, committing, and pushing Git changes, this Skill handles the entire workflow by staging all differences, generating a conventional commit message, committing, and pushing to your remote repository automatically.

Can I generate conventional commit messages automatically from my Git diff?

Yes, you can generate conventional commit messages automatically from your Git diff. The Skill analyzes your staged and unstaged changes to create descriptive commit messages complete with summaries and AI co-authorship.

Does automated Git push handle merge conflicts during rebasing?

Yes, the automated Git push process supports rebasing and handles merge conflicts during a pull by providing a conflict resolution prompt to guide you through the necessary manual steps.

How are secrets and sensitive files excluded from an automated Git commit?

Secrets and sensitive files are excluded from an automated Git commit through built-in secret handling that identifies and prevents sensitive data from being staged and pushed to your remote repository.

What is the best way to verify a Git push to a remote repository?

The best way to verify a Git push is using the Skill's built-in post-push verification, which confirms your code changes were successfully uploaded to the remote repository and provides session bookmarking for your workflow.