メニュー
Generate a complete PR description from the project's pull-request template, populated with context derived from the current branch. Trigger keywords - pr description, pull request description, generate pr.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Address review comments on GitHub pull requests using the gh CLI. Use when the user wants to respond to feedback, make changes, or update a pull request. Trigger keywords - address review comments, update PR, respond to feedback.
Commit changes to the repository using git. Use when the user wants to save their work before creating a pull request. Trigger keywords - commit, save changes, git commit.
Create GitHub pull requests using the gh CLI. Use when the user wants to create a new PR, submit code for review, or open a pull request. Trigger keywords - create PR, pull request, new PR, submit for review, code review.
Update all Python dependencies across the kyma-companion Poetry subprojects, one at a time. For each dependency: update to latest (fall back to minor/patch on conflicts), run pre-commit-check, fix issues, commit.
| name | pr-description |
| description | Generate a complete PR description from the project's pull-request template, populated with context derived from the current branch. Trigger keywords - pr description, pull request description, generate pr. |
Generate a complete PR description from the project's pull-request template, populated with context derived from the current branch.
/pr-description [issue-number]
issue-number (optional): GitHub issue number to link in the "Related issue(s)" section.When this skill is invoked, follow these steps:
Read .github/pull-request-template.md from the repository root.
Run the following commands to understand what changed:
git log <base-branch>..HEAD --oneline
git diff <base-branch>...HEAD --stat
git diff <base-branch>...HEAD
Use the commit messages and diff to understand the nature and scope of the changes.
Based on the changes, select the most appropriate prefix mentioned in the workflow: .github/workflows/lint-pr-title.yml.
Produce a markdown output that fills in the template: .github/pull-request-template.md from the repository root.
Output a suggested PR title with the chosen prefix. Keep it under 70 characters. Example:
feat: add new api endpoint for user authentication
Present the output clearly so the user can copy it directly into a GitHub PR form: