What problem does it solve? When automating GitHub workflows such as issue creation, you need to know which repository the current project points to. Manually inspecting Git configuration is error-prone, and assuming a GitHub remote when none exists breaks downstream integrations. ## Core Features & Use Cases - Remote URL Detection: Runs git config --get remote.origin.url to retrieve the configured remote for the current repository. - URL Parsing: Extracts the repository owner and name from both HTTPS (https://github.com/<owner>/<repo>.git) and SSH (git@github.com:<owner>/<repo>.git) formats. - GitHub Verification: Confirms whether the remote actually points to github.com instead of assuming it does. - Graceful Degradation: Returns an empty result with a warning when Git is unavailable, the directory is not a repository, or no remote is configured, so other workflows continue uninterrupted. - Use Case: A spec-kit automation needs to create a GitHub issue for a new feature specification; it first uses this Skill to resolve the correct owner and repository from the local Git configuration. ## Quick Start Ask the assistant to detect the Git remote URL of the current repository and report the GitHub owner and repository name.