gitcode-create-pr

Creates and updates GitCode pull requests from specified source and target branches.

104|9|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/openyuanrong-project/yuanrong --skill gitcode-create-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitcode-create-pr
Source: https://github.com/openyuanrong-project/yuanrong/tree/main/.skills/gitcode-create-pr
Command: npx skills add https://github.com/openyuanrong-project/yuanrong --skill gitcode-create-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically create and update GitCode pull requests from user prompts, reducing manual PR drafting and submission overhead.

Core Features & Use Cases

  • Create PRs on GitCode from a local branch or fork, including title and body formatting for the API.
  • Update existing PR title or description, or adjust PR metadata using the GitCode API.
  • Infer owner/repo from a remote URL and support cross-repository PRs when needed.

Quick Start

Create a PR for owner/repo with source_branch and target_branch, set the title and body, and submit it to GitCode.

Frequently Asked Questions about gitcode-create-pr

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

FAQPage Schema
How do I automate GitCode pull request creation from a prompt?

You can automate GitCode pull request creation by providing the owner, repo, source branch, target branch, title, and body. The skill formats these inputs into an API payload to submit the PR directly from your prompt.

Can I update an existing PR title and description using the GitCode API?

Yes, you can update an existing GitCode PR title and description. The skill formats your prompt inputs into the required API payload to adjust PR metadata and descriptions programmatically.

Does creating a cross-repository PR from a fork require manual owner and repo inputs?

No, creating a cross-repository PR from a fork does not require manual owner and repo inputs. The skill can automatically derive the owner and repo from a provided remote URL, while supporting optional fork info.

What is the best way to format API payloads for GitCode PR management?

The best way to format API payloads for GitCode PR management is through this automation skill. It structures your provided source branch, target branch, and metadata into the correct GitCode API format for submission.

Why does my GitCode PR creation fail when submitting cross-repo changes?

GitCode PR creation for cross-repo changes may fail if fork information is omitted or the remote URL is incorrect. Ensure you provide valid source and target branches, and let the skill derive the owner and repo from the remote.