okhp3-replit-github-sync

Diagnose and safely recover Replit-to-GitHub synchronization failures using Git state inspection.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/OKHP3/telling-forward --skill okhp3-replit-github-sync-okhp3
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: okhp3-replit-github-sync
Source: https://github.com/OKHP3/telling-forward/tree/main/.agents/skills/okhp3-replit-github-sync
Command: npx skills add https://github.com/OKHP3/telling-forward --skill okhp3-replit-github-sync-okhp3

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Replit's Git UI can fail with errors like PUSH_REJECTED or a stuck commit button, leaving your workspace out of sync with GitHub. This Skill establishes the actual Git state, preserves local work, and follows an explicit, safe integration path instead of blindly retrying rejected pushes or force-pushing. ## Core Features & Use Cases - Sync Diagnosis: Records repository root, branch, remotes, and ahead/behind counts against the verified default branch before making any changes. - Safe Recovery Paths: Applies a decision table for behind-only, local-only, diverged, and conflicted states, using fast-forward pulls, reviewed commits, and normal pushes while refusing force-push or history rewriting. - PR and Squash Merge Handoff: Pushes feature branches, creates or updates pull requests, and performs explicitly authorized squash merges with verification of head SHA, approvals, and required checks. - Use Case: Replit reports "the remote has commits that are not in the local repository." The Skill fetches origin, shows the divergence, fast-forwards or routes work through a feature branch PR, then verifies the remote contains the expected commit. ## Quick Start Use the okhp3-replit-github-sync skill to diagnose this Replit checkout, safely reconcile it with GitHub, and verify the branch is synchronized.

Frequently Asked Questions about okhp3-replit-github-sync

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

FAQPage Schema
How do I fix PUSH_REJECTED when pushing from Replit to GitHub?▼

PUSH_REJECTED means the remote has commits your local checkout lacks. Fetch origin, compare ahead/behind counts with git rev-list --left-right --count, then fast-forward if behind-only or route diverged work through a feature branch pull request instead of force-pushing.

How to squash merge a Replit feature branch into main on GitHub?▼

Push the feature branch, create a pull request targeting the verified default branch, then verify the head SHA, approvals, and required checks. Squash merge only after explicit user authorization for that exact PR and strategy, never as a way to bypass a rejected push.

Can this Skill force-push or automatically resolve merge conflicts?▼

No. Force-push, history rewriting, reset, and automatic conflict resolution are explicitly out of scope. When conflicts or diverged shared history appear, it reports the exact state and the smallest safe next action for owner decision.

Does Replit GitHub sync require a connected GitHub integration?▼

A connected GitHub capability is optional. Local Git remains authoritative for the working tree; the connector is used only for hosted compare, pull-request, and merge actions when available, and its repository must match the local origin before any write.

Why does the Replit commit button get stuck and what should I check first?▼

A stuck commit usually signals underlying Git state issues rather than a UI problem. Inspect git status, remotes, merge or rebase state, conflict markers, and run git diff --check before staging anything, then commit only reviewed and authorized paths.