jr-code-review

Identify defects, test gaps, and design issues in code changes.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/bmsull560/Fabric_4L --skill jr-code-review-bmsull560
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jr-code-review
Source: https://github.com/bmsull560/Fabric_4L/tree/main/.windsurf/skills/jr-code-review
Command: npx skills add https://github.com/bmsull560/Fabric_4L --skill jr-code-review-bmsull560

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, rigorous approach to evaluating code changes, identifying defects, test gaps, and design or implementation issues before integration.

Core Features & Use Cases

  • Structured code review: evaluates correctness, edge cases, and maintainability of changes.
  • Gap detection: surfaces missing tests, inadequate coverage, and potential security concerns.
  • Feedback workflow: guides the reviewer to produce actionable, changes-requested notes aligned with acceptance criteria.

Quick Start

Log the upcoming changes ticket and PR diff, then generate a concise, actionable review summary.

Frequently Asked Questions about jr-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I perform a structured code review on a pull request diff?

Perform a structured code review by evaluating the pull request diff for correctness, edge cases, and maintainability. This process surfaces defects and design issues, generating actionable changes-requested notes aligned with acceptance criteria.

What is the best way to identify test coverage gaps in a code diff?

Identify test coverage gaps in a code diff by evaluating edge-case handling and correctness against acceptance criteria. This surfaces missing tests and inadequate coverage, ensuring reliability before integration.

How do I find security issues and defects in code changes before integration?

Find security issues and defects in code changes by applying structured evaluation criteria to the diff. This process flags potential vulnerabilities and reliability concerns, producing actionable review notes for mitigation.

Can I use diff analysis to check documentation consistency for task tickets?

Yes, you can use diff analysis to check documentation consistency by evaluating code changes against task ticket requirements. This ensures implementation aligns with documented acceptance criteria and maintains quality.

Does code review work for evaluating maintainability and design issues?

Code review works for evaluating maintainability and design issues by analyzing the implementation structure within the diff. It identifies architectural flaws and produces actionable changes-requested outputs to improve code quality.