AI Agent Hub
Back to skills
Gitee CLI icon

Gitee CLI

Development Updated 2026.08.29

Paste the following prompt into your AI chat to install this skill:

Follow https://skillhub.cn/install/skillhub.md to install @user_f74b71bc/ge-pro

About this skill

Problem

Everyday Gitee work is often split across web pages, raw API calls, and ad-hoc scripts: checking repositories, opening issues, merging pull requests, inspecting diffs, and fetching paginated lists all require context switching. Engineers who want a local, command-line entry point similar to gh lack a consistent tool for these actions.

How It Works

The skill wraps common Gitee operations into gitee commands:
- Auth: gitee auth manages login, logout, status, and tokens; credentials can come from --token, GITEE_TOKEN, or the local config file.
- Repositories and collaboration: gitee repo, gitee issue, and gitee pr cover listing, creating, viewing, merging, commenting, and diff inspection.
- Organizations and search: gitee org and gitee search support viewing organizations, members, repositories, and searching related resources.
- API and output: gitee api calls Gitee API v5 directly; output can be table, json, or csv, and --paginate can retrieve full paginated results.

Boundaries

It fits local development, CI scripts, and private Gitee instances, especially when stable JSON output or HTTP debugging is needed. Keep token scope, --hostname, and --api-url aligned, and avoid embedding high-privilege tokens in production scripts.

Use Cases

  • Inspect Gitee repository branches, lists, and details in a terminal instead of repeatedly opening the web UI.
  • Create, comment on, merge, and diff issues and pull requests with fewer context switches.
  • Convert Gitee API v5 responses into JSON or CSV for scripts that paginate and analyze data locally.
  • Debug authentication and requests on private Gitee instances by inspecting HTTP requests and responses.

Best For

  • Backend engineers maintaining Gitee repositories who want command-line branch, issue, and PR workflows.
  • DevOps engineers writing CI/CD scripts that need stable JSON output from the CLI or API.
  • Team leads on private Gitee deployments who need to configure hostname, API URL, and tokens.
  • QA engineers debugging API errors by inspecting requests, responses, and error codes.