.cursor/skills/code-review/SKILL.md
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.
npx skillsauth add openshift/lightspeed-console code-reviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
Present findings grouped by severity:
For each finding:
data-ai
Update the project version number across all files that contain it on the current branch. Use when bumping the version on a single branch only. For a full multi-branch release, use the release skill instead.
testing
Run Cypress tests filtered by tag. Use when the user asks to run tests, run Cypress, or test a specific feature tag like @core or @attach.
testing
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.
development
Review all README.md files in the repo for typos, errors, and outdated information. Use when the user asks to review READMEs, check documentation accuracy, or audit docs.