push

Stage, commit, and push Git changes with secret detection.

2|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/soliblue/cloude --skill push-soliblue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: push
Source: https://github.com/soliblue/cloude/tree/main/.claude/skills/push
Command: npx skills add https://github.com/soliblue/cloude --skill push-soliblue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates committing and pushing changes to a Git repository without deploying, removing manual steps from the standard workflow.

Core Features & Use Cases

  • Automated commit workflow: Stage changes, create a conventional commit, and push to the remote.
  • Guided review & planning: Review changes, ensure sensitive data is not committed, and generate a plan ticket if none exists.
  • Safety and compliance: Stop when sensitive data is detected and require human review before proceeding.

Quick Start

Invoke the skill to commit and push changes. Example: push a new feature with a conventional commit message like feat: add authentication flow, then push to the remote repository.

Frequently Asked Questions about push

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

FAQPage Schema
How do I automate git commit and push without deploying?

To automate git commit and push without deploying, this Skill stages all modifications, creates a conventional commit, pushes to the remote repository, and performs a post-push plan ticket check. It removes manual steps from the standard workflow.

How does sensitive data scanning work before pushing code to Git?

Sensitive data scanning works by reviewing staged changes before committing and pushing to Git. If potential secrets are detected, the push is stopped immediately to require human review and ensure safety compliance.

What's the best way to generate conventional commit messages automatically?

The best way to generate conventional commit messages automatically is by using a guided workflow that reviews your staged changes and formats the commit, such as feat: add authentication flow, before pushing to the remote repository.

Can I use this to push code changes if I don't have a plan ticket?

Yes, you can push code changes without an existing plan ticket. The workflow includes a post-push plan ticket check that will generate a plan ticket if none exists, ensuring your changes are tracked.

Does git add . stage all modifications before committing?

Yes, git add . stages all modifications before committing. The structured workflow operates by staging all modifications, creating a conventional commit, and pushing to the remote repository.