pr
Open a GitHub PR targeting the correct branch with the project template
npx skills add EverMind-AI/EverOS --skill pr --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# /pr Open a pull request on GitHub using the `gh` CLI and the repo's PR template. ## Steps 1. Confirm the branch and target: - Base branch is **`main`**. - Head branch should be a scoped branch such as `feat/*`, `fix/*`, `docs/*`, `ci/*`, `chore/*`, or `refactor/*`. 2. Ensure local checks pass first: ```bash make ci ``` Do not open a PR with failing lint/tests. 3. Push the branch: ```bash git push -u origin HEAD ``` 4. Create the PR, filling the template ([.github/PULL_REQUEST_TEMPLATE.md](../../../.github/PULL_REQUEST_TEMPLATE.md)): ```bash gh pr create --base main --fill-first ``` Then edit the body to complete each section: - **Summary** — what changed and why. - **Area** — tick the relevant box (architecture / benchmark / use case / docs / DX / CI-build-release). - **Verification** — paste the commands you ran (`make ci`, manual checks). - **Checklist** — tick honestly; don't tick boxes you didn't satisfy. - **Notes for Reviewers** — anything subtle. ## Notes - Keep the PR scoped to one area. Split unrelated changes. - If `make ci` was not fully run, say so in Verification rather than implying it passed. - Never retarget a community PR away from `main` unless a maintainer expl
- Steps
- Notes
make ci git push -u origin HEAD gh pr create --base main --fill-first
What does the pr skill do?
Open a GitHub PR targeting the correct branch with the project template
How do I install it?
Run `npx skills add EverMind-AI/EverOS --skill pr --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From EverMind-AI/EverOS, a repository with 11,801 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.