pr
Skill4 starsChanged 30 days agoMITView on GitHub
Guide pull request creation, review automation, and merge strategies. Use when: creating PRs, automating reviews, configuring merge policies. Not for: the substance of the review itself — use /code-review; branch naming and merge strategy — use /git-workflow-guide. Keywords: pull request, PR, merge, review, GitHub, GitLab.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- AsiaOstrich/universal-dev-standardsword for word, first seen Nov 4, 2026
Other versions1 project uses a version of this.
Word for word · 1
- AsiaOstrich/universal-dev-standards★ 84100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository55 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ac-coverageSkill
- adrSkill
- ai-collaboration-standardsSkill
- ai-friendly-architectureSkill
- ai-instruction-standardsSkill
- api-designSkill
- atddSkill
- auditSkill
- bddSkill
- brainstormSkill
- changelogSkill
- checkinSkill
- ci-cdSkill
- code-reviewSkill
- commitSkill
- contract-testSkill
- databaseSkill
- deploySkill
- methodologySkill
- dev-workflowSkill
- docgenSkill
- documentation-guideSkill
- durableSkill
- e2eSkill
- error-code-guideSkill
- git-workflow-guideSkill
- incidentSkill
- journey-test-assistantSkill
- knowledge-graphSkill
- logging-guideSkill
- metricsSkill
- migrateSkill
- observabilitySkill
- orchestrateSkill
- planSkill
- discoverSkill
- project-structure-guideSkill
- pushSkill
- refactorSkill
- releaseSkill
- requirementSkill
- retrospectiveSkill
- reverseSkill
- runbookSkill
- securitySkill
- scanSkill
- skill-builderSkill
- sloSkill
- spec-deriveSkill
- sddSkill
- sweepSkill
- tddSkill
- coverageSkill
- testing-guideSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 98
After /pr completes, the AI assistant should suggest:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- DEPRECATION NOTICE (XSPEC-086 Phase 4, 2026-04-28):
PR lifecycle orchestration (5-step: CREATE→REVIEW→APPROVE→MERGE→CLEANUP,
size gate >400 lines block, CI gate, squash/merge strategy, gh CLI integration) relocated to
adoption layer (XSPEC-095, 2026-04-28). This Skill retains: PR description template,
merge strategy decision matrix, auto-review trigger rules.
For enforced lifecycle execution, use your adoption layer's toolchain.
-->PR Automation Assistant | PR 自動化助手
⚠️ Status: Reference（參考用，非可執行流程） — PR 生命週期協調（5 步驟 CREATE→REVIEW→APPROVE→MERGE→CLEANUP、>400 行 size gate、CI gate、squash/merge 策略、gh CLI 整合）已於 2026-04-28 移至 adoption layer（XSPEC-095）。此處保留 PR 描述模板、合併策略決策矩陣、auto-review 觸發規則供參考。 Lifecycle orchestration has moved to the adoption layer (XSPEC-095); this document is reference-only. For enforced execution, use your adoption layer's toolchain.
Streamline the pull request lifecycle from creation to merge.
簡化從建立到合併的 Pull Request 生命週期。
PR Creation Checklist | PR 建立檢查清單
| Item | Rule | 規則 |
| Title | <type>(<scope>): <summary> under 70 chars | 70 字元內，遵循 conventional commits |
| Description | Use structured template below | 使用下方結構化模板 |
| Labels | At least one category label | 至少一個分類標籤 |
| Reviewers | Assign based on CODEOWNERS or domain | 依 CODEOWNERS 或領域指派 |
| Branch | Up to date with base branch | 與基礎分支同步 |
PR Description Template | PR 描述模板
## Summary | 摘要
<1-3 bullet points describing the change>
## Changes | 變更內容
- Added / Modified / Removed ...
## Test Plan | 測試計畫
- [ ] Unit tests pass
- [ ] Manual verification steps
## Screenshots | 截圖
(if UI changes)Merge Strategy Decision | 合併策略決策
| Strategy | When to Use | 使用時機 |
| Squash merge | Feature branches with messy commits | 功能分支，提交記錄零散 |
| Merge commit | Release branches, preserve history | 發布分支，保留完整歷史 |
| Rebase | Linear history, small changes | 線性歷史，小幅變更 |
Auto-Review Triggers | 自動審查觸發條件
| Trigger | Threshold | Action | 動作 |
| PR size | > 400 lines changed | Request split | 要求拆分 |
| No tests | 0 test files changed | Block merge | 阻止合併 |
| CI failure | Any check fails | Block merge | 阻止合併 |
| Stale PR | > 7 days no activity | Notify author | 通知作者 |
| Draft PR | Marked as draft | Skip reviewers | 跳過審查者指派 |
Workflow | 工作流程
CREATE ──► REVIEW ──► APPROVE ──► MERGE ──► CLEANUP- Create — Branch, commit, push, open PR with template
- Review — Automated checks + human review
- Approve — All checks green, required approvals met
- Merge — Apply chosen merge strategy
- Cleanup — Delete source branch, update linked issues
Usage | 使用方式
/pr - Guide PR creation for current branch | 引導建立當前分支的 PR
/pr create - Create PR with template | 使用模板建立 PR
/pr --template - Show PR description template | 顯示 PR 描述模板
/pr review 123 - Review specific PR | 審查特定 PRNext Steps Guidance | 下一步引導
After /pr completes, the AI assistant should suggest:
PR 操作完成。建議下一步 / PR operation complete. Suggested next steps:
- 執行
/code-review進行詳細程式碼審查 ⭐ Recommended / 推薦 — Run detailed code review- 執行
/commit修正審查發現的問題 — Fix issues found in review- 執行
/changelog更新變更日誌 — Update changelog- 檢查 CI 狀態 →
gh pr checks— Check CI status
Reference | 參考
- Core standard: code-review-checklist.md
- Core standard: git-workflow.md
Version History | 版本歷史
| Version | Date | Changes | 變更說明 |
| 1.0.0 | 2026-03-23 | Initial release | 初始版本 |
AI Agent Behavior | AI 代理行為
完整的 AI 行為定義請參閱對應的命令文件：
/prFor complete AI agent behavior definition, see the corresponding command file:
/pr
License | 授權
CC BY 4.0 — Documentation content
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.