pre-pr
GitHub在提交PR前检查代码变更，根据影响范围运行测试、lint和文档验证，收集证据并生成符合模板的PR描述，确保PR就绪。
触发场景
安装
npx skills add plastic-labs/honcho --skill pre-pr -g -y
SKILL.md
Frontmatter
{
"name": "pre-pr",
"description": "Prepare a Honcho change for a pull request to plastic-labs\/honcho. Invoke before opening a PR, when drafting a PR body, when asked if a branch is PR-ready, or when filling the pull request template. Checks required tests and docs, then writes Description \/ Proofs \/ Fixes."
}
Pre-PR checklist
Do this after the change works, before anyone opens the GitHub PR. Output is a filled template body — do not create the PR.
The template lives at .github/pull_request_template.md. Do not add extra sections.
1. Classify the diff
git diff main...HEAD --stat
Pick one primary kind: bug, feature, docs. Then decide layers:
| Surface touched | Required |
|---|---|
src/ (non-prompt) |
unit tests under the matching tests/ tree |
| deriver / dialectic / dreamer / LLM path | unit + consider live-llm (tests/live_llm) |
| queue, config hierarchy, multi-turn, SDK contract | unified (uv run python -m tests.unified.run) |
/v3 HTTP or deriver queue behavior |
/verify skill (runtime, not just pytest) |
public API, SDK exports, config.toml / settings, mintlify docs/ |
documentation in the matching file |
Skip a layer only with a one-line reason (e.g. "docs-only", "comment-only"). "When appropriate" is not a skip.
Invoke /verify when the runtime surface moved. Do not restate that skill here.
Lint/type before claiming tests are green: uv run ruff check src/ → uv run basedpyright → the pytest command for the layer.
2. Proofs
Collect evidence that belongs in the PR, not in the commit:
- command + pass/fail for what you ran
- a log snippet, screenshot, or file path that shows the new behavior
- for bugs: the failing case before vs after, if you have it
If /verify ran, the proofs are that session's output. Do not invent green runs.
3. Write the body
Fill the description and proofs portion of the pull request description template.
If there is a related GitHub issue, link it with Fixes #<N>.
版本历史
-
d11a764
当前 2026-11-02 23:33
移除Issue门控（Issue gate）硬限制步骤，不再强制要求维护者批准的Issue才能创建PR。
-
ed9fe6c
2026-10-19 06:32
新增贡献指南文档更新指引，强化Issue模板与安全报告路由规则。
- e153721 2026-08-27 20:28
