speckit-git-remote

Read the Git remote URL and report owner, repository, and GitHub status.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detect and report the Git remote URL for a repository to verify GitHub integration and extract owner/repo information.

Core Features & Use Cases

  • Remote URL detection: Reads the git remote.origin.url when Git is available and the current directory is a Git repository.
  • GitHub verification: Determines if the remote points to github.com and extracts owner and repository name.
  • Graceful degradation: Returns an empty result if Git is not installed or no remote is configured, enabling downstream workflows to continue.

Quick Start

Run the speckit-git-remote tool inside a Git repository to retrieve the GitHub owner and repository name of the remote.

Frequently Asked Questions about speckit-git-remote

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

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

To get the GitHub owner and repository name from a Git remote URL, you can run a tool that reads the git configuration, parses remote.origin.url, and reports the extracted owner and repository details. This automates verifying GitHub integration.

What happens if Git is not installed or no remote is configured when checking a repository?

If Git is not installed or no remote is configured when checking a repository, the detection process returns an empty result. This graceful degradation enables downstream automation workflows to continue running without crashing due to missing Git remote URLs.

How can I verify if a local repository's origin points to GitHub in an automated workflow?

You can verify if a local repository's origin points to GitHub in an automated workflow by applying a tool that reads the Git configuration and checks the remote.origin.url. It determines if the remote points to github.com and reports the GitHub status.

Does Git remote URL detection work outside of a Git repository directory?

Git remote URL detection relies on reading the git remote.origin.url configuration. It is designed to run inside a Git repository directory, returning an empty result if Git is not available or the current directory is not a Git repository.

What is the best way to extract owner and repo details from a remote URL for DevOps tooling?

The best way to extract owner and repo details from a remote URL for DevOps tooling is to use an automated script that parses the Git configuration. It specifically reads remote.origin.url to identify the owner and repository name for GitHub integration.

Why does my automated workflow fail to verify GitHub integration from the Git remote?

Automated workflows fail to verify GitHub integration from the Git remote if Git is not installed, the current directory is not a Git repository, or no remote.origin.url is configured. The detection returns an empty result in these cases.