Lerd Open PR
Developmentlerd-open-prLerd Open PR is an Agent Skill for development published in the lerd-env/lerd repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Draft and open a pull request the lerd way — issue-first, correct issue linking, human prose, none of the banned sections. Use when asked to open, prepare, or draft a PR for lerd. Never creates anything on GitHub without explicit per-action approval.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/lerd-env/lerd/blob/HEAD/.claude/skills/lerd-open-pr/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/lerd-open-pr, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Open a lerd PR
Every write to GitHub (create/edit/close/reopen/merge/comment on an issue or PR)
needs explicit approval each time. Draft the text, show it, and wait. Do not
run gh pr create or any state-changing gh command until the human says go.
Before the PR
- An issue should already exist for the work, framed as future work. If it doesn't, draft one and ask before creating it.
- Run
/lerd-preflight— the PR is not ready until the local gate is green. - Confirm the branch is off
main, notmainitself, and staged by explicit path (nevergit add -A).git statusfirst.
PR body — write it as a human would
Prose paragraphs, single-line (no column wrapping), explaining what changed and why. Then the issue link:
- Feature PR →
Closes #N(auto-closes on merge). - Bug-report issue →
Refs #N(stays open until the stable release ships). - Security issue →
Closes #N(closes once the fix merges to main).
Never include
- A Test plan section.
- A Verified / Tested / Manual testing section or trailer.
- A checklist of any kind (
- [ ]/- [x], "Release checklist"…). - A "Notes for reviewers" section — we own the project, there is no external reviewer.
file:linecitations, em dashes,Co-Authored-By, or "Generated with…" footers.- Prose about tests, TDD, or coverage; and don't mention incidental cleanup.
PR and issue comments
Casual plain prose. No markdown, no bullets, no hyphens — commas instead. Don't open with boilerplate like "Pulled it down and put it on my install." Vary it.
After pushing
Return immediately. Don't sit polling CI; failures get flagged by the human.