speckit-git-remote

Parse Git remote URLs to identify GitHub owner and repository name.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/omerkllm/edris-antigravity --skill speckit-git-remote-omerkllm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-remote
Source: https://github.com/omerkllm/edris-antigravity/tree/main/.agent/skills/speckit-git-remote
Command: npx skills add https://github.com/omerkllm/edris-antigravity --skill speckit-git-remote-omerkllm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detect and resolve the Git remote URL to determine if a repository is hosted on GitHub and extract the owner and repository name for integration tasks.

Core Features & Use Cases

  • Detects and parses the git remote.origin.url to identify repository owner and name.
  • Determines whether the remote points to a GitHub-hosted repository.
  • Supports both HTTPS and SSH remote URLs for GitHub.

Quick Start

Run the speckit-git-remote workflow to fetch the git remote URL and determine the GitHub repository.

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?

This skill parses the local git remote URL to extract the GitHub repository owner and name. It reads the remote.origin.url in both HTTPS and SSH formats to identify repository details for integration tasks.

Does this git remote parser support both SSH and HTTPS URL formats?

Yes, the git remote parser supports both HTTPS and SSH remote URLs for GitHub. It detects the remote.origin.url format and resolves the owner and repository name regardless of which protocol your local repository uses.

What happens if my git remote does not point to a GitHub repository?

If your git remote does not point to GitHub, the parser gracefully handles the non-GitHub remote. It checks the GitHub status and reports the owner and repository name without failing on non-Git or non-GitHub repositories.

When do I need to resolve a git remote URL for GitHub integration?

You need to resolve a git remote URL when performing GitHub integration, issue creation, or automation tasks. Extracting the owner and repository name from the remote.origin.url enables these downstream development workflows to target the correct repository.

Can I use this to automate GitHub issue creation from a local repository?

Yes, identifying the GitHub repository owner and name from your local git remote supports issue creation workflows. By parsing the remote.origin.url, you can dynamically resolve the target repository for automated GitHub integration tasks.