speckit-git-remote

Extract GitHub repository owner and name from the origin remote URL.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/alienstro/mediapipe-scroll --skill speckit-git-remote-alienstro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-remote
Source: https://github.com/alienstro/mediapipe-scroll/tree/main/.agents/skills/speckit-git-remote
Command: npx skills add https://github.com/alienstro/mediapipe-scroll --skill speckit-git-remote-alienstro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you reliably determine the Git remote’s GitHub repository owner and name so downstream GitHub integrations (like issue creation) have the correct context.

Core Features & Use Cases

  • Git remote detection: Reads the configured origin remote URL from the local Git repository.
  • GitHub-safe parsing: Extracts owner and repo only when the remote URL explicitly points to github.com.
  • Graceful fallback: Returns empty output when Git is unavailable, the directory is not a Git repo, or no remote is configured.

Use case: You’re running an automated workflow from a local checkout and need to open/create issues in the correct GitHub repository without manually specifying the owner and repo each time.

Quick Start

Run the Skill in your project directory to output the GitHub owner and repository name derived from the origin remote URL.

Frequently Asked Questions about speckit-git-remote

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

FAQPage Schema
How do I get the GitHub repository owner and name from a Git remote URL?

To get the GitHub repository owner and name from a Git remote URL, the Skill reads the local origin remote URL and parses supported HTTPS and SSH GitHub formats to extract the specific owner and repository identifiers.

How do I automate GitHub issue creation using my local Git checkout?

Automating GitHub issue creation from a local Git checkout requires deriving the repository context by parsing the Git remote origin URL, which provides the necessary owner and name targets for the downstream GitHub integration workflow.

Does this Git remote parser work with SSH URLs or only HTTPS GitHub formats?

Yes, the Git remote parser works with both SSH and HTTPS GitHub URL formats. It safely extracts the owner and repository name specifically when the remote URL explicitly points to github.com.

What happens if Git is unavailable or the directory is not a repository?

If Git is unavailable, the directory is not a repository, or no remote is configured, the Git remote detection process applies a graceful fallback by returning empty output instead of failing or throwing an execution error.

Why do I need to extract GitHub repository metadata for workflow context?

Extracting GitHub repository metadata provides the necessary workflow context so downstream GitHub integrations like issue creation can target the correct repository automatically without manually specifying the owner and repo during each execution.