Check the current branch. If on main or master, create a new feature branch first:
- Pick a short, descriptive branch name based on the recent changes (e.g. add-start-skill)
- Fetch latest main: git fetch origin main (or master)
- Create the branch from latest main: git checkout -b <branch> origin/main
- Cherry-pick or re-apply any uncommitted/staged work onto the new branch
Commit any uncommitted changes with a clear commit message.
Push the branch: git push -u origin HEAD
Open the PR with gh pr create, targeting main. Write a concise title and summary based on the changes.
Return the PR URL to the user.

Más de este repositorio

mismo repositorio

Commit current work, push, open a pull request, wait for CI to pass, then merge.

Switch to main branch, pull latest changes, and optionally begin work on a task.

Manually test your work against the locally running app by making real API or HTTP requests.

Scaffold a new project from the fullstack or Rust CLI boilerplate. Use when starting a new codebase.

Comprehensive analysis of testing strategy and coverage across the codebase. Evaluates all test types and identifies gaps.

Reviews test coverage and testing strategy for recent code changes. Use before creating PRs to ensure changes are well-tested.

name	pr
description	Commit current work, push, and open a pull request against main.
user_invocable	true

Run the following steps:

Check the current branch. If on main or master, create a new feature branch first:
- Pick a short, descriptive branch name based on the recent changes (e.g. add-start-skill)
- Fetch latest main: git fetch origin main (or master)
- Create the branch from latest main: git checkout -b <branch> origin/main
- Cherry-pick or re-apply any uncommitted/staged work onto the new branch
Commit any uncommitted changes with a clear commit message.
Push the branch: git push -u origin HEAD
Open the PR with gh pr create, targeting main. Write a concise title and summary based on the changes.
Return the PR URL to the user.