speckit-git-remote

To get the GitHub owner and repository name from a local Git remote URL, the tool reads your configured `remote.origin.url` via git config. It parses both HTTPS and SSH formats to extract the exact owner and repo details for GitHub integration workflows.

If Git is missing or no remote exists when parsing a repository, the detection process applies a graceful fallback. It reads `remote.origin.url` and returns an empty result with a warning instead of failing, ensuring your workflow continues without crashing.

Yes, you can detect if a Git remote points to GitHub using SSH or HTTPS formats. The parser reads the `remote.origin.url` from a valid work tree and supports both GitHub URL structures to accurately determine if the origin targets `github.com`.

You extract repository metadata from a working tree's origin remote by running git inside the valid work tree. The tool reads the `remote.origin.url` configuration, extracting the owner and repo name to use in GitHub issue creation or metadata enrichment.

GitHub remote detection requires running git inside a valid work tree with a configured `remote.origin.url`. It specifically checks if the origin URL targets `github.com` to safely parse the owner and repository name, returning empty results if the prerequisite environment is missing.

GitHub repository detection returns empty results without failing as a graceful fallback mechanism. When Git is unavailable, the directory isn't a repo, or no `remote.origin.url` is configured, it outputs empty data with a warning instead of throwing an error.