Push the current branch and open a draft PR for Meshtastic-Android the repo way — baseline verified first, body drafted per CONTRIBUTING.md (WHY-first, categorized changes, screenshots for UI work). Use whenever work is ready to go up as a PR.
72
88%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Opens a PR the way this repo expects. The SOP lives in CONTRIBUTING.md → Pull Requests — read it now and follow it; this skill only adds the steps around it.
main unless told otherwise.spotlessApply spotlessCheck detekt assembleDebug test allTests). If it hasn't run since the last code change, run /baseline first — CI has failed repeatedly on skipped local checks. (The pre-push hook only gates detekt.)git status: nothing unintended staged. Never commit .agent_memory/. If docs/assets/screenshots/*.png are dirty from a test run (not an intentional UI change), restore them: git checkout -- docs/assets/screenshots.Draft per CONTRIBUTING.md → Pull Requests → Writing the description (WHY-first summary, then changes under the 🌟 New Features / 🛠️ Refactoring & Architecture / 🐛 Bug Fixes / 🧹 Chores categories that apply, Testing Performed section when tests were added/changed).
Screenshots (UI changes want them): CONTRIBUTING.md → Pull Requests → Screenshots owns the policy, and it allows either a GitHub-hosted upload or a committed image. When committing one, push it first and embed it by commit-pinned raw URL so it renders immediately:
https://raw.githubusercontent.com/<owner>/<repo>/<full-commit-sha>/<path/to/img.png>Pin to the SHA that contains the image, not the branch name.
git push -u origin HEAD
gh pr create --draft --base <target> --title "<type>: <summary>" --body-file <(printf '%s' "$BODY")--base is the target branch chosen in pre-flight (main unless told otherwise) — always pass it explicitly; omitting it silently uses the repo default.--ready if explicitly asked.🤖 Generated with [Claude Code](https://claude.com/claude-code)d003a21
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.