Skip to content
cccskills
FreePublished on GitHubEnglish overview

pr

Opens a GitHub pull request from a scoped branch to `main` using the repository’s template. It checks that `make ci` passes, pushes the branch, and guides completion of the summary, change area, verification, checklist, and reviewer notes.

OriginalShow the original description

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

EverMind-AI/EverOS13,704 stars(GitHub 13,704 + cccskills 0)
Works withGitHub

Run score Not tested

See how to install

Good for

  • Opening a pull request for a completed change
  • Filling out the repository’s PR template
  • Recording CI and manual verification results
  • Creating a PR from a scoped feature or fix branch

Overview

What it does

Uses the GitHub CLI gh to open a pull request from the current working branch to main. Before creating it, the skill confirms the branch and target, then runs make ci to check that local checks pass. It pushes the branch and prepares the pull request body using the repository’s template.

The body covers what changed and why, the relevant area, verification commands, a checklist, and notes for reviewers. It records only checks that were actually completed; if make ci was not run to completion, the Verification section says so. Each pull request is kept focused on one area.

When it helps

Use it after finishing a feature or fix when you want to request a review. It also helps organize the change and its verification steps into the template’s sections.

Example requests

  • “Open a pull request from this branch to main.”
  • “Fill in the template with the changes and verification results, then open the PR.”
  • “Create a fix PR that includes the make ci result.”

Notes

The GitHub CLI gh and make ci are required. If checks fail, the skill does not create the pull request.

This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.

Document check

AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).

SafetyAre sending data, deleting files, and running commands disclosed?
AGoodIt blocks PR creation on failed checks and requires honest verification notes.
Easy setupDoes it need few tools or API keys, and are they documented?
AGoodIt names the GitHub CLI `gh` and `make ci` as requirements.

Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 29, 2026. Treat it as a guide and read the original before installing.

Disagree? Request a re-evaluation

Tell us which point is wrong and why. No login needed. We will check it against the SKILL.md, redo the evaluation, and show the result here.

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

Files included (1)

  • SKILL.md1.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

/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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

add-memory-kind

FreeSummary

Guide developers through adding a persisted business memory type. Choose Markdown, SQLite, and LanceDB storage and a Markdown file strategy, then wire up schemas, repositories, and writers across the layers the data needs.

  • Adding a new persisted business record type
  • Choosing storage for searchable memory
  • Wiring a daily Markdown log with database indexes
EverMind-AI/EverOS13.7KUpdated Oct 29, 2026

commit

FreeSummary

Review the current Git changes and recent history, then create a focused commit with a Conventional Commits message. The skill helps stage only related files, follow the required format, and address hook failures before committing.

  • Creating a commit for a focused code change
  • Staging only related files from a mixed working tree
  • Writing a Conventional Commits message
EverMind-AI/EverOS13.7KUpdated Oct 29, 2026

new-branch

FreeSummary

Creates a scoped Git branch from the updated `main` branch using the project’s naming convention. It selects a prefix for feature work, fixes, docs, CI, maintenance, or refactoring, then adds a concise lowercase, hyphenated name.

  • Starting a feature branch
  • Creating a bug fix branch
  • Preparing a docs or CI change
EverMind-AI/EverOS13.7KUpdated Oct 29, 2026

release

FreeSummary

Prepare and publish a versioned everos release to PyPI. The skill guides version and changelog updates, the tag-triggered workflow, its approval step, and review and publication of the resulting GitHub Release draft.

  • Preparing a patch, minor, or major release
  • Publishing a release candidate to PyPI
  • Reviewing and publishing the GitHub Release draft
EverMind-AI/EverOS13.7KUpdated Oct 29, 2026

See all skills by EverMind-AI

Report a problem with this skill