github-code-review

You can review local git changes by running the skill with the 'review-local' command in your current repository. It analyzes uncommitted diffs to identify security issues like SQL injection and plaintext passwords before you push your code.

To review code on a GitHub pull request, the skill uses gh or curl commands to fetch open pull request data. It analyzes detailed diffs and provides inline comments to highlight code quality issues and merge conflicts.

Yes, the code review skill performs security checks that specifically identify SQL injection risks and sensitive data exposure like plaintext passwords. It also detects merge conflicts to ensure your pull request maintains code quality.

You need git installed to run code review checks. For reviewing GitHub pull requests specifically, you also need either the gh command line tool or curl installed to interact with the GitHub API.

Yes, you can use this skill to check for merge conflicts in your git repository. It manages code review workflows by identifying and reporting merge conflicts along with common code quality issues in local changes and pull requests.

The best way to find plaintext passwords in your code changes is to run a local code review session. The skill automatically identifies sensitive data exposure across your git diffs before you push to a remote repository.