agentleFS
Sign inStart free
opsmillopsmill/infrahub/.agents/skills/speckit-git-remote/SKILL.md

speckit-git-remote

Skill548 starsChanged 9 days agoApache-2.0View on GitHub

Detect Git remote URL for GitHub integration

35 other projects use a version of this, 32 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. 4 are common, 0 are distinctive, and 1 is very specific to this project.

  • 4

    Common

    Most of the 32 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check if Git is available by running git rev-parse --is-inside-work-tree 2>/dev/null

    line 18
  2. Common:

    If Git is not available, output a warning and return empty:

    line 19
  3. Common:

    Run the following command to get the remote URL:

    line 26
  4. Common:

    If Git is not installed, the directory is not a Git repository, or no remote is configured:

    line 50
  5. Common:

    Do NOT error — other workflows should continue without Git remote information

    line 52

“Common” is measured: kept by at least 6 in 10 of the 32 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

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: git@github.com:<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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free