Skip to content
cccskills
FreePublished on GitHub

pr

Commit the current changes on a new branch, push, and open a GitHub PR following this repo's conventions.

The English summary is being prepared. Showing the original description.

howard36/probase20 stars(GitHub 20 + cccskills 0)
Works withGitHub

Run score Not tested

See how to install

Files included (1)

  • SKILL.md1.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Optional PR title or branch hint: $ARGUMENTS

  1. Run /verify first. Do not open a PR with failing lint, Prettier, or build.
  2. If on main, create a branch: descriptive kebab-case, no prefix (e.g. one-time-use-invites). Derive the name from the change or from the arguments.
  3. Review git status and git diff before staging. Never stage .env* files (other than .env.example).
  4. Commit with a Conventional Commits subject: <type>: <short imperative description>, lowercase description (types: feat, fix, refactor, chore, docs, style, ci). End the message with the Co-Authored-By and Claude-Session trailers the session provides.
  5. Push with git push -u origin <branch>.
  6. Open the PR with gh pr create. Title matches the commit subject. Body: what changed and why, in a few sentences. If the PR includes a Prisma migration, say so in the body and note it will apply to production on merge.
  7. Reply with the PR URL.

PRs are rebased into main, so keep commits clean and self-contained rather than relying on squash.

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

prisma-migrate

Free

Create a Prisma migration for a schema change against the local database. Use after editing prisma/schema.prisma.

The English summary is being prepared. Showing the original description.

howard36/probase20Updated Sep 26, 2026

verify

Free

Verify a change is done by running lint, the Prettier check, the test suites, and a production build. Use after finishing any code change and before opening a PR.

The English summary is being prepared. Showing the original description.

howard36/probase20Updated Sep 26, 2026

See all skills by howard36

Report a problem with this skill