speckit-git-remote

Detect the GitHub repository owner and name from the configured Git remote URL.

Updated Dec 20, 2023
One-click install
npx skills add https://github.com/Thiago-Cruz-eng/Hibrygame --skill speckit-git-remote-thiago-cruz-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-remote
Source: https://github.com/Thiago-Cruz-eng/Hibrygame/tree/main/.claude/skills/speckit-git-remote
Command: npx skills add https://github.com/Thiago-Cruz-eng/Hibrygame --skill speckit-git-remote-thiago-cruz-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit-git-remote solves the problem of identifying the correct GitHub repository owner and name by reading the current project's configured Git remote URL, enabling downstream GitHub-related workflows.

Core Features & Use Cases

  • Remote URL detection: Reads the origin remote URL from the local Git configuration to determine the repository context.
  • GitHub parsing (safe reporting): Extracts owner and repo name only when the remote actually points to github.com, avoiding incorrect assumptions.
  • Graceful fallback: Returns empty results when Git is missing, the directory is not a Git repo, or no remote is configured, preventing workflow failures.

Use case: When creating issues or linking artifacts in GitHub, you can automatically infer the target repository from the developer’s current clone.

Quick Start

Run the skill in your spec-kit project directory to detect the GitHub owner and repository name from the configured origin 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 detect the GitHub repository owner and name from a Git remote URL?

To detect the GitHub repository owner and name, the skill executes git config --get remote.origin.url and parses HTTPS or SSH URL formats pointing to github.com, returning the extracted details for automation workflows.

Can I automatically infer the target GitHub repository from my current project clone?

Yes, you can automatically infer the target GitHub repository from your current clone by running the skill in a Git working tree, which reads the origin remote URL to identify the repository context.

What happens if Git is unavailable or no remote is configured when detecting a repository?

When Git is unavailable or no remote is configured, the detection process returns empty output with warnings instead of failing, ensuring graceful fallback for integration workflows.

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

Yes, the repository detection skill supports both SSH and HTTPS GitHub URL formats, parsing the origin remote URL to safely extract owner and repository name only when it points to github.com.

Why does my GitHub issue creation automation fail to identify the correct repository context?

Your GitHub issue creation automation may fail to identify the correct repository context if the directory is not a Git working tree, Git is missing, or the origin remote points to a non-github.com host.