メニュー
Step-by-step workflow for committing staged changes and opening a pull request in the lightspeed-service repo.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/openshift/lightspeed-service --skill raise-prコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Resolve a CVE vulnerability issue from Jira. Reads the CVE details, assesses impact, and either marks "not affected" with a Jira comment and transition, bumps the affected dependency, or implements a code fix. Use when the user says "cve", "resolve CVE", or provides a CVE Jira issue.
Assess whether an application is ready to migrate to OpenShift. Use when the user describes an application and asks about migration, containerization, or moving to Kubernetes/OpenShift.
Triage production incidents involving data corruption, data loss, slow performance, or outages. Classify severity and recommend immediate actions.
SKILL.md を表示中
SOC 職業分類に基づく
| name | raise-pr |
| description | Step-by-step workflow for committing staged changes and opening a pull request in the lightspeed-service repo. |
| disable-model-invocation | true |
git fetch upstream
git branch --show-current
git log --oneline upstream/main..HEAD
git diff upstream/main --stat
gh pr list --head "$(git branch --show-current)" --state open
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:
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> ...
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.
git add -A # or only the relevant files
git commit -m "<message>"
git push -u origin HEAD
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
gh pr create --title "<JIRA-ID>: <description>" --body "$(cat <<'EOF'
<populated template>
EOF
)"
Return the PR URL to the user when done.