菜单
Generate a PR title and description following the WCC repo template, infer change types from the diff, and print the GitHub URL to open the PR in the browser. Use when asked to open a PR or create a pull request.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Interactively create a well-structured GitHub issue (bug or feature) for Women-Coding-Community/wcc-backend with Scrum user story, acceptance criteria, test scenarios, and code examples derived from the codebase. Adds the issue to the Backend Platform project board.
Review local staged and unstaged changes before committing. Auto-fixes style violations (line length, @DisplayName casing, var, eq() wrappers, .get(0)), then outputs a summary of findings requiring human judgement.
Read a GitHub issue from Women-Coding-Community/wcc-backend, produce an implementation plan, and — on user confirmation — implement it following WCC project standards (unit tests, integration tests, PMD-clean, Javadoc on public methods, no inline comments, language-specific best practices).
| name | open-pr |
| description | Generate a PR title and description following the WCC repo template, infer change types from the diff, and print the GitHub URL to open the PR in the browser. Use when asked to open a PR or create a pull request. |
| disable-model-invocation | true |
| allowed-tools | Bash, Read, Glob |
Scope: Local — wcc-backend only
Canonical runbook:
.ai/skills/open-pr.mdThis file is the Claude Code adapter. The workflow logic is defined in the canonical skill so it can be shared with other agents (Codex, Copilot, Cursor). Any changes to the workflow should be made in.ai/skills/open-pr.mdfirst.
Gather context in parallel:
git log main..HEAD --oneline — commits in this PRgit diff main...HEAD --stat — files changedgit branch --show-current — current branch name.github/PULL_REQUEST_TEMPLATE.mdDetermine change types by mapping conventional-commit prefixes and the nature of the diff:
| Conventional prefix | PR Change Type |
|---|---|
feat | New Feature |
fix | Bug Fix |
refactor | Code Refactor |
docs / doc | Documentation |
test | Test |
chore / ci / build | Other |
Only keep the change types present in this PR — remove the rest from the template.
Suggest a PR title using Conventional Commits format: <type>: <short imperative description> (50–72 chars). When multiple types apply, use the most significant: feat > fix > refactor > test > docs > chore.
Generate the filled-in PR description. Pre-check only the applicable change type boxes; remove the inapplicable ones entirely. Write all prose sections (Description, Related Issue) as flowing paragraphs where each paragraph is a single unbroken line — do NOT insert newlines within a paragraph for any reason. Blank lines between paragraphs are fine; newlines inside a paragraph are not. When the user pastes the description into GitHub, mid-sentence newlines are preserved literally in the text area and break the visual layout.
Screenshots section — decide based on changed files:
admin-wcc-app/**, *.tsx, *.css, components, pages): include the section and list the specific screenshots needed (before/after UI, error states, label/title changes, GIF for interactions). Emphasise that screenshots are required for the reviewer to assess visual changes./swagger-ui/index.html).test, docs, chore, ci, or refactor with no endpoint changes: omit the Screenshots section entirely.Pull request checklist — always include the contributor guide checkbox. Include "I have tested my changes locally" only for feat, fix, refactor, or frontend changes — omit it for pure docs, chore, or ci changes.
Derive the contributor's GitHub username from the origin remote:
git remote get-url origin
# https://github.com/<username>/wcc-backend.git or git@github.com:<username>/wcc-backend.git
Extract <username> from the URL (path segment before /wcc-backend).
Print:
https://github.com/Women-Coding-Community/wcc-backend/compare/main...<username>:<branch-name>Each prose paragraph must be a single unbroken line — never wrap text at 72, 80, or any column width. The only newlines inside prose sections must be blank lines separating paragraphs. Mid-sentence newlines paste literally into the GitHub text area and break the rendered layout.
✅ Correct: This PR adds email notifications. Notifications are sent to both mentor and mentee when an application changes.
❌ Wrong: This PR adds email notifications.\nNotifications are sent to both mentor\nand mentee when an application changes.
Always target main on Women-Coding-Community/wcc-backend (upstream)
Never use gh pr create — fork permissions require the user to open the PR through the browser
If the issue number cannot be found in branch name or commits, use #? and ask the user
Never include change type checkboxes for types not present in the diff
Never include the Screenshots section for pure test/docs/chore/ci changes
Never include "I have tested my changes locally" for pure docs/chore/ci changes