gitcode

Operate GitCode issues, pull requests, wikis, and org templates via the gitcode CLI.

64|15|Updated Aug 14, 2026
One-click install
npx skills add https://github.com/openJiuwen-ai/sciencediscovery --skill gitcode-openjiuwen-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gitcode
Source: https://github.com/openJiuwen-ai/sciencediscovery/tree/main/.agents/skills/gitcode
Command: npx skills add https://github.com/openJiuwen-ai/sciencediscovery --skill gitcode-openjiuwen-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gitcode-cli, uv, and includes scripts (resource) components.

What problem does it solve? Managing issues, pull requests, wikis, and images on GitCode (gitcode.com / atomgit.com) requires many manual web UI steps and error-prone CLI invocations; this Skill standardizes authenticated, scriptable GitCode operations with correct flags, pagination, and fork-based MR workflows. ## Core Features & Use Cases - Issue and PR lifecycle management: Create, list, view, edit, comment, review, merge, and close issues and PRs with --json output, complete paginated inventories, and fork-based --head owner:branch merge requests. - Image upload and download: Upload local images to a repo and download authenticated raw.gitcode.com user-images via helper scripts that resolve tokens like the gitcode CLI. - Org template caching: Fetch openJiuwen .gitcode issue/PR templates (Chinese and English) into a local cache and convert issue forms into Markdown bodies. - Use Case: A maintainer needs to file a bug report from the openJiuwen Chinese issue form, attach a screenshot, and open a PR from their own fork referencing Fixes #32 — all without touching the web UI. ## Quick Start Ask the agent to use the gitcode skill to list all open issues in openJiuwen/sciencediscovery with full pagination and JSON output.

Frequently Asked Questions about gitcode

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

FAQPage Schema
How do I create a pull request on GitCode from the command line?▼

Use `gitcode pr create -R owner/repo --head <login>:<branch> --base main --title "..." --body-file pr.md --json`. Push the source branch to your own fork first, never to the upstream origin, and confirm the result with `gitcode pr view`.

How do I list all issues on GitCode without truncation?▼

The default `gitcode issue list` limit is 30 and commonly truncates results. Pass an explicit `--limit` larger than the expected set, check the returned array length, and keep fetching `--page 2`, `--page 3`, and so on until a page returns fewer rows than the limit, then deduplicate by issue number.

Does GitCode support uploading images into issue or PR comments?▼

Yes. The upload_image.py script posts a base64-encoded image to the repo's uploads endpoint and returns a Markdown embed pointing to raw.gitcode.com. Downloading those images later requires Bearer token auth, since anonymous requests return 403.

Why does git fetch over HTTPS fail for GitCode merge request refs?▼

HTTPS git transport on GitCode commonly hangs without a credential helper or returns 403 on web fetches. Use SSH instead: `git fetch git@gitcode.com:owner/repo.git refs/merge-requests/N/head` to inspect an MR head.

What should I do when gitcode pr create returns a 409 conflict?▼

A 409 citing an existing MR `!N` may refer to the PR this call just created or an earlier one from the same branch. Read it back with `gitcode pr view N --json`, compare base, head SHA, title, and author, then edit the existing PR rather than retrying or renaming the branch.