speckit.git.remote — Claude Code command: what it does, install
speckit.git.remote detects the Git remote origin URL, parses repository ownership, and validates github.com hosts for downstream workflows.
MIT ★ 110 updated 2026-10-19
.claude/commands/speckit.git.remote.mdWhat speckit.git.remote does
The command verifies the current directory with git rev-parse --is-inside-work-tree and pulls the origin address using git config --get remote.origin.url. From there, it isolates the repository owner and project name. It recognizes standard HTTPS strings (https://github.com/<owner>/<repo>.git) as well as SSH paths ([email protected]:<owner>/<repo>.git).
Non-GitHub remotes will not be flagged as GitHub targets. That distinction matters: automation tasks such as issue creation rely strictly on github.com endpoints. If Git is absent or no remote origin exists, the prompt returns an empty result instead of throwing a fatal error.
What it helps with
- extract repository owner and name from remote origin URL
- verify whether origin points directly to github.com
- prepare repository parameters for GitHub issue automation
- handle non-Git folders without breaking parent agent steps
Example prompts for the agent
- Run
speckit.git.remoteto parse the remote URL of this project - Check with
speckit.git.remoteif the origin remote points to github.com - Execute
speckit.git.remoteand print the detected repository owner
How to install speckit.git.remote
Manually: put the files in place
.claude/commands/speckit.git.remote.mdCall it with /speckit.git.remote. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/speckit.git.remote.mdCall it with /prompts:speckit.git.remote. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/speckit.git.remote.prompt.mdManually: put the files in place
.gemini/commands/speckit.git.remote.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about speckit.git.remote
How to install speckit.git.remote in Claude Code?
Add the command file directly to your project under .claude/commands/speckit.git.remote.md.
What does speckit.git.remote do?
It reads the origin URL via Git, parses the owner and repo name, and checks if the remote points to GitHub.
Which Git remote formats are supported?
It handles HTTPS (https://github.com/<owner>/<repo>.git) and SSH formats ([email protected]:<owner>/<repo>.git).
Source text
speckit.git.remote.md · MIT
--- description: "Detect Git remote URL for GitHub integration" --- # Detect Git Remote URL Detect the Git remote URL for integration with GitHub services (e.g., issue creation). ## Prerequisites - Check if Git is available by running `git rev-parse --is-inside-work-tree 2>/dev/null` - If Git is not available, output a warning and return empty: ``` [specify] Warning: Git repository not detected; cannot determine remote URL ``` ## Execution Run the following command to get the remote URL: ```bash git config --get remote.origin.url ``` ## Output Parse the remote URL and determine: 1. **Repository owner**: Extract from the URL (e.g., `github` from `https://github.com/github/spec-kit.git`) 2. **Repository name**: Extract from the URL (e.g., `spec-kit` from `https://github.com/github/spec-kit.git`) 3. **Is GitHub**: Whether the remote points to a GitHub repository Supported URL formats: - HTTPS: `https://github.com/<owner>/<repo>.git` - SSH: `[email protected]:<owner>/<repo>.git` > [!CAUTION] > ONLY report a GitHub repository if the remote URL actually points to github.com. > Do NOT assume the remote is GitHub if the URL format doesn't match. ## Graceful Degradation If Git is not installed, the directory is not a Git repository, or no remote is configured: - Return an empty result - Do NOT error — other workflows should continue without Git remote information
© alfredoperez · MIT · alfredoperez/speckit-companion