菜单
Quality-check repository pull requests and PR-thread communication. Use when creating, updating, reviewing, or validating PR titles, bodies, review comments, replies, or thread notes.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | pull-request-quality-check |
| description | Quality-check repository pull requests and PR-thread communication. Use when creating, updating, reviewing, or validating PR titles, bodies, review comments, replies, or thread notes. |
<type>[optional scope][optional !]: <description> and use commit-message-quality-check for type and breaking-change notation.> [!WARNING]
> This pull request was created with assistance from LLMs.
Use this alert for AI-assisted reviews, replies, and thread notes:
> [!WARNING]
> This comment was created with assistance from LLMs.
Omit an alert only when assistance was not significant.
## Testing, then ### AI-assisted inspections after automated checks, with Request: ... and nested AI-assisted result: .... Never describe AI-performed work as manual.prose-quality-check or security-check for applicable prose or sensitive content.Use Update Note, Discussion Note, or Review Note only when the task requests process, decision, or review-summary notes. Place Request addressed: ... after the required alert; group retrospective notes by meaningful theme, separate independently reviewable themes when requested, label inferences, and omit secrets, private paths, and hidden reasoning.
When using gh, write Markdown to a temporary file and pass --body-file. Verify the stored body with gh pr view --json body, correct quoting, and remove the temporary file.
Create, align, or review production-quality Python Flet applications across package and module architecture, presentation state, Flet controls, async lifecycle, persistence and I/O boundaries, uv dependency management, Ruff, strict mypy, pytest, 100% branch and statement coverage, GitHub Actions, Flet packaging, security, and developer documentation. Use for new Flet projects, large UI refactors, quality-baseline adoption, CI setup, release readiness, or reviews of pyproject.toml, uv.lock, src/tests layout, and Flet application code. Pair with software-documentation-maintenance for document ownership and with security-check for dependencies, secrets, and CI supply chain decisions.
Select a reviewed APM CLI version, then set up, pin, deploy, audit, and update APM-managed agent dependencies safely. Use when creating or editing apm.yml or apm.lock.yaml, choosing or installing APM, adding an Agent Skill, plugin, or MCP dependency, validating a pinned deployment, or preparing a cooldown-aware update proposal.
Review or create a BepInEx Mono mod for C# project and module structure, plugin identity, game compatibility, dependency boundaries, GitHub CI and release automation, packaging, release metadata, and verification. Use when implementing, reviewing, preparing a release for, or diagnosing quality gaps in a BepInEx 5 Mono plugin or its build and release workflow.
Maintain a canonical developer changelog and versioned release history. Use when adding or correcting Keep a Changelog entries, prerelease history, compatibility context, or release-source material; not for user-facing release notes or publishing.
Review or draft repository commit messages for Conventional Commits format, accurate change summaries, breaking-change footers, and required attribution trailers. Use before creating, amending, or validating a commit.
Set up and use an isolated Git worktree for repository implementation tasks. Use unless the user explicitly requests another workspace arrangement.