gitcode-cli

Manage GitCode repositories via oh-gc CLI for authentication, issues, PRs, releases, and configuration.

31|6|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/openharmonyinsight/openharmony-skills --skill gitcode-cli
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gitcode-cli
Source: https://github.com/openharmonyinsight/openharmony-skills/tree/main/skills/gitcode-cli
Command: npx skills add https://github.com/openharmonyinsight/openharmony-skills --skill gitcode-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of managing GitCode repositories through a browser by providing an efficient terminal workflow for authentication, issues, pull requests, releases, and repository configuration.

Core Features & Use Cases

  • GitCode CLI operations (oh-gc): Authenticate, list/view/create/edit issues and PRs, add comments, assign reviewers/testers, and manage labels/milestones.
  • Cross-repo pull request support: Create PRs using fork-to-upstream flow with the required head format and repository targeting via --repo.
  • Automation-friendly outputs: Use global flags like --json for scripting and CI pipelines.

Quick Start

Run oh-gc --version first to verify you have the required CLI version, then log in with oh-gc auth login and use oh-gc pr list --repo openharmony/arkui_ace_engine to see pull requests.

Frequently Asked Questions about gitcode-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage GitCode issues and pull requests from the terminal?▼

You can manage GitCode issues and pull requests from the terminal by using the oh-gc CLI to authenticate, triage issues, handle PR lifecycles, and configure repositories directly via command-line operations.

What is the best way to automate GitCode repository management in CI pipelines?▼

Automating GitCode repository management in CI pipelines is best achieved by using CLI commands with global flags like --json, which outputs automation-friendly data for scripting cross-repo PR creation and issue tracking.

How do I create a cross-repo pull request on GitCode using the command line?▼

To create a cross-repo pull request on GitCode via the command line, use the fork-to-upstream flow with the required head syntax and target the specific repository using the --repo flag.

Do I need to verify my CLI version before managing GitCode repositories?▼

Yes, you need to verify your CLI version before managing GitCode repositories. Running oh-gc --version ensures you have the required CLI version to perform authenticated API access and repository configuration.

Can I assign reviewers and manage labels for GitCode PRs without a browser?▼

Yes, you can assign reviewers, add comments, and manage labels or milestones for GitCode PRs without a browser by executing the appropriate CLI commands within your terminal-based workflow.

What are the limitations of using terminal commands for GitCode issue triage?▼

A limitation of using terminal commands for GitCode issue triage is the strict requirement for correct repository scoping via --repo and authenticated API access, which must be precisely configured to avoid execution errors.