Gitcode

GitCode (Issue / PR)

Project-local skill for sciencediscovery on gitcode.com (not under skills/).

New issues and pull requests for this repository are not filed here. Use gh against openJiuwen-ai/sciencediscovery, and write the title and body in English. This skill is for an existing GitCode mirror item that still has to be read or commented on.

Use the command table below, gitcode schema, or gitcode <cmd> --help to resolve flags. Only if a flag is still unclear, run gitcode api repos/gitcode-cli/cli/contents/docs, select the download_url for COMMANDS.md, AUTH.md, or AI-GUIDE.md, and read that raw.gitcode.com content. Do not scrape GitCode blob-page HTML.

Rules

1. Run gitcode, never bare gc (often a git commit alias).
2. Install/helpers via uv; never commit CLI binaries or tokens.
3. Never print tokens (auth token / auth status --show-token).
4. Prefer --json; if create/edit JSON is thin (missing html_url or with the wrong number), confirm with view/list.
5. For a complete Issue inventory or count, never rely on issue list's default --limit 30. Pass an explicit limit larger than the expected result set, check the returned JSON array length, and continue with --page 2, --page 3, … whenever a page length equals the requested limit. Stop only after a shorter page, then deduplicate by Issue number before counting.
6. Destructive ops (close/reopen/merge/delete…) need user intent + --yes.
7. Scope: only repos the user named (or cwd remote when clearly that clone).
8. Transports: metadata/API → gitcode CLI; code/MR head → SSH git. HTTPS git easily fails (hangs without a credential helper; web/HTTPS fetches commonly return 403), so always use SSH and do not scrape gitcode.com HTML.
9. Follow Cross-references and issue association for visible links and unverified auto-close behavior.
10. sciencediscovery merge requests: each operator uses their own GitCode fork of openJiuwen/sciencediscovery (do not hard-code a login). Resolve <gitcode-login> from gitcode auth status --json. Push the source branch to that fork (common remote name gitcode-fork) and create with --head <gitcode-login>:<branch>. Do not git push origin <task-branch> onto openJiuwen/sciencediscovery. If the fork is missing: gitcode repo fork openJiuwen/sciencediscovery --json.

Hosts

gitcode.com and atomgit.com are hostnames for the same website/platform: repositories and their issue/PR numbers are identical. Do not treat AtomGit as a separate product. For authored or reported repo, issue, and PR URLs, prefer https://gitcode.com/...; rewrite AtomGit hosts and CLI html_url paths such as /merge_requests/N to these canonical forms:

• Issue: https://gitcode.com/openJiuwen/sciencediscovery/issues/9
• PR list: https://gitcode.com/openJiuwen/sciencediscovery/pulls
• PR detail: https://gitcode.com/owner/repo/pull/N
• SSH: git@gitcode.com:owner/repo.git and git@atomgit.com:owner/repo.git are equivalent; prefer writing/configuring the gitcode.com form, even when an existing remote uses AtomGit.

Install / auth (once)

uv tool install gitcode-cli
export PATH="$HOME/.local/bin:$PATH"
gitcode version
gitcode auth status --json   # need logged_in + token_valid

Token priority: GC_TOKEN > GITCODE_TOKEN > ~/.config/gc/auth.json. No browser on box → user creates classic token at https://gitcode.com/setting/token-classic and runs gitcode auth login on a private TTY (do not ask them to paste token into chat). Fallback install: uv venv .local/gitcode-venv && uv pip install --python .local/gitcode-venv gitcode-cli. Binary resolve: command -v gitcode → $HOME/.local/bin/gitcode → .local/gitcode-venv/bin/gitcode. PyPI stale: uv tool install --from 'https://gitcode.com/gitcode-cli/cli/releases/download/<ver>/gitcode_cli-<ver>-py3-none-any.whl' gitcode-cli.

Targeting

Always pass -R owner/repo when not on cwd origin. Forms: owner/repo, HTTPS URL, SSH URL (CLI API only — not git transport).

Issue / PR commands

# issues
gitcode issue create -R owner/repo --title "…" --body-file body.md --json
# Complete inventory: 30 is the CLI default and is commonly truncated.
gitcode issue list -R owner/repo --state open --limit 100 --page 1 --json
gitcode issue view N -R owner/repo --json
gitcode issue view N -R owner/repo --comments --json
gitcode issue edit N -R owner/repo --body-file body.md --json
gitcode issue comment N -R owner/repo --body "…" --json
gitcode issue comments N -R owner/repo --json
gitcode issue comment edit <comment_id> -R owner/repo --body "…"   # may not support --json
gitcode issue close N -R owner/repo --yes --json
gitcode issue reopen N -R owner/repo --yes --json

# PRs — sciencediscovery: source branch on the operator's own fork, never on origin
gitcode pr create -R openJiuwen/sciencediscovery --head <gitcode-login>:branch --base main --title "…" --body-file pr.md --json
gitcode pr create -R upstream/repo --head myfork:branch --title "…" --body-file pr.md --json
gitcode pr create -R owner/repo --head branch --fill --json
gitcode pr create -R owner/repo --head branch --title "WIP" --draft --json
gitcode pr list -R owner/repo --state open --json
gitcode pr view N -R owner/repo --json
gitcode pr view N -R owner/repo --comments --json
gitcode pr diff N -R owner/repo
gitcode pr edit N -R owner/repo --body-file pr.md --json
gitcode pr comment N -R owner/repo --body "…" --json
gitcode pr comment N -R owner/repo --body "…" --path path/to/file.py --position 12 --json
gitcode pr comments N -R owner/repo --json
gitcode pr reply N -R owner/repo --discussion <id> --body "…"
gitcode pr review N -R owner/repo --comment "…" --json   # or --comment-file
gitcode pr merge N -R owner/repo --yes --json            # optional --method squash|rebase
gitcode pr close|reopen|ready N -R owner/repo --yes --json
gitcode pr checkout N -R owner/repo
gitcode repo fork owner/repo --json
gitcode repo view owner/repo --json
gitcode schema
gitcode schema "issue create"

PR view JSON shapes

gitcode pr view changes its top-level JSON shape when comments are requested:

• gitcode pr view N -R owner/repo --json returns the PR object directly.
• gitcode pr view N -R owner/repo --comments --json returns { "pull_request": <PR object>, "comments": [...] }.

Do not read .number, .head, or .labels at the top level of the comments form; those fields are below .pull_request. Optional arrays such as labels may be null, so normalize them with // [] before iterating.

# PR metadata only
gitcode pr view N -R owner/repo --json |
  jq '{number, title, state, head_sha: .head.sha,
       labels: [((.labels // [])[]) | .name]}'

# PR metadata and comments
gitcode pr view N -R owner/repo --comments --json |
  jq '{pr: (.pull_request | {number, title, state, head_sha: .head.sha}),
       comments: [(.comments // [])[] |
         {author: (.user.login // .author.login // .author_name),
          body: (.body // .note // ""), created_at}]}'

Use gitcode pr comments N -R owner/repo --json when only the comment list is needed.

For complete Issue inventories, treat length == --limit as “possibly truncated,” not as a final count. Fetch subsequent pages with the same filters until one returns fewer rows than the limit; combine the pages and deduplicate by .number. If the first page returns fewer than the explicit limit, it is complete for those filters at that retrieval time.

• Line comments: --position = line on the new file (right side of diff). Inline comments appear as comment_type: diff_comment.
• --approve: only with explicit user intent + approval permission; own-PR / missing role → 403 — leave a comment review instead.
• --request (request changes) unsupported; put change requests in --comment.
• Merge only with explicit user OK for that PR.
• pr create 409 / "same source branch already has an open MR !N": !N may be the PR this very call just created (observed on this repo), an earlier PR opened from the same branch, or one you should not touch. Never retry blindly and never rename the branch to dodge it. Read it back — gitcode pr view N -R owner/repo --json — compare base, head branch, head SHA, title, body, author, created time, and existing review activity against this attempt, then act on what !N actually is. Typical outcomes: this attempt landed ⇒ report !N; your own re-delivery on the same branch, where the MR already tracks the pushed head but title/body are stale ⇒ bring it up to date with gitcode pr edit N --body-file … instead of creating a second PR; head SHA still behind your push ⇒ confirm the push reached the fork before touching the PR; wrong base, another author, or review already under way ⇒ stop and report so the user can choose (edit, close, or a fresh branch). Judge from the read-back, not from the error text.

Read a PR (review prep)

1. gitcode pr view N -R owner/repo --json — title, body, SHAs, state
2. gitcode pr diff N -R owner/repo — patch overview; prefer text output, and expect no binary preview
3. gitcode api repos/owner/repo/pulls/N/files — structured file list / raw URLs
4. Full tree: SSH git fetch git@gitcode.com:owner/repo.git refs/merge-requests/N/head (GitCode MR ref; not HTTPS). Prefer this over scraping the web UI.

Cross-references and issue association

• Ordinary issue/comment reference: [#32](https://gitcode.com/openJiuwen/sciencediscovery/issues/32).
• Ordinary PR reference: [#10](https://gitcode.com/openJiuwen/sciencediscovery/pull/10). Write /pull/N in authored links even if CLI html_url says /merge_requests/N.
• To associate an issue in a PR body, retain the trigger candidate and add a readable link: Fixes #32 ([#32](https://gitcode.com/openJiuwen/sciencediscovery/issues/32)).
• Automatic closing after merge is not verified. Never promise that Fixes #N or its Markdown link will close the issue; commit messages alone do not auto-close.