From vgv-wingspan
Stages changes, commits using Conventional Commits spec and project conventions, pushes branch, runs validation/CI checks, and opens pull request on GitHub or GitLab.
npx claudepluginhub verygoodopensource/very_good_claude_code_marketplace --plugin vgv-wingspanThis skill is limited to using the following tools:
Stage uncommitted changes, commit them, push the branch, and open a pull request on the project's Git hosting platform.
Commits changes with conventional messages, runs tests, rebases onto default branch, and pushes feature branch for PR review. Use when work is complete.
Creates new git branch if on main, commits and pushes changes, adapts PR template to git diffs, and opens GitHub pull request with conventional commit title.
Creates GitHub pull requests from current branch: analyzes git diffs, categorizes changes, generates ticket-ID prefixed titles and templated bodies, runs gh pr create. Use after commits for review.
Share bugs, ideas, or general feedback.
Stage uncommitted changes, commit them, push the branch, and open a pull request on the project's Git hosting platform.
SKIP_CHECKS)SKIP_CHECKS)BASE_BRANCH (determined in Step 2).Use this skill when:
$ARGUMENTS
This may include skip-checks, a ticket number (e.g. VGV-123), a short description, or be empty.
Check whether the argument contains skip-checks. Store as SKIP_CHECKS (boolean).
Extract the ticket number or short description from the remaining argument text (if any).
Skip this step if SKIP_CHECKS is true.
Detect and run the project's formatter, linter, and test runner.
If any command fails, report the error and stop. Do not proceed until all checks pass.
Run in parallel:
git branch --show-current
git status --short
git diff --cached
git diff
main or master, warn the user and stop.git log <BASE_BRANCH>..HEAD --oneline. If there are no commits ahead of BASE_BRANCH, inform the user there is nothing to commit or push, and stop.Use AskUserQuestion:
Question: "Which branch should this PR target?"
Options:
main (default)developStore as BASE_BRANCH.
Use the create-commit skill with the single-commit argument to stage files and produce a single conventional commit message.
Consult references/push.md to push the branch and handle any failures.
Skip this step if SKIP_CHECKS is true.
Consult references/ci-checks.md to discover and run checks locally from .github/workflows/ci.yaml.
If any check fails, report the errors and stop. Do not proceed until all checks pass.
Run in parallel:
git log <BASE_BRANCH>..HEAD --oneline
git log <BASE_BRANCH>..HEAD --format="%s%n%b"
git diff <BASE_BRANCH>..HEAD --stat
Extract the ticket number from the branch name (e.g. feat/VGV-59-... → VGV-59) or from the argument.
Follow Conventional Commits summarizing the overall change:
type(scope): short description
Check for a template:
cat .github/PULL_REQUEST_TEMPLATE.md 2>/dev/null
feat → ✨ New featurefix → 🛠️ Bug fixrefactor → ♻️ Refactordocs → 📝 Documentationtest → 🧪 Testschore/build/ci → 🔧 Maintenancereferences/pull-request-template.md for the default template and filling rules.Output the proposed PR:
## Proposed PR
**Title:** `type(scope): short description`
**Description:**
...
Use AskUserQuestion:
Question: "Do you want me to create this PR?"
Options:
references/pr-cli.md to detect the available CLI tool, check for an existing PR, and create it.