pre-pr
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.
How do I install this agent skill?
npx skills add https://github.com/plastic-labs/honcho --skill pre-prIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill is a developer utility for preparing pull request descriptions by analyzing branch changes and running tests. It uses standard tools like git and uv to automate project-specific workflows for the Honcho repository. No malicious patterns or security risks were identified.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
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>.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/plastic-labs/honcho/pre-pr">View pre-pr on skillZs</a>