speckit-git-remote

Detect GitHub owner and repository from the local Git origin remote URL.

Updated May 3, 2026
One-click install
npx skills add https://github.com/tykhoncode/dicekit --skill speckit-git-remote-tykhoncode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-remote
Source: https://github.com/tykhoncode/dicekit/tree/main/.claude/skills/speckit-git-remote
Command: npx skills add https://github.com/tykhoncode/dicekit --skill speckit-git-remote-tykhoncode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of reliably determining which GitHub repository a project is connected to by reading the configured Git remote, so GitHub-dependent workflows (like issue creation) can run with the correct owner and repo.

Core Features & Use Cases

  • Detects Git repository presence: checks whether the current directory is inside a Git work tree and whether Git is available.
  • Extracts origin remote URL: reads the configured remote.origin.url value to identify repository location.
  • Safely parses GitHub ownership: supports HTTPS and SSH formats and only reports GitHub when the remote URL actually points to github.com.

Quick Start

Use the speckit-git-remote skill to detect the GitHub owner and repository name from your current project's configured 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 find the GitHub repository owner and name from a local Git remote?

To find the GitHub repository owner and name, you can read the configured Git origin remote URL. This process safely parses both HTTPS and SSH formats pointing to github.com to extract the exact owner and repository name for your automation workflows.

Can I use Git remote URL detection for GitHub issue automation?

Yes, Git remote URL detection is built specifically for GitHub issue automation scenarios. By extracting the repository owner and name from the origin remote, it provides the necessary repository context required to programmatically create and manage GitHub issues.

How do I check if a directory is a Git repository before reading the remote?

To check if a directory is a Git repository, the process verifies Git availability and whether the current directory is inside a Git work tree. This ensures safe remote URL extraction and prevents errors when Git or configured remotes are missing.

What happens when Git is not installed or the origin remote is missing?

When Git is not installed or the origin remote is missing, the remote detection process provides a graceful empty output. This ensures your integration workflows do not crash when repository context cannot be resolved from the local environment.

Does Git origin remote parsing support both SSH and HTTPS GitHub formats?

Yes, Git origin remote parsing supports both SSH and HTTPS URL formats. It specifically validates that the parsed remote URL points to github.com before extracting the repository owner and name, ignoring other Git hosting providers.

Why does my GitHub repository detection return empty for non-GitHub remotes?

GitHub repository detection returns empty for non-GitHub remotes because it only reports ownership when the origin URL actually points to github.com. This prevents incorrect repository context from being passed into GitHub-specific issue integration workflows.