菜单
Review a pull request for code quality, correctness, and project conventions. Use when the user asks to review a PR, code review, or examine changes on a branch. Accepts a GitHub PR URL, PR number, or local branch name.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Run end-to-end tests filtered by tag. Use when the user asks to run tests, run Playwright, or test a specific feature tag like @core or @attach.
Find exported symbols that are never imported by another file. Use when the user says "check exports", "unused exports" or asks to clean up exports.
Rebase the current branch onto its base branch, resolve all conflicts, and verify lint, i18n, and build pass. Use when the user asks to rebase, update, or sync a branch with its upstream base.
Backport commits or PRs from main to a release branch. Use when the user asks to backport, cherry-pick, or port changes between branches, or when resolving conflicts from a cherry-pick onto a release branch.
Bump the project version across all release branches and commit the changes. Use when the user asks to do a release or update the version on all branches.
Review project AI skills for duplication, stale references, mistakes, and structural issues. Use when the user asks to review skills, audit skills, check for duplicate skills, or verify skill quality.
| name | code-review |
| description | Review a pull request for code quality, correctness, and project conventions. Use when the user asks to review a PR, code review, or examine changes on a branch. Accepts a GitHub PR URL, PR number, or local branch name. |
Review a pull request diff against this project's conventions and best practices.
The user will provide one of the following:
Extract the remote and PR number from the URL.
https://github.com/openshift/lightspeed-console/pull/123 → remote
upstream, PR 123Then fetch and diff:
git fetch <remote> pull/<number>/head:pr-<number>
git diff <remote>/main...pr-<number>
Assume the PR is on upstream (openshift/lightspeed-console).
git fetch upstream pull/<number>/head:pr-<number>
git diff upstream/main...pr-<number>
The branch already exists locally. Determine its base branch by reading release-branches.md for the list of branches. For each branch, compute the merge-base and count the commits between them:
mb=$(git merge-base <branch> <candidate>)
git rev-list --count "$mb"..<branch>
The base branch is whichever candidate has the lowest commit count (fewest
commits between the merge-base and the branch). If counts are tied, prefer
main.
Then diff against the detected base:
git diff <base-branch>...<branch>
In all cases, also run git log --oneline <base>...<ref> to see the commit
messages.
Read the diff and surrounding context in changed files. Check for correctness,
security, project conventions (see AGENTS.md), React/Redux patterns, test
coverage, and maintainability.
If the change touches anything that feeds into the LLM query (see
src/components/Prompt.tsx and src/pageContext.ts), trace each interpolated
variable back to its source. Flag any source that can carry arbitrary strings
(e.g. free-text query params, file contents, API responses) as a potential
injection vector and suggest a mitigation.
Present findings grouped by severity:
For each finding: