菜单
Use when creating a pull request, preparing changes for review, or pushing work to GitHub. Handles quality checks, branch management, conventional commits, openspec archival, and PR creation end-to-end.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/tedivm/opencode-config --skill making-prs命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | making-prs |
| description | Use when creating a pull request, preparing changes for review, or pushing work to GitHub. Handles quality checks, branch management, conventional commits, openspec archival, and PR creation end-to-end. |
| license | MIT |
| metadata | {"author":"Robert Hafner","source":"https://github.com/tedivm/opencode-config"} |
Run quality checks, verify openspec status, create a feature branch, commit with conventional format, and open a PR.
Load and execute the quality-checks skill to ensure all tests, lints, and formatting pass before proceeding. Do not skip this step.
If quality checks fail, fix everything until the full suite passes green. Only continue to step 2 once all checks pass.
If the project uses OpenSpec (check for .openspec/ directory or openspec.json):
openspec list --json to find active changes.openspec list shows the change as active (not archived), ask the user: "The OpenSpec proposal [name] is still active. Should I archive it before creating the PR?"openspec-archive) and load it to handle the archival. If no archive skill exists, fall back to running openspec archive <change-name> --yes.git symbolic-ref refs/remotes/origin/HEAD or check git remote show origin for the HEAD branch.git branch --show-current.git diff --stat --cached or git status --short.feat/..., fix/..., chore/..., refactor/..., docs/....git checkout -b <branch-name>.Stage all changes: git add -A.
Determine the conventional commit type by analyzing the changes:
feat — new functionalityfix — bug fixesrefactor — code restructuring without behavior changeschore — maintenance, deps, configdocs — documentation onlytest — adding or modifying testsstyle — formatting, missing semicolons, etcperf — performance improvementsFunctional markdown: AGENTS.md files and skills (.opencode/skills/ or skills/) are markdown but function as agent instructions. Changes to them alter agent behavior — classify them as feat (new behavior), fix (corrected behavior), or refactor (restructured guidance), never chore or docs.
Write a conventional commit message:
<type>(<scope>): <description>Examples:
feat(auth): add JWT-based session management
fix(payments): retry failed transactions with exponential backoff
chore(deps): bump redis client to v4.2
refactor(parser): extract tokenization into standalone module
git commit -m "<title>" [-m "<body>"].git push -u origin <branch-name>.Implements [change-name] or link to the spec.gh-cli skill:
gh pr create --title "TITLE" --body "BODY"
When the user confirms the PR has been merged:
git checkout <default-branch>.git pull origin <default-branch>.基于 SOC 职业分类
