npx skills add ...
npx skills add openshift/lightspeed-service --skill raise-pr
npx skills add openshift/lightspeed-service --skill raise-pr
Step-by-step workflow for committing staged changes and opening a pull request in the lightspeed-service repo.
Present the summary and ask before proceeding:
"You are currently on branch
<branch>. It has<N>commit(s) ahead ofupstream/maintouching:<files>. [If an open PR exists]: This branch already has an open PR:<url>. Pushing here would add commits to that existing PR. Should I create a new branch fromupstream/main(recommended), or use the current branch?"
Do not continue until the user answers.
If creating a new branch — git carries uncommitted changes automatically:
Never branch from origin/main — the fork may have stale commits that will appear in the PR.
Run in order and fix all failures before proceeding:
make test-unitmake test-integrationmake verifyIf a Jira issue ID has not been provided, ask the user for it before proceeding.
Commit message: short imperative sentence, no period, no conventional prefix, no Jira ID.
Title format: <JIRA-ID>: <same short imperative sentence as commit>
Read .github/PULL_REQUEST_TEMPLATE.md and populate all sections:
Closes #<github-issue> if it resolves one; always link the Jira ticket
Return the PR URL to the user when done.
git fetch upstream
git checkout -b <type>/<short-description> upstream/main
# cherry-pick intended commits from the old branch if needed
git cherry-pick <sha1> <sha2> ...git add -A # or only the relevant files
git commit -m "<message>"
git push -u origin HEADgh pr create --title "<JIRA-ID>: <description>" --body "$(cat <<'EOF'
<populated template>
EOF
)"