ethereal-git-push

Push all modified files via the Git Data API when git push fails.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ferundatattoo/ethereal --skill ethereal-git-push
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ethereal-git-push
Source: https://github.com/ferundatattoo/ethereal/tree/main/.claude/skills/ethereal-git-push
Command: npx skills add https://github.com/ferundatattoo/ethereal --skill ethereal-git-push

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents push failures and file gaps in Git operations by leveraging the Git Data API to ensure every modified file is included in the push, avoiding index.lock stalls and partial commits.

Core Features & Use Cases

  • Index.lock resolution: transparently switches to the Git Data API when standard git push is blocked by index.lock.
  • Complete push guarantees: ensures all changed files are included in the push to avoid mega-push gaps.
  • Cross-ecosystem workflows: supports pushes across GitHub, Git Data API endpoints, CI/CD pipelines, and automated deployments.

Quick Start

Follow this protocol when a standard git push fails or index.lock blocks operations to push all changed files via the Git Data API.

Frequently Asked Questions about ethereal-git-push

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

FAQPage Schema
How do I fix git push failures caused by an index.lock file?

Resolve index.lock stalls by switching from standard git push to the Git Data API, which directly commits modified files and bypasses the blocked index to guarantee a complete push.

What is the best way to prevent file omissions during large multi-file git pushes?

To prevent file omissions during large multi-file pushes, use the Git Data API to enumerate and verify all modified files individually, ensuring every change is included in the final commit and preserving the base_tree.

How do I push changed files via the Git Data API when standard git push fails?

Push changed files via the Git Data API by using a personal access token to authenticate, enumerating all modified files, creating a tree that preserves the base_tree, and committing changes directly through the endpoint.

Do I need a personal access token to use the Git Data API for pushing files?

Yes, using the Git Data API to push files requires a personal access token and repository access to authenticate, enumerate modified files, and verify complete pushes across GitHub and CI pipelines.

Can I use the Git Data API for pushes across CI/CD pipelines and automated deployments?

Yes, you can use the Git Data API for pushes across CI/CD pipelines and automated deployments, ensuring complete file transfers across GitHub endpoints when standard git push operations fail.

Why does my standard git push fail with missing files in large multi-file commits?

Standard git push fails with missing files in large multi-file commits due to index.lock stalls or mega-push gaps, which the Git Data API mitigates by verifying every modified file is included while preserving the base_tree.