pull-request-delivery
Prepares and optionally creates a traceable draft pull request from closed-run evidence. Use after engineering closure and final report generation.
- License 许可
- Apache-2.0
- 最近更新
- 2026-07-13
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- pull-request-delivery
- description
- Prepares and optionally creates a traceable draft pull request from closed-run evidence. Use after engineering closure and final report generation.
03 SKILL.md 正文
Pull Request Delivery
Purpose
Create a reviewable PR package that explains what changed, why, what was validated, what risks remain, and how to roll back.
Required PR body sections
- Summary
- Why
- Scope
- Task and commit traceability
- Validation
- Review outcomes
- Residual risks and deferred work
- Rollback
- Operational notes
- Learning and audit evidence
- Explicit non-goals
Rules
- Prepare PR evidence offline before remote mutation.
- Draft by default.
- No merge, auto-merge, deployment, or CI-success claim.
- Push and PR creation require explicit delivery authority.
- Update an existing PR for the same head branch instead of creating duplicates.
Verification
- [ ] PR metadata matches current branch and run.
- [ ] Task-to-commit traceability is complete.
- [ ] Reports are linked.
- [ ] Risks and rollback are explicit.
- [ ] Remote action is authorized.
04 同仓库更多 Skills
invoice-domain-review
Domain review for contractor invoice governance, ingestion, reconciliation, attendance attribution and billing evidence.
python-domain-review
Reviews generic Python implementation against task intent, API expectations, simplicity and maintainability.
verified-commit
Creates a task-scoped commit only after validator and exact-tree postflight pass.
using-agent-skills
Selects and applies the smallest relevant set of skills for a task, preventing generic prompting and unused specialist guidance. Use at the start of every command, task, review, or repair cycle.
testing-patterns
Designs focused, hierarchical, regression, boundary, integration, and end-to-end tests for vertical-slice implementation. Use before and after implementation, and during test review.
test-hierarchy
Classifies and enforces the required unit, integration, local E2E, and cloud E2E test tier for a task or run.