skills.rest
zhu637882-stack
zhu637882-stackCOMMUNITY
Explore all skills by this author →
GitHub

git-push

Automate GitHub pushes using a temporary Personal Access Token.

1|Updated Apr 6, 2026
Search Tags:#automation#git#devops#security#github#push#token
One-click install
npx skills add https://github.com/zhu637882-stack/jiaoyi --skill git-push-zhu637882-stack
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-push
Source: https://github.com/zhu637882-stack/jiaoyi/tree/main/.qoder/skills/git-push
Command: npx skills add https://github.com/zhu637882-stack/jiaoyi --skill git-push-zhu637882-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates pushing project code to GitHub while securely managing Personal Access Tokens and cleaning up credentials after push.

Core Features & Use Cases

  • Automated Git push workflow: checks status, commits changes, and updates the remote URL using a temporary token.
  • Secure token handling: prompts for a PAT, applies it only for the push, then reverts the remote URL to remove credentials.
  • Use cases: publishing code to the main branch, syncing feature branches, and recovering from failed pushes with safe rollback.

Quick Start

Push your latest local changes to the main branch on GitHub, providing a temporary Personal Access Token when prompted.

Frequently Asked Questions about git-push

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

FAQPage Schema
How do I push code to GitHub using a temporary Personal Access Token securely?▼

To push code securely, this workflow automates applying a temporary Personal Access Token to the remote URL, executing the push, and then immediately reverting the URL to remove credentials.

What is the best way to automate a git push without leaving credentials in the remote URL?▼

The best way to automate a secure git push is to prompt for a token, temporarily update the remote URL, push the changes, and then automatically clean up the credentials from the configuration.

How does secure token handling work when syncing local feature branches to multiple remotes?▼

Secure token handling works by temporarily injecting the token into the remote URL during the push, then automatically rolling back the URL to ensure credentials are not persisted in the local repository.

Can I recover from a failed GitHub push if my credentials expire during the workflow?▼

Yes, you can recover from a failed push because the workflow safely reverts the remote URL after attempting to push, preventing broken authentication states and allowing for a safe rollback.

Does this automation handle checking local changes and committing before pushing to the main branch?▼

Yes, the automated workflow checks your local status, commits changes, and updates the remote URL using a temporary token to safely publish code to the main branch on GitHub.

Why should I clean up credentials after pushing instead of storing my GitHub token locally?▼

You should clean up credentials after pushing to prevent unauthorized access if your local machine is compromised, ensuring your GitHub token is only applied temporarily and not stored in the remote URL.

Related Skills

Explore More Software Engineering Skills→
dtsongdtsong
1

Git Sync

Fetches Git remote changes and displays local branch status vs upstream tracking branch.

Community
Intermediate
B4sanB4san

ci-deploy

Automate CI/CD pipelines, deployments, and post-deployment verification.

Community
Advanced
plot-pmplot-pm
2

plot-idea

Create a plan branch, plan file, and draft pull request in Plot.

Official
Intermediate
JansenAnalyticsJansenAnalytics
5

ssh-remote

Automates SSH remote server management, SCP/Rsync transfers, and tunnel setup with key handling and scripted commands.

Community
Intermediate