Skip to content
cccskills
FreePublished on GitHub

pr

Create a pull request for the current branch

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

BuddiesOfBudgie/docs12 stars(GitHub 12 + cccskills 0)
Works withGitHub

Run score Not tested

See how to install

Files included (1)

  • SKILL.md1.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Create a Pull Request

You are creating a pull request for the current branch on Buddies of Budgie docs (Docusaurus / React / TypeScript site).

Step 1: Gather Context

Run these commands to understand the current state:

git status
git log --oneline main..HEAD
git diff main...HEAD --stat
git diff main...HEAD
git branch --show-current

If there are uncommitted changes, run the /commit skill first before proceeding.

Step 2: Determine PR Type

Based on the changes, choose the conventional commit prefix:

  • feat: - New feature or functionality
  • fix: - Bug fix
  • chore: - Maintenance, dependency updates, refactoring
  • docs: - Documentation content changes
  • refactor: - Code restructuring without behavior change

Step 3: Generate PR Content

Title format: <type>: <short description> (under 70 characters)

Body format:

## Summary

- <bullet point describing key change 1>
- <bullet point describing key change 2>
- <bullet point describing key change 3>

## Test plan

- [ ] `bun run build` completes successfully
- [ ] `bun run typecheck` passes
- [ ] `bun run check` passes
- [ ] Verified locally with `bun run start`
- [ ] <additional specific test steps>

If any commits include Assisted-by trailers, note that in the PR description (e.g., "AI-assisted - see commit trailers for details").

Step 4: Create the PR

Push the branch and create the PR:

git push -u origin HEAD
gh pr create --title "<title>" --body "$(cat <<'EOF'
<body content>
EOF
)"

Target branch: main (default)

Notes

  • Review all commits since divergence from main, not just the latest one
  • Ensure the title accurately reflects the overall change
  • Test plan should include bun run build, bun run typecheck, and bun run check

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

commit

Free

Stage and commit changes using Conventional Commits

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

BuddiesOfBudgie/docs12Updated Oct 20, 2026

See all skills by BuddiesOfBudgie

Report a problem with this skill