CtrlK
BlogDocsLog inGet started
Tessl Logo

pr

Open a GitHub PR targeting the correct branch with the project template

62

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/pr/SKILL.md
SKILL.md
Quality
Evals
Security

/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:
    make ci
    Do not open a PR with failing lint/tests.
  3. Push the branch:
    git push -u origin HEAD
  4. Create the PR, filling the template (.github/PULL_REQUEST_TEMPLATE.md):
    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 explicitly asks for it.
Repository
EverMind-AI/EverOS
Last updated
First committed

Is this your skill?

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.