speckit-git-remote

Parse Git remote URLs to output owner, repo, and GitHub flag.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify the Git remote URL from a local repository to enable GitHub integration workflows such as issue creation and repo linking.

Core Features & Use Cases

  • Detects the remote URL via git config and parses owner and repository from github.com URLs.
  • Determines whether the remote points to a GitHub repository to drive GitHub-specific automation.
  • Use case: automatically verify repository ownership before creating GitHub issues or linking to services.

Quick Start

Run the script against your local repository to fetch the configured remote URL and output the owner, repository, and a GitHub-match flag.

Frequently Asked Questions about speckit-git-remote

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

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

To parse the GitHub owner and repository from a git remote URL, the skill reads the remote configuration via git config and extracts the owner and repo details from github.com URLs, emitting the parsed values.

Can I check if a local git repository points to a GitHub remote?

Yes, you can verify if a local git repository points to GitHub by reading the remote URL through git config and evaluating the domain to emit a boolean is_github flag indicating a match.

How do I automatically detect the git remote URL for GitHub issue automation?

To detect the git remote URL for GitHub issue automation, run the script against your local repository to fetch the configured remote URL and output the owner, repository, and a GitHub-match flag.

What is needed to identify remote repository details before linking GitHub services?

Identifying remote repository details requires running the script within a local git repository to read the configured remote URL via git config, enabling workflows like issue creation and service linking.

Does this git remote parsing approach work for non-GitHub repository URLs?

The approach reads the remote URL via git config and parses owner and repo from github.com URLs, determining whether the remote points to a GitHub repository to drive GitHub-specific automation.

Why use a dedicated script to extract owner and repo from a GitHub remote instead of manual checks?

Using a dedicated script to extract owner and repo from a GitHub remote automates the verification of repository ownership, ensuring accurate parsing before creating issues or linking to services.