push

Push code to Gitee and GitHub after validating eight pre-push checks.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/MJ-AgentLab/mj-agentlab-marketplace --skill push-mj-agentlab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: push
Source: https://github.com/MJ-AgentLab/mj-agentlab-marketplace/tree/main/plugins/mj-git/skills/mj-git-push
Command: npx skills add https://github.com/MJ-AgentLab/mj-agentlab-marketplace --skill push-mj-agentlab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures your code is pushed reliably to both GitHub and Gitee, preventing CI/CD failures due to remote access issues and maintaining code integrity through pre-push checks.

Core Features & Use Cases

  • Dual-Push Execution: Automatically pushes code to Gitee (mirror) and then GitHub.
  • Pre-Push Checklist: Enforces 8 critical checks including commit message format, branch naming, and CHANGELOG updates.
  • Error Handling: Provides clear guidance on common push errors and their resolutions.
  • Use Case: Before merging a new feature, use this skill to run all pre-push checks, push your code to both repositories, and ensure your CI pipeline can access the latest version from Gitee.

Quick Start

Run the push skill to execute the pre-push checklist and push your code to Gitee and GitHub.

Frequently Asked Questions about push

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

FAQPage Schema
How do I push code to both GitHub and Gitee at the same time?

Dual-push execution automatically mirrors your code to Gitee and then pushes to GitHub, ensuring both remote repositories receive your commits simultaneously for CI/CD compatibility.

What should I check before pushing code to a remote repository?

Before pushing code, run an 8-item pre-push validation checklist covering commit message format, branch naming conventions, and CHANGELOG updates to enforce branch discipline and maintain code integrity.

Why does my CI/CD pipeline fail to access the latest code after a git push?

CI/CD pipeline access failures often occur when remote synchronization is incomplete; utilizing a dual-push strategy to Gitee and GitHub ensures your CI pipeline reliably fetches the latest version from the Gitee mirror.

Do I need to use Git worktree and specific branch naming for dual-remote pushing?

Yes, successful dual-remote pushing requires adherence to specific branch naming conventions and Git worktree usage to enforce branch discipline and ensure the pre-push validation checklist passes.

What is the best way to automate code review checks before a git push?

Automating code review checks before a git push is best handled by enforcing a pre-push checklist that validates commit messages, verifies branch discipline, and confirms CHANGELOG updates prior to dual-remote synchronization.

How do I resolve common git push errors during dual-remote synchronization?

Resolving git push errors during dual-remote synchronization involves following provided error handling guidance, which addresses common push failures and their specific resolutions for Gitee and GitHub remote access.