git-save

Commit and push Git changes with conventional commits and secret checks.

Updated May 8, 2026
One-click install
npx skills add https://github.com/freire19/Mythos --skill git-save-freire19
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-save
Source: https://github.com/freire19/Mythos/tree/main/skills/git-save
Command: npx skills add https://github.com/freire19/Mythos --skill git-save-freire19

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the hassle of manually preparing a safe Git workflow by combining synchronization, staging, committing with conventions, and pushing to the remote.

Core Features & Use Cases

  • Unified commit or per-package commits: Creates either a single commit for the whole repo or multiple scoped commits per component when release-please uses separate pull requests.
  • Repo-safe execution with guardrails: Fetches and pulls the latest remote changes before committing, checks for sensitive files, and blocks commits that would include unprotected secrets.
  • Conventional Commits + clear release-please alignment: Uses conventional commit types and structured scopes, then pushes to the current branch.

Quick Start

Run git-save when you want to commit and push your changes, for example after you update a feature branch with code modifications.

Frequently Asked Questions about git-save

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

FAQPage Schema
How do I commit and push changes safely without accidentally exposing secrets?▼

To commit and push safely, you can use a workflow that stages only intended files and validates secret protection via .gitignore checks before pushing to the current branch without force.

How do I create per-package commits in a monorepo using release-please?▼

To create per-package commits in a monorepo, the workflow splits commits by package when release-please is configured to use separate pull requests, ensuring structured scopes for each component.

What is the best way to automate conventional commits and push in one step?▼

The best way to automate conventional commits is to use a workflow that applies conventional commit types and structured scopes, then pushes to the current branch in a single action.

Does this Git workflow fetch remote changes before committing to prevent conflicts?▼

Yes, the Git workflow fetches and pulls the latest remote changes before committing to ensure correctness and prevent conflicts, then stages only intended files for the commit.

Can I use this commit and push workflow for both simple repositories and monorepos?▼

Yes, you can use this commit and push workflow for both simple repositories and monorepos, creating either a single commit for the whole repo or multiple scoped commits per component.

Why should I not use force push when updating a feature branch with this workflow?▼

You should not force push because the workflow ensures correctness by pushing to the current branch without force, protecting the remote history from being overwritten after fetching and pulling.