speckit-git-remote

Detect Git remote URLs and extract GitHub owner and repository names.

2|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/d0whc3r/statsig-browser-extension --skill speckit-git-remote-d0whc3r
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-remote
Source: https://github.com/d0whc3r/statsig-browser-extension/tree/main/.trae/skills/speckit-git-remote
Command: npx skills add https://github.com/d0whc3r/statsig-browser-extension --skill speckit-git-remote-d0whc3r

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit users often need the GitHub owner/repo derived from their current repository so integrations like issue creation can use the correct identifiers automatically.

Core Features & Use Cases

  • Detect Git remote URL: Checks whether you are inside a Git work tree and reads the configured remote.origin.url.
  • Extract owner and repository name: Parses supported HTTPS and SSH remote URL formats to derive GitHub owner and repo.
  • Validate GitHub vs non-GitHub remotes: Reports GitHub details only when the remote actually targets github.com.

Quick Start

Run the skill to detect the GitHub owner and repository name from your current repository’s 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 extract the GitHub owner and repository name from a Git remote URL?

To extract the GitHub owner and repository name from a Git remote URL, parse the configured `remote.origin.url` by detecting the local Git work-tree context and handling both HTTPS and SSH GitHub URL formats.

Does Git remote URL parsing work for both SSH and HTTPS GitHub formats?

Yes, Git remote URL parsing works for both SSH and HTTPS GitHub formats by reading `remote.origin.url` and validating whether the target actually points to github.com before deriving the owner and repository name.

How to detect a GitHub repository from a local Git work tree for automation?

Detect a GitHub repository from a local Git work tree by invoking Git to check the work-tree context and read the `remote.origin.url`, returning empty results without errors when Git or remotes are unavailable.

Why does my GitHub integration fail when the remote is not github.com?

GitHub integration fails when the remote is not github.com because the detection logic validates GitHub details only when the remote actually targets github.com, ignoring non-GitHub remotes.

What happens if Git is unavailable or no remote is configured during repository detection?

If Git is unavailable or no remote is configured during repository detection, the process returns empty results without errors, ensuring your local automation and tooling workflows do not break.