to-quality-pr
Quality-gated ship: run ensure-quality, then commit dirty gated work and open a triage PR whose body is the gate summary (LOW_RISK_MERGE / MEDIUM_REVIEW / HIGH_HOLD). Guardrail against AI slop leaving the machine. Use when the user asks to to-quality-pr, quality PR, gate and PR, ship a PR, or open a PR after changes; after finishing substantive or AI-generated work when the next step is a pull request; prefer this over committing or opening a PR without a quality gate.
- License 许可
- GPL-3.0
- 所属仓库
- gambitph/Ahentic
- 最近更新
- 2026-08-15
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- to-quality-pr
- description
- Quality-gated ship: run ensure-quality, then commit dirty gated work and open a triage PR whose body is the gate summary (LOW_RISK_MERGE / MEDIUM_REVIEW / HIGH_HOLD). Guardrail against AI slop leaving the machine. Use when the user asks to to-quality-pr, quality PR, gate and PR, ship a PR, or open a PR after changes; after finishing substantive or AI-generated work when the next step is a pull request; prefer this over committing or opening a PR without a quality gate.
02 资源文件 3
- 参考文档agents/openai.yaml125 B
- 参考文档reference/pr-body.md3.9 KB
- 参考文档reference/ship.md2.3 KB
03 SKILL.md 正文
To quality PR
Ship guardrail: gate first, then PR.
Runs ensure-quality to completion, then commits the gated worktree and opens a pull request whose description is the gate output in a triage-first format.
Reviewers should decide merge-now vs inspect-first from the PR header alone.
Does not re-implement the gate. Anti-slop / review / test / docs / lint live only in ensure-quality.
Stages (order): ensure-quality → ship (branch → commit → push → PR).
Load reference/ship.md and reference/pr-body.md only when ship runs.
When to run
Fire this skill when any of these hold:
- The user asks for to-quality-pr / quality PR / gate and PR / ship a PR / open a PR after changes.
- You finished substantive or AI-generated source changes and the natural next step is a pull request.
- You would otherwise commit and open a PR without a quality gate.
Prefer ensure-quality alone when the user wants a local gate only (no commit, no PR). Skip auto-invoke for pure Q&A, exploration with no edits, or when the user said to keep iterating without shipping.
Preconditions
- Synthesize intent the same way ensure-quality requires - authoritative acceptance criteria for the gate.
- Confirm ship target. Record base branch (same default resolution as ensure-quality's fixed-point base) and whether the user named a PR title or branch.
- Dirty scope. Note that ship will include all work ensure-quality gated (committed-since-fixed-point plus unstaged/staged fixes the gate applied).
Completion: intent written; ship target named; then enter the pipeline.
Pipeline
1. Ensure quality
Read and execute .cursor/skills/ensure-quality/SKILL.md fully for this worktree.
Honor its HITL pauses; do not ship past unresolved ask-user findings.
Capture its Summary fields verbatim for the PR body - do not invent a second risk score.
If Summary Ship readiness is blocked (or the gate aborts): stop.
Leave the worktree dirty.
Emit a short blocked report (intent, risk, remaining findings).
Do not commit.
Do not push.
Do not open a PR.
If the gate reports ready with an empty diff (nothing to gate): stop and say so - no empty PR.
2. Ship
Only when ensure-quality ended Ship readiness: ready with a non-empty gated change set.
- Read
reference/ship.mdand follow it (branch, commit, push). - Read
reference/pr-body.md, map Summary → triage verdict + body, open the PR. - Return the PR URL and the triage verdict to the user.
Completion: PR URL exists (or ship blocked with a concrete git/gh error); verdict stated; worktree clean relative to the pushed commit unless the user forbade commit.
Triage verdict (summary)
Derived in reference/pr-body.md from ensure-quality Risk (+ caution signal):
| Verdict | Meaning for reviewers |
|---|---|
LOW_RISK_MERGE |
Skim intent + diffstat; merge if CI green |
MEDIUM_REVIEW |
Read Caution and linked hunks before merge |
HIGH_HOLD |
Do not merge until Caution is checked; open as draft unless the user already approved shipping high risk |
Empty Caution on Medium or High is a skill failure - rewrite before gh pr create.
04 同仓库更多 Skills
writing-for-agents
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
wp-rest-api
Use when building, extending, or debugging WordPress REST API endpoints/routes: register_rest_route, WP_REST_Controller/controller classes, schema/argument validation, permission_callback/authentication, response shaping, register_rest_field/register_meta, or exposing CPTs/taxonomies via show_in_rest.
wp-project-triage
Use when you need a deterministic inspection of a WordPress repository (plugin/theme/block theme/WP core/Gutenberg/full site) including tooling/tests/version hints, and a structured JSON report to guide workflows and guardrails.
wp-plugin-directory-guidelines
Use when reviewing WordPress plugins for GPL compliance, checking license headers or compatibility, evaluating upsell/freemium/trialware patterns, validating plugin naming or trademark rules, checking plugin slugs, understanding why a plugin was rejected from WordPress.org, or answering any question about the 18 WordPress.org Plugin Directory guidelines — even if the user doesn't mention 'guidelines' explicitly.
wp-plugin-development
Use when developing WordPress plugins: architecture and hooks, activation/deactivation/uninstall, admin UI and Settings API, data storage, cron/tasks, security (nonces/capabilities/sanitization/escaping), and release packaging.
wp-performance
Use when investigating or improving WordPress performance (backend-only agent): profiling and measurement (WP-CLI profile/doctor, Server-Timing, Query Monitor via REST headers), database/query optimization, autoloaded options, object caching, cron, HTTP API calls, and safe verification.