Automated summary
Automates opening a pull request in the Meshtastic-Android repo by first verifying the baseline, drafting the body per the repo's SOP, and embedding screenshots through commit-pinned raw URLs.
Strengths
- Requires a freshly run full baseline (spotless, detekt, assembleDebug, tests) before publishing, preventing the repeated CI failures caused by skipped local checks
- Drafts the PR body following .github/copilot-pull-request-instructions.md, with a WHY-first summary and changes grouped into feature/improvement/bug-fix/chore categories
- Handles screenshots reliably by committing them to the branch and referencing them with raw URLs pinned to the commit SHA so they render right away
- Sanity-checks git state beforehand: unintended staged files, .agent_memory/, and screenshot PNGs dirtied by test runs
Limitations
- Tightly coupled to the Meshtastic-Android repository and its internal SOP file, so it is not portable as-is
- Assumes a /baseline command and a detekt pre-push hook already exist in the environment
- Does not cover code review, merging, or marking the PR ready without an explicit request
Use it when a set of changes is ready to go up as a pull request in the Meshtastic-Android repository.
Avoid it for repositories without a PR instruction file or a /baseline command, or when the work is still in progress and not meant to be published yet.
Security analysis
CautionThe skill automates pushing a branch and opening a draft PR using standard Git and GitHub CLI commands. There are no destructive, exfiltrating, or obfuscated actions, but it does interact with remote systems and can alter repository state, so it warrants caution rather than a completely safe rating.
- •Executes `git push` and `gh pr create`, which modify the remote repository and create pull requests — legitimate but has network and repository side effects.
- •Uses `git checkout -- docs/assets/screenshots` to discard local changes, but scoped to screenshot files and only after a status check.
Examples
Push my current branch and open a draft PR against main for Meshtastic-Android.Ship this UI change as a draft PR — commit the new screenshots, push, and embed them with commit-pinned raw URLs in the body.Create the PR the repo way: run /baseline first if it hasn't run since my last change, then draft the body per the copilot pull request instructions.name: pr description: 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. disable-model-invocation: true
pr
Opens a PR the way this repo expects. The SOP lives in .github/copilot-pull-request-instructions.md — 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 assembleDebug test allTests). If it hasn't run since the last code change, run/baselinefirst — CI has failed repeatedly on skipped local checks. (The pre-push hook only gates detekt.) git status: nothing unintended staged. Never commit.agent_memory/. Ifdocs/assets/screenshots/*.pngare dirty from a test run (not an intentional UI change), restore them:git checkout -- docs/assets/screenshots.
2. Body
Draft per the SOP file (WHY-first summary, then changes under the 🌟 Features / 🛠️ Improvements / 🐛 Bug Fixes / 🧹 Chores categories that apply, Testing Performed section when tests were added/changed).
Screenshots (UI changes want them): commit the PNGs on the branch, push, then embed with commit-pinned raw URLs so they render in the PR body 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. - End the body with:
🤖 Generated with [Claude Code](https://claude.com/claude-code) - Report the PR URL as a markdown link.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/open-draft-pr-for-meshtastic-android-mrzxurao/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/open-draft-pr-for-meshtastic-android-mrzxurao' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/open-draft-pr-for-meshtastic-android-mrzxurao/download' --output '.skill-downloads/open-draft-pr-for-meshtastic-android-mrzxurao/SKILL.md.part' && mv '.skill-downloads/open-draft-pr-for-meshtastic-android-mrzxurao/SKILL.md.part' '.skill-downloads/open-draft-pr-for-meshtastic-android-mrzxurao/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/open-draft-pr-for-meshtastic-android-mrzxurao/SKILL.md' && test -s '.skill-downloads/open-draft-pr-for-meshtastic-android-mrzxurao/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/pr' && cp -R '.skill-downloads/open-draft-pr-for-meshtastic-android-mrzxurao' '.claude/skills/pr'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/open-draft-pr-for-meshtastic-android-mrzxurao'openskills read 'open-draft-pr-for-meshtastic-android-mrzxurao'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/open-draft-pr-for-meshtastic-android-mrzxurao/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.