Skill11.6k repo starsupdated today
pr
The `pr` skill automates opening GitHub pull requests for the EverOS project with correct branch targeting and template completion. Use it after local CI checks pass to create properly scoped pull requests that route feature and fix branches to `dev` and hotfix branches to `master`, with all required template sections completed.
Install in Claude Code
Copygit clone --depth 1 https://github.com/EverMind-AI/EverOS /tmp/pr && cp -r /tmp/pr/.claude/skills/pr ~/.claude/skills/prThen start a new Claude Code session; the skill loads automatically.
Definition
SKILL.md
# /pr
Open a pull request on GitHub using the `gh` CLI and the repo's PR template.
## Steps
1. Confirm the branch and target:
- `feat/*`, `fix/*` → base **`dev`**.
- `hotfix/*` → base **`master`** (then a follow-up PR/sync into `dev`).
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 dev --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.
- A `hotfix` is not done until it has landed on **both** `master` and `dev`.More from this repository
commitSkill
Stage and create a Conventional Commits message for the current change
new-branchSkill
Create a branch following the project's GitFlow Lite model
add-memory-kindSkill
Add a new business memory kind end-to-end. Pick the storage combination (Markdown / SQLite / LanceDB), pick the markdown strategy (daily-log / skill-named / single-file), then wire up the schema(s), repo(s), and writer(s).