2.9 KiB
Prepared via the openclaw-github-authoring skill template copy.
Draft this PR body for the user instead of replaying every heading as a questionnaire when the intent is already clear.
Ask only a very short grouped follow-up for missing high-value facts such as branch context, verification, or risk.
Automatically redact obvious secrets, tokens, cookies, passwords, emails, phone numbers, and similar sensitive strings before filing when the technical meaning remains intact.
If explicit title, base branch, head branch, or proof of an existing remote head branch is still missing after the brief follow-up, respond with exactly NOT_ENOUGH_INFO.
Summary
Describe the problem and fix in 2–5 bullets:
- Problem:
- Why it matters:
- What changed:
- What did NOT change (scope boundary):
Change Type (select all)
- Bug fix
- Feature
- Refactor
- Docs
- Security hardening
- Chore/infra
Scope (select all touched areas)
- Gateway / orchestration
- Skills / tool execution
- Auth / tokens
- Memory / storage
- Integrations
- API / contracts
- UI / DX
- CI/CD / infra
Linked Issue/PR
- Closes #
- Related #
User-visible / Behavior Changes
List user-visible changes (including defaults/config).
If none, write None.
Security Impact (required)
- New permissions/capabilities? (
Yes/No) - Secrets/tokens handling changed? (
Yes/No) - New/changed network calls? (
Yes/No) - Command/tool execution surface changed? (
Yes/No) - Data access scope changed? (
Yes/No) - If any
Yes, explain risk + mitigation:
Repro + Verification
Environment
- OS:
- Runtime/container:
- Model/provider:
- Integration/channel (if any):
- Relevant config (redacted):
Steps
Expected
Actual
Evidence
Attach at least one:
- Failing test/log before + passing after
- Trace/log snippets
- Screenshot/recording
- Perf numbers (if relevant)
Human Verification (required)
What you personally verified (not just CI), and how:
- Verified scenarios:
- Edge cases checked:
- What you did not verify:
Review Conversations
- I replied to or resolved every bot review conversation I addressed in this PR.
- I left unresolved only the conversations that still need reviewer or maintainer judgment.
If a bot review conversation is addressed by this PR, resolve that conversation yourself. Do not leave bot review conversation cleanup for maintainers.
Compatibility / Migration
- Backward compatible? (
Yes/No) - Config/env changes? (
Yes/No) - Migration needed? (
Yes/No) - If yes, exact upgrade steps:
Failure Recovery (if this breaks)
- How to disable/revert this change quickly:
- Files/config to restore:
- Known bad symptoms reviewers should watch for:
Risks and Mitigations
List only real risks for this PR. Add/remove entries as needed. If none, write None.
- Risk:
- Mitigation: