跳到正文
cccskills
免费在 GitHub 公开

speckit-git-remote

Detect Git remote URL for GitHub integration

中文简介正在准备中。当前显示原文说明。

集成工具GitHub
查看安装方法

包含的文件(1)

  • SKILL.md1.6 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

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

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Analyzes recent CI failures on pull requests to identify flaky tests, using retry outcomes (failed attempt → green re-run) and cross-PR recurrence as evidence, and maintains a local longitudinal ledger so flakiness can be tracked over time. TRIGGER when: the user wants to find flaky tests, correlate recent CI failures, check which tests fail across PRs or recover on retry, or refresh the flakiness trend report. DO NOT TRIGGER when: babysitting a single PR's CI until green → monitoring-pull-requests; diagnosing or fixing one specific failing test → the bug-analysis skills.

中文简介正在准备中。当前显示原文说明。

opsmill/infrahub5382026年10月17日 更新

Audits internal (dev/) and external (docs/) documentation completeness for a feature, subject, or set of existing docs, maps changes indicated by the user, across Infrahub's documentation layers, reports gaps, and optionally applies the fixes. TRIGGER when: the user wants to audit or check documentation coverage, find doc gaps after a feature branch, or verify docs are still current for a subject or specific files. DO NOT TRIGGER when: authoring new documentation from scratch → use the add-docs flow; only linting/formatting Markdown → run `uv run invoke docs.lint`.

中文简介正在准备中。当前显示原文说明。

opsmill/infrahub5382026年10月17日 更新

commit

免费

Stages and commits the current changes onto a safe working branch, enforcing branch discipline and optionally pushing upstream. TRIGGER when: the user wants to commit, save, or check in the current changes. DO NOT TRIGGER when: opening a pull request → pr.

中文简介正在准备中。当前显示原文说明。

opsmill/infrahub5382026年10月17日 更新

Use when you've fixed a bug, added a feature, or made any user-facing change in a project that uses Towncrier and need to record it for the changelog — before committing or opening a PR, or whenever asked to add a changelog entry, towncrier fragment, or news fragment.

中文简介正在准备中。当前显示原文说明。

opsmill/infrahub5382026年10月17日 更新

Turns a single feature idea, improvement, or bug into ONE well-structured GitHub issue. TRIGGER when: the user wants to file/open/create an issue, turn a feature idea or improvement into a ticket, or capture something missing or broken as a ticket. DO NOT TRIGGER when: breaking work into multiple issues or planning a body of work → a planning skill; writing a full Product Requirements Document → creating-prd; the idea is still fuzzy and unhardened → grilling-ideas first.

中文简介正在准备中。当前显示原文说明。

opsmill/infrahub5382026年10月17日 更新

Synthesises the current conversation context into a Product Requirements Document and publishes it to GitHub (as a comment on a referenced issue, or a new issue). Synthesises from context; does not interview. TRIGGER when: the conversation has produced enough understanding of a feature and the user wants it captured as a PRD. DO NOT TRIGGER when: a single small issue is enough → creating-issues; the idea has not been stress-tested yet → grilling-ideas first; bug reports.

中文简介正在准备中。当前显示原文说明。

opsmill/infrahub5382026年10月17日 更新

查看 opsmill 的全部技能

报告此技能的问题