Standardizes PR creation for Meshtastic-Android with strict pre-flight checks and automated UI screenshot embedding.
Install
mkdir -p .claude/skills/pr-meshtastic && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17319" && unzip -o skill.zip -d .claude/skills/pr-meshtastic && rm skill.zipInstalls to .claude/skills/pr-meshtastic
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Push the current branch and open a draft PR for Meshtastic-Android the repo way — baseline verified first, body drafted per .github/copilot-pull-request-instructions.md (WHY-first, categorized changes), screenshots embedded via commit-pinned raw URLs. Use whenever work is ready to go up as a PR.Key capabilities
- →Verify local baseline checks before PR creation
- →Draft PR body following a WHY-first structure
- →Categorize changes under specific headings (Features, Improvements, Bug Fixes, Chores)
- →Embed commit-pinned raw URLs for UI screenshots in the PR body
- →Open a draft PR for Meshtastic-Android
How it works
The skill standardizes the PR process for Meshtastic-Android by running local baseline checks, drafting the PR body according to specific guidelines, embedding commit-pinned screenshots, and then pushing the branch to open a draft PR.
Inputs & outputs
When to use pr
- →Open a draft PR for Meshtastic-Android
- →Capture and link UI screenshots for a PR
- →Run local baseline checks before submitting work
About this skill
pr
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.
1. Pre-flight
- Target branch is
mainunless told otherwise. - On the default branch? Create a feature branch first.
- Baseline must be green this session (
spotlessApply spotlessCheck detekt detektTypeResolved assembleDebug test allTests). If it hasn't run since the last code change, run/baselinefirst. The push hook in.claude/hooks/pre-bash-guard.shruns onlydetekt. git status: nothing unintended staged. Never commit.agent_memory/. Ifdocs/assets/screenshots/*.pngare dirty and the change is not an intentional UI change, restore them:git restore --source=HEAD --staged --worktree -- docs/assets/screenshots.
2. Body
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.
3. Push and open
git push -u origin HEAD
gh pr create --draft --base <target> --title "<type>: <summary>" --body-file <(printf '%s' "$BODY")
--baseis the target branch chosen in pre-flight (mainunless told otherwise) — always pass it explicitly; omitting it silently uses the repo default.- Draft by default; only
--readyif explicitly asked. - Report the PR URL as a markdown link.
When not to use it
- →When creating a PR for a repository other than Meshtastic-Android
- →When the user does not want to follow the specific PR instructions in `.github/copilot-pull-request-instructions.md`
- →When local baseline checks are not required or are expected to be skipped
Limitations
- →The skill is specific to the Meshtastic-Android repository
- →The PR body must follow the SOP in `.github/copilot-pull-request-instructions.md`
- →Screenshots must be embedded using commit-pinned raw URLs
How it compares
This skill enforces a highly specific PR workflow for a particular repository, including mandatory local checks and structured body content with embedded screenshots, which is more rigorous than a generic PR creation process.
Compared to similar skills
pr side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| pr (this skill) | 0 | 3mo | Review | Intermediate |
| push | 0 | 5mo | Review | Beginner |
| proof-of-work | 1 | 9mo | No flags | Intermediate |
| reviewing-changes | 1 | 5mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by meshtastic
View all by meshtastic →You might also like
push
robinbeier
Push the current issue branch, create or update the GitHub pull request, link
proof-of-work
MadAppGang
Proof artifact generation patterns for task validation. Covers screenshots, test results, deployments, and confidence scoring.
reviewing-changes
bitwarden
Guides Android code reviews with type-specific checklists and MVVM/Compose pattern validation. Use when reviewing Android PRs, pull requests, diffs, or local changes involving Kotlin, ViewModel, Composable, Repository, or Gradle files. Triggered by "review PR", "review changes", "check this code", "Android review", or code review requests mentioning bitwarden/android. Loads specialized checklists for feature additions, bug fixes, UI refinements, refactoring, dependency updates, and infrastructure changes.
ck-refs
Fredrik-C
Find textual references for a symbol in C#, TypeScript, Kotlin, and Python/TSX files within scoped folders or explicit paths.
dev_unity_unreal
AllurinsX
dev_unity_unreal — an agent skill by AllurinsX.
kotlin-patterns
Sapeksh2001
Idiomatic Kotlin patterns, best practices, and conventions for building robust, efficient, and maintainable Kotlin applications with coroutines, null safety, and DSL builders.