SkillsAdd

plastic-labs/honcho

pre-pr

Prepare a Honcho change for a pull request to plastic-labs/honcho.

First seen Aug 20, 2026

Installation

$ npx skills add plastic-labs/honcho --skill pre-pr
View on skills.sh ↗ GitHub repository ↗

Summary

  • 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 the linked issue, required tests and docs, then writes Description / Proofs / Fixes.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

agent-browser Shared topics
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
azure-diagnostics Shared topics
microsoft/azure-skills

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …

568.9K installs
azure-validate Shared topics
microsoft/azure-skills

Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure…

567.7K installs
supabase-postgres-best-practices Shared topics
supabase/agent-skills

Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill …

391.6K installs

Also in this package

Other skills from plastic-labs/honcho.

npx skills add plastic-labs/honcho
honcho-integration 838 honcho-cli 528 migrate-honcho 345 migrate-honcho-ts 345 honcho-memory 93 verify 90

Browse all from plastic-labs/honcho

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 7.1K
License LICENSE
Default branch main
Open issues 76
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,485 B
  • docs SUMMARY.md 304 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 43 installs

SKILL.md

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/pullrequesttemplate.md. Do not add extra sections.

1. Issue gate (hard stop)

A PR without a maintainer-approved issue will be closed.

gh issue view <N> --repo plastic-labs/honcho --json number,title,labels,state

Stop if any of these fail:

  • no issue number, or the issue is not in plastic-labs/honcho
  • issue is closed (unless this PR is explicitly reopening it)
  • labels do not include maintainer-approved

Say which check failed. Do not draft a PR body around it.

2. 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.

3. 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.

4. Write the body

Fill the description, proofs, checklist portion of the pull request description template. Make sure to link the related github issue, otherwise the PR will be auto-closed.