메뉴
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.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/lerd-env/lerd --skill lerd-open-pr명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Add or extend a lerd framework definition (a new PHP framework or a new major version) as versioned YAML in the lerd-frameworks store. Use whenever the task involves framework detection, per-framework workers, env wiring, doctor checks, custom commands, or scaffolding — never branch on a framework name in Go.
Add or edit a lerd service preset (database, cache, search engine, admin dashboard) as YAML in the lerd-services store. Use whenever the task is to add a new service, a new version of a service, or wire a service into projects — never add services in Go.
Run the full local verification gate for lerd before committing — build, test, vet, gofmt, UI tests, installer tests, then install the local build and smoke-test. Use before every commit or PR, and whenever asked to "verify", "check CI locally", or "make sure it's green".
SOC 직업 분류 기준
SKILL.md 표시 중
| name | lerd-open-pr |
| description | 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. |
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.
/lerd-preflight — the PR is not ready until the local gate is green.main, not main itself, and staged by explicit
path (never git add -A). git status first.Prose paragraphs, single-line (no column wrapping), explaining what changed and why. Then the issue link:
Closes #N (auto-closes on merge).Refs #N (stays open until the stable release ships).Closes #N (closes once the fix merges to main).- [ ] / - [x], "Release checklist"…).file:line citations, em dashes, Co-Authored-By, or "Generated with…" footers.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.
Return immediately. Don't sit polling CI; failures get flagged by the human.