What makes Relay GitCode CLI notable?

974 downloads. Trust evidence available

How should Relay GitCode CLI be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

Relay GitCode CLI

Use gd, the relay-gitcode-cli GitCode command line client, for GitCode API v5 workflows including authentication, repositories, pull requests, issues, search...

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

974

Updated

Oct 11, 2026

Version

0.1.5

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 974 downloads reported by the source. Last updated 10/11/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 11, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 11, 2026
Adoption signal: 974 downloadsadoption · observed Oct 11, 2026
Latest release: 0.1.5release · observed May 20, 2026
Handshake status: UNKNOWNsecurity

What changed

Newest first. Only changes that point at a source are listed.

Release 0.1.5release
gd v0.1.5
Observed May 20, 2026 · source

Install and run

Setup complexity: low.

clawhub skill install s175261s0xvkyprt3f0vdgxm8h84hkx6:relay-gitcode-cli

Install using `clawhub skill install s175261s0xvkyprt3f0vdgxm8h84hkx6:relay-gitcode-cli` in an isolated environment before connecting it to live workloads.
No published capability contract is available yet, so validate auth and request/response behavior manually.
Review the upstream CLAWHUB listing at https://clawhub.ai/stevetdp/relay-gitcode-cli before using production credentials.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-stevetdp-relay-gitcode-cli/snapshot"

Run-check

$0.02 USD

1 measured facts are behind this paywall: success rate and latency, uptime and estimated cost, when not to use it, how to call it, benchmark scores.

Agents pay $0.02 in USDC. A card payment is $0.50, the smallest a card allows.

Documentation

CLAWHUB

140,346 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: relay-gitcode-cli
description: Use gd, the relay-gitcode-cli GitCode command line client, for GitCode API v5 workflows including authentication, repositories, pull requests, issues, search, SSH keys, labels, releases, GitCode Pipeline operations, raw API calls, JSON automation, version checks, and shell completion. Use when an agent should operate GitCode by running local gd commands. Do not use this skill for GitHub-only gh surfaces unless GitCode exposes an equivalent API through gd or gd api.
metadata:
version: 0.1.5
openclaw:
skillKey: relay-gitcode-cli
homepage: https://github.com/coolplayagent/relay-gitcode-cli
---

# Relay GitCode CLI

## Workflow

Use the selected `gd` binary as the GitCode control surface. Prefer `--json`
for automation and inspect command help before exposing unfamiliar operations:

```bash
gd --help
gd pr create --help
gd api --help
```

Keep behavior GitCode-specific. Do not introduce GitHub-only command surfaces
such as gists, codespaces, projects, GitHub Actions, rulesets, extensions, or
Copilot unless GitCode exposes equivalent API behavior and the task can be done
through `gd api`.

When `gd` commands, flags, examples, or user-facing behavior change in this
repository, update this `SKILL.md` in the same change so agent workflows stay
aligned with the compiled CLI.

`gd` reuses reqwest system proxy behavior for `HTTP_PROXY`/`http_proxy`,
`HTTPS_PROXY`/`https_proxy`, `ALL_PROXY`/`all_proxy`, and
`NO_PROXY`/`no_proxy`. TLS certificate verification is disabled by default for
GitCode API calls. Set `GD_SSL_VERIFY`/`gd_ssl_verify`,
`GITCODE_SSL_VERIFY`/`gitcode_ssl_verify`, or `SSL_VERIFY`/`ssl_verify` to
`true` to enable verification; any non-empty
`GIT_SSL_NO_VERIFY`/`git_ssl_no_verify` value keeps it disabled.

## Readiness

Select the newest usable `gd` before running workflows. Resolve bundled assets
relative to this skill directory. On Linux x64, check
`assets/bin/linux-x86_64/gd`; on Windows x64, check
`assets/bin/windows-x86_64/gd.exe`. Also check the `gd` binary found on `PATH`
with `command -v gd` on Unix or `where gd` on Windows.

For every candidate that exists and is executable, run `<candidate> --version`
and parse the semver from output such as `gd 0.1.0`. Use the candidate with the
highest semver. If versions are equal, prefer the bundled binary. Ignore
candidates that cannot run or do not print a parseable `gd` version. If the
selected binary is not on `PATH`, run it by absolute path or set `GD_BIN` and
substitute `"$GD_BIN"` for `gd` in the examples below.

Set `GD_BIN` to the selected path, then inspect version and authentication
state:

```bash
"$GD_BIN" --version
"$GD_BIN" version check --json
"$GD_BIN" auth status --json
```

Only install online when no bundled or `PATH` binary is usable. Prefer the Rust
package first and GitHub Releases second:

```bash
cargo install relay-gitcode-cli --force
gd version check --json
```

When falling back to GitHub Releases downloads, use the

_meta.json

{
  "ownerId": "kn7ftpbqzwq14ga3f5ms64h1yn84hc25",
  "slug": "relay-gitcode-cli",
  "version": "0.1.5",
  "publishedAt": 1779268454911
}

references/cli-workflows.md

# Relay GitCode CLI Workflows

## Contents

- [Installation and Authentication](#installation-and-authentication)
- [Safe Automation Defaults](#safe-automation-defaults)
- [Repository Workflows](#repository-workflows)
- [Issue and Pull Request Workflows](#issue-and-pull-request-workflows)
- [Search, SSH Keys, Labels, and Releases](#search-ssh-keys-labels-and-releases)
- [Raw GitCode API Calls](#raw-gitcode-api-calls)
- [GitCode Pipeline Workflows](#gitcode-pipeline-workflows)
- [Workflow YAML References](#workflow-yaml-references)
- [Out of Scope](#out-of-scope)

## Installation and Authentication

Select the newest usable released `gd` binary before running workflows. Check
the bundled binary for the current platform, if present:
`assets/bin/linux-x86_64/gd` on Linux x64 or
`assets/bin/windows-x86_64/gd.exe` on Windows x64. Also check the `gd` binary
found on `PATH` with `command -v gd` on Unix or `where gd` on Windows.

Run `<candidate> --version` for each candidate and parse the semver from output
such as `gd 0.1.0`. Use the highest semver. If versions are equal, prefer the
bundled binary. Ignore candidates that cannot run or do not print a parseable
`gd` version. If the selected binary is not on `PATH`, run it by absolute path
or set `GD_BIN` and substitute `"$GD_BIN"` for `gd` in examples.

Only install online when no bundled or `PATH` binary is usable. Prefer the Rust
package first and GitHub Releases second:

```bash
cargo install relay-gitcode-cli --force
gd --version
gd version check --json
```

When falling back to GitHub Releases downloads, use the environment proxy
required by the host network. Check or set `HTTPS_PROXY`/`https_proxy`,
`HTTP_PROXY`/`http_proxy`, `ALL_PROXY`/`all_proxy`, and
`NO_PROXY`/`no_proxy` before running `curl`, `wget`, or another downloader.

Do not install from a local repository checkout as part of this skill workflow.
The bundled binaries and online fallbacks should come from released CLI
artifacts.

Use `GD_TOKEN` or `GITCODE_TOKEN` for temporary automation and CI. `GD_TOKEN`
takes precedence when both are present:

```bash
GD_TOKEN="$GD_TOKEN" gd auth status --json
```

Use keyring-backed login for interactive local sessions:

```bash
printf '%s' "$GITCODE_TOKEN" | gd auth login --with-token --json
gd auth status --json
```

Do not write tokens to shell history, repository files, committed fixtures, or
skill outputs. Do not include private API responses in docs or examples.

## Safe Automation Defaults

- Prefer `--json` for any output an agent will parse.
- Prefer explicit `--repo owner/repo` rather than relying on local default
  repository state.
- Use `--hostname` for GitCode host overrides and `--api-base` for API base
  overrides.
- Keep page sizes bounded with `--limit`.
- Read command help before using a subcommand in a new automation path.
- Use `gd api` only for GitCode API v5 endpoints or another user-approved
  GitCode-compatible API base.

## Repository Workflows

Inspect repositories:

```bas

references/gitcode-workflow-yml.md

# GitCode Workflow YAML Examples

Use this reference when creating or updating GitCode Pipeline workflow files
under `.gitcode/workflows`, especially `.gitcode/workflows/ci.yml`.

Official GitCode Pipeline documentation describes workflows as YAML files stored
under `.gitcode/workflows`. A workflow has trigger events, one or more jobs, and
ordered steps. Jobs run on a GitCode runner such as `euleros-2.10.1`, and steps
can either run shell commands or use reusable actions such as
`[email protected]`, `[email protected]`, `[email protected]`,
`[email protected]`, and `[email protected]`.

Sources:

- <https://docs.gitcode.com/en/docs/help/home/org_project/pipeline/pipeline-intro1/>
- <https://docs.gitcode.com/docs/help/home/org_project/pipeline/pipeline-intro1/>

## Style

- Store workflow files in `.gitcode/workflows`.
- Use `ci.yml` for the main continuous-integration workflow unless the project
already has a clearer local naming convention.
- Keep YAML indentation at two spaces.
- Use a clear top-level `name`.
- Prefer explicit branch filters for `push` and `pull_request`.
- GitCode documents manual triggers as a pipeline capability, but the public
intro page does not show a YAML key for that trigger. Do not add
`workflow_dispatch` to reusable examples unless the target GitCode project has
already confirmed that syntax.
- Start each job by checking out the repository with `[email protected]`.
- Run repository commands from `repo_workspace` after checkout.
- Keep secrets in GitCode project secrets or environment configuration, not in
workflow files.
- Keep GitCode workflow examples separate from GitHub Actions examples. Do not
use `actions/checkout`, `ubuntu-latest`, or GitHub-only workflow surfaces.
- GitCode documents `[email protected]`, `[email protected]`, and
`[email protected]` as available built-in actions, but this reference does not
guess their `with` inputs without action-specific docs.

## Minimal CI

```yaml
name: ci

on:
push:
branches: [ "main" ]
pull_request:
branches: [ "main" ]

jobs:
build:
runs-on: euleros-2.10.1
steps:
- uses: [email protected]
- name: Inspect workspace
run: |
cd repo_workspace
pwd
ls
```

## CodeCheck

Use `gd pipeline codecheck` to generate this workflow so the personal access
token is referenced through a project secret instead of committed as a literal
value:

```bash
gd pipeline codecheck --repo owner/repo --language SHELL --access-token-secret CODECHECK_ACCESS_TOKEN --json
```

The generated workflow uses `[email protected]` with `repo_url`,
`branch`, `rule_sets`, and `access_token` inputs as documented by GitCode
CodeCheck. Pull request runs pass the PR source repository and branch to
CodeCheck; push runs pass the configured repository URL and current ref.

## Rust CLI CI

Use this shape for Rust command line projects. It installs stable Rust inside
the clean EulerOS runner, then runs the same local gate u

skill-card.md

## Description:

Relay GitCode CLI guides agents to use the local `gd` command line client for GitCode API v5 workflows, including authentication, repositories, pull requests, issues, search, SSH keys, labels, releases, pipelines, raw API calls, JSON automation, version checks, and shell completion.

This skill is ready for commercial/non-commercial use.

## Publisher:

[stevetdp](https://clawhub.ai/user/stevetdp)

### License/Terms of Use:

MIT-0

## Use Case:

Developers and agent operators use this skill when an agent needs to inspect or change GitCode resources through `gd` commands instead of GitHub-only tooling. It supports repository, pull request, issue, release, label, SSH key, pipeline, workflow YAML, and raw API automation.

### Deployment Geography for Use:

Global

## Known Risks and Mitigations:

Risk: The skill handles GitCode credentials and private API responses.

Mitigation: Use narrow, revocable tokens through environment variables or keyring-backed login, and do not print, commit, or persist tokens or private API responses.

Risk: The documented CLI behavior disables TLS certificate verification by default.

Mitigation: Enable verification with `GD_SSL_VERIFY`, `GITCODE_SSL_VERIFY`, or `SSL_VERIFY` set to `true`, and avoid setting `GIT_SSL_NO_VERIFY`.

Risk: The skill can guide powerful repository and API changes, including moves, delete/recreate syncs, SSH-key deletion, label deletion, pipeline cancellation, and raw API mutations.

Mitigation: Require explicit user confirmation before high-impact operations, prefer disposable repositories for tests, and use dry-run or skip modes where available.

Risk: Online installation fallbacks may fetch unpinned binaries or packages.

Mitigation: Prefer bundled or already installed released `gd` binaries, verify the selected version before use, and avoid online installs unless no usable local binary exists.

## Reference(s):

- [Relay GitCode CLI ClawHub page](https://clawhub.ai/stevetdp/skills/relay-gitcode-cli)
- [Relay GitCode CLI homepage](https://github.com/coolplayagent/relay-gitcode-cli)
- [Relay GitCode CLI Workflows](references/cli-workflows.md)
- [GitCode Workflow YAML Examples](references/gitcode-workflow-yml.md)
- [GitCode Pipeline documentation](https://docs.gitcode.com/en/docs/help/home/org_project/pipeline/pipeline-intro1/)
- [GitCode Pipeline documentation (Chinese)](https://docs.gitcode.com/docs/help/home/org_project/pipeline/pipeline-intro1/)

## Skill Output:

**Output Type(s):** [text, markdown, code, shell commands, configuration, guidance]

**Output Format:** [Markdown guidance with shell command examples, JSON-oriented command patterns, and GitCode workflow YAML snippets]

**Output Parameters:** [1D]

**Other Properties Related to Output:** [Prefers explicit repositories, bounded result sizes, and `--json` output for agent-readable automation.]

## Skill Version(s):

0.1.5 (source: frontmatter and server release metadata)

## Ethical Considerations:

Users should e

Github ReposUpdated 3d agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.

MCPOPENCLAW

Github ReposUpdated 7mo agoRank 70

CopilotKit

The Frontend for Agents & Generative UI. React + Angular