github-code-review

To review a GitHub pull request for security and correctness issues, this Skill inspects PR metadata and changed files, applying a structured checklist to surface risks. It then posts general or inline comments through the GitHub REST API or gh.

Yes, you can analyze local branch diffs before pushing. The Skill reviews staged or branch-level changes using git history and file-level context, returning critical issues, warnings, and positive notes in a reviewer-friendly layout.

Yes, authenticated GitHub access through gh or the REST API is required to gather diffs and post inline comments. The Skill needs this access to leave formal review feedback and decisions directly on the pull request.

The best way to structure code review feedback for maintainability is through a severity-based format. The Skill summarizes findings into critical issues, warnings, suggestions, and positive notes, ensuring a repeatable checklist for correctness and documentation.

Yes, this code review workflow supports testing and performance issue detection. It applies a repeatable checklist covering correctness, security, testing, performance, and documentation to evaluate changed files before code is merged.

Automated diff analysis requires a local git repository and authenticated GitHub access to function. It focuses strictly on changed files and metadata, meaning it may lack broader architectural context outside the current pull request diff.