Skills Plugins MCP Prompt Model 博客 我的中心

create-pr

Create Git branches, commits, pushes, and GitHub pull requests for Next.js. Use when the user asks to create a branch, commit current changes, open a PR or draft PR, publish a pull request, or recover from gh pr create / PR template issues. Covers .github/pull_request_template.md, --body formatting, codex/ branch names, and Codex app git directives.

DeepseekModel 官方收录技能 质量 优秀 · 90 v1.0.0

获取

https://deepseekmodel.com/api/download.php?id=vercel-next-js-agents-skills-create-pr-skill-md&format=skill
下载 .skill 标准格式,含 system_prompt 与 model_config,导入任意 Agent 框架即可使用
.skill 文件中 system_prompt 字段的实际内容。
name create-pr description Create Git branches, commits, pushes, and GitHub pull requests for Next.js. Use when the user asks to create a branch, commit current changes, open a PR or draft PR, publish a pull request, or recover from gh pr create / PR template issues. Covers .github/pull_request_template.md, --body formatting, codex/ branch names, and Codex app git directives. metadata {"internal":true} Create PR Use this skill when turning local work into a GitHub pull request. Fork PRs vs Branch PRs Before writing a PR description, check whether this is a branch PR (the branch lives in vercel/next.js ) or a fork PR (an external contribution from a fork). You may write full descriptions for branch PRs, but not for fork PRs — inform the user, offer to review their description or provide technical details, and give them the GitHub URL to create the PR themselves. See "GitHub Pull Requests and Issues" in AGENTS.md for the full policy. Workflow Inspect the current state before mutating Git: git status --short git branch --show-current git diff -- <paths> Stage only files that belong to the requested change. Preserve unrelated user changes. Create or confirm the branch: git switch -c codex/<short-topic> Use the codex/ prefix unless the user asks for a different name. If a .git/*lock or Operation not permitted error appears, rerun the same Git command with sandbox escalation. Do not assume a branch namespace conflict until checking refs with git branch --list , git show-ref , or git for-each-ref . Validate and commit: git add <paths> git diff --cached --check git commit -m "<concise message>" Keep commit messages concise and do not add generated-tool or co-author footers. Push the branch: git push -u origin <branch> Create the PR as a draft unless the user explicitly asks otherwise: gh pr create --draft --base canary -- head <branch> --title "<title>" --body '<body>' For this repo, prefer canary as the base branch. If GitHub network access fails in the sandbox, rerun with escalation. PR Body Use this PR body format: ## Summary < what changed and why > ## Verification - `<command that passed>` - Not run: `<command>` ( `<reason>` ) <!-- NEXT _JS_ LLM --> The "what" should be explained from the end-user perspective or developer perspective. Only include implementation changes if they're not obvious from the diff. A "why" should be included if the change isn't self-explanatory, or if the motivation is not clear from the diff. Omitting the "why" should be used sparingly and only for small changes. Do not include trivial verification commands that CI already covers (e.g. pnpm run build ), but do include any manual verification steps. If the PR changes a test, you don't need to repeat the command to run that test. But if you used an existing test to validate some behavior didn't change, include that test. Use --body with this filled content. Recovery If a PR may already exist, check before creating a duplicate: gh pr view -- head <branch> --json url,isDraft,title If approval is denied for gh pr create , report that the branch is pushed but the PR was not created, and provide the exact corrected command. After successful Codex app Git actions, include the appropriate final-response directives for branch creation, staging, committing, pushing, and PR creation. Related Skills $pr-status-triage - Analyze CI failures and PR review feedback after the PR exists. $gh-stack - Manage stacked branches and dependent pull requests.
Agent 识别该技能的关键词,点击任意一个即可复制。

该技能未提供触发词。

下载的 .skill 包内含以下字段。
字段 说明
format格式标识(skill/v1)
skill_id技能唯一 ID
name技能名称
version版本号
description技能描述
category所属分类(数组)
trigger_words触发词列表
tags标签列表
source来源标识
source_url来源链接(本页地址)
exported_at导出时间(每次下载生成)
system_prompt系统提示词正文
model_config模型参数:provider / model / temperature / max_tokens / top_p
examples示例
install_guide各平台导入说明(Coze / Dify / Claude / 自定义框架)
同一份技能可按不同平台格式导出。
.skill 标准格式,含 system_prompt 与 model_config,导入任意 Agent 框架即可使用 下载
.skillpro 增强格式,额外含脚本 / 工具 / 依赖 / 钩子占位 下载
.json 纯 JSON 导出,只含 system_prompt 与模型参数 下载
Coze 带 frontmatter 的 Markdown,Coze 平台导入用 下载
Dify Dify DSL,创建应用后直接导入 下载

每日精选 Skill 推荐,免费送到你邮箱

输入邮箱,每天接收一个精选 AI Agent 技能推荐。完全免费,持续更新。

提交后我们会发送一封确认邮件,点击邮件里的链接才会开始收信。

完全免费,取消任意时间。我们不会发送垃圾邮件。