speckit-git-remote

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

60|12|Updated Aug 1, 2013
One-click install
npx skills add https://github.com/vtex/front.phone --skill speckit-git-remote-vtex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-remote
Source: https://github.com/vtex/front.phone/tree/main/.agents/skills/speckit-git-remote
Command: npx skills add https://github.com/vtex/front.phone --skill speckit-git-remote-vtex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps integrations automatically determine whether a project is connected to a GitHub repository by detecting the configured Git remote URL.

Core Features & Use Cases

  • Detect Git remote URL: Reads the repository’s configured origin remote via Git configuration.
  • Parse owner and repo: Extracts the GitHub repository owner and name when the remote URL matches GitHub.
  • Graceful fallback: Avoids errors when Git is missing, the folder is not a Git repo, or no remote is configured.
  • Use Case: When creating issues or linking PRs to the correct GitHub repository, the integration can use detected owner/name instead of asking the user.

Quick Start

Ask an AI to run the speckit-git-remote skill on the current repository to return the detected GitHub remote owner and repository name (or an empty result if not available).

Frequently Asked Questions about speckit-git-remote

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

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

To detect a GitHub repository owner and name, run the skill on the current directory to execute git config --get remote.origin.url, parsing SSH and HTTPS formats to extract the metadata while returning empty results if Git is unavailable.

How does git remote URL detection work when Git is not installed or the folder is not a repository?

Git remote URL detection applies a graceful fallback by returning empty results without failing when Git is missing, the folder is not a Git repo, or no remote is configured, ensuring integration workflows continue without errors.

Can I use this to automatically link issues and PRs to the correct GitHub repository without user input?

Yes, you can automate GitHub issue and PR linking by using the detected repository owner and name extracted from the configured origin remote, bypassing the need to manually ask the user for repository metadata.

Does the remote detection skill support both HTTPS and SSH GitHub URL formats?

Yes, the remote detection skill supports both HTTPS and SSH GitHub URL formats, parsing the extracted remote.origin.url to accurately determine the repository owner and repository name for integration workflows.

What happens if git rev-parse fails during repository metadata discovery?

If git rev-parse fails during repository metadata discovery, the skill applies a graceful fallback and returns empty results instead of throwing errors, preventing integration workflows from breaking when detection is not possible.

What is the best way to extract repository metadata from a local Git configuration for integration workflows?

The best way to extract repository metadata is to run the skill to query the Git configuration for the remote.origin.url, parsing the output to return the GitHub repository owner and name for automated integration workflows.