git-setup

Configure Git remotes to validate URLs and enforce consistent naming.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/captainsparrow10/LLM-ENGINEERS-HANDBOOK --skill git-setup-captainsparrow10
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-setup
Source: https://github.com/captainsparrow10/LLM-ENGINEERS-HANDBOOK/tree/main/.claude/skills/git-setup
Command: npx skills add https://github.com/captainsparrow10/LLM-ENGINEERS-HANDBOOK --skill git-setup-captainsparrow10

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you configure and verify Git remotes to ensure pushes go to the correct repository, preventing misdirected commits.

Core Features & Use Cases

  • Validate current remotes and correct misconfigurations
  • Automate switching origin/upstream to designated URLs
  • Preserve upstream references and prevent accidental pushes

Quick Start

Set the origin to the correct captainsparrow10 repository and verify the remote configuration.

Frequently Asked Questions about git-setup

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

FAQPage Schema
How do I verify Git remote URLs before pushing commits?

Verifying Git remote URLs involves checking the current remote configuration to ensure pushes target the correct repository. This skill validates existing remote URLs, suggests corrections for misconfigurations, and prevents accidental misdirected commits.

How do I switch origin and upstream remotes when updating a fork?

Switching origin and upstream remotes when updating a fork involves applying a workflow that automates switching origin/upstream to designated URLs. This preserves upstream references and enforces consistent remote naming through scripted commands to align your fork with upstream sources.

Why does my Git push go to the wrong repository after cloning?

Git pushes go to the wrong repository when remote URLs are misconfigured during cloning or forking. Validating current remotes and correcting misconfigurations ensures pushes target the correct repository, preventing accidental pushes to unintended sources.

Can I automate Git remote setup to prevent accidental pushes to upstream?

You can automate Git remote setup using scripted commands that enforce consistent remote naming and preserve upstream references. This approach validates remote URLs and prevents accidental pushes by ensuring your origin and upstream designations remain correctly aligned.

What is the best way to align a forked repository with upstream sources?

The best way to align a forked repository with upstream sources is to apply a remote configuration workflow that validates remote URLs and automates switching origin/upstream. This preserves upstream references while ensuring pushes target the correct forked repository.