speckit-git-remote

Parse the Git remote URL to extract the GitHub repository owner and name.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detect the Git remote URL and extract repository information to enable GitHub integration workflows.

Core Features & Use Cases

  • Reads the Git remote URL from the local repository (remote.origin.url) and parses it to determine the repository owner, repository name, and whether the URL points to GitHub.
  • Supports HTTPS and SSH URL formats and gracefully handles cases when Git is unavailable or no remote is configured.
  • Use cases include routing automation to GitHub-specific tasks (e.g., issue creation, repository configuration) based on the detected owner/name.

Quick Start

Execute the remote URL check to extract the repository owner and repository name.

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 repository owner and name from a Git remote URL?

You can extract the GitHub repository owner and name by reading the local Git remote URL and parsing it. This identifies the origin and host to properly route automation actions based on the detected repository information.

Can I parse both SSH and HTTPS GitHub remote URLs?

Yes, you can parse both SSH and HTTPS GitHub remote URLs. The parsing mechanism supports both URL formats to accurately determine the repository owner and name regardless of the configured Git remote protocol.

Does the Git remote URL detection work if Git is unavailable or no remote is configured?

Git remote URL detection gracefully degrades to an empty result when Git is unavailable or no remote is configured. This ensures automation workflows handle missing repository origins without causing execution failures.

How do I verify repository origin to route GitHub automation tasks?

You verify repository origin to route GitHub automation tasks by checking the Git remote URL and parsing it into owner and repo components. This allows workflows to confirm GitHub integration targets before executing actions like issue creation.

What is the best way to check for Git availability before reading the remote URL?

The best way to check for Git availability before reading the remote URL is to use a detection mechanism that gracefully handles missing Git environments. It reads remote.origin.url only if Git is present, returning an empty result otherwise.