git-teacher-upload

Push committed Git work to GitHub with beginner-friendly explanations.

114|19|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/fivetaku/gptaku-plugins-codex --skill git-teacher-upload-fivetaku
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-teacher-upload
Source: https://github.com/fivetaku/gptaku-plugins-codex/tree/main/plugins/git-teacher-codex/skills/git-teacher-upload
Command: npx skills add https://github.com/fivetaku/gptaku-plugins-codex --skill git-teacher-upload-fivetaku

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Push committed work to GitHub with beginner-friendly explanations, guiding users through validation checks and common errors so they can push confidently.

Core Features & Use Cases

  • Step-by-step push workflow with status checks to confirm a Git repository is ready for pushing, including verification of origin and a clean working tree.
  • Clear failure handling for cases like non-fast-forward, permission denied, or remote not found, with actionable remediation.
  • Browser URL translation of the remote to show where changes will appear on GitHub, plus suggested next steps (e.g., opening a PR).

Quick Start

Push your committed work to the connected GitHub repository.

Frequently Asked Questions about git-teacher-upload

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

FAQPage Schema
How do I push committed work from a local Git repository to GitHub?

To push committed work to GitHub, the repository must have a configured origin remote and a clean working tree. This Skill validates the repository state and runs git push origin HEAD, translating the remote URL to a browser link and explaining the outcome with next-step recommendations.

What does a non-fast-forward error mean when pushing to GitHub?

A non-fast-forward error during a GitHub push indicates remote commits are missing locally. This Skill detects non-fast-forward failures, permission denied, and missing remote errors, providing actionable remediation steps to resolve the conflict and push successfully.

How do I check if my local repository is ready for a git push?

Checking if a local repository is ready for a git push involves verifying a configured origin remote and a clean working tree. This Skill performs automated status checks before executing git push origin HEAD to ensure the workflow proceeds without environmental errors.

Can I get beginner-friendly guidance for resolving common git push issues?

Yes, you can get beginner-friendly guidance for resolving common git push issues. This Skill validates repository state, handles missing remotes or permission denied errors with clear explanations, and provides actionable next-step recommendations for beginners to push confidently.

Why does my git push fail with a missing remote not found error?

A git push fails with a remote not found error when the origin is missing or incorrectly configured. This Skill identifies missing remotes during validation and explains the remediation steps needed to configure the origin and push committed work to GitHub.