skills.rest
rusi
rusiCOMMUNITY
Explore all skills by this author →
GitHub

jr-code-review

Review current branch changes for debug code, dead code, rule violations, and correctness risks.

3|1|Updated Mar 28, 2026
Search Tags:#architecture#security#refactoring#maintainability#static-analysis#code-review
One-click install
npx skills add https://github.com/rusi/junior --skill jr-code-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jr-code-review
Source: https://github.com/rusi/junior/tree/main/agents/skills/jr-code-review
Command: npx skills add https://github.com/rusi/junior --skill jr-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Comprehensive expert review of current branch changes to identify debug code, dead code, rule violations, architectural concerns, and correctness risks, delivering actionable improvements.

Core Features & Use Cases

  • End-to-end evaluation of changes across four execution categories: Debug Code, Dead Code, Rule Violations, and Correctness.
  • Cross-cutting checks for architectural violations, design-pattern misuse, structure/layering concerns, and DRY violations.
  • Guidance for applying fixes, with a plan-style output that translates findings into concrete refactors or deletions.
  • Suitable before PRs, after feature work, or during cleanup to improve maintainability and production-readiness.

Quick Start

Invoke the jr-code-review workflow on the current branch to generate an actionable review report.

Frequently Asked Questions about jr-code-review

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

FAQPage Schema
How do I check my branch changes for dead code and rule violations before merging?▼

A comprehensive code review identifies dead code, debug code, rule violations, and correctness risks in your branch changes. It categorizes findings to ensure architectural integrity, DRY compliance, and maintainability before merging to the main branch.

What does a maintainability and architecture code review cover?▼

A maintainability and architecture code review covers cross-cutting checks for design-pattern misuse, structure and layering concerns, DRY violations, and security risks. It evaluates changes across debug, dead code, rule violations, and correctness categories to deliver actionable refactoring guidance.

What is the best way to find security and correctness risks in feature changes?▼

The best way to find security and correctness risks in feature changes is to perform a diff-focused expert code review. This process analyzes current branch changes and categorizes identified risks to ensure production-readiness and architectural integrity.

Can I get actionable refactoring guidance from a static code analysis?▼

Yes, you can get actionable refactoring guidance from static code analysis. The review translates identified architectural violations and rule violations into a plan-style output with concrete refactors or deletions to improve code quality.

When should I run a code review for cleanup and production-readiness?▼

You should run a code review for cleanup and production-readiness after feature completion, before creating PRs, or during general cleanup. This ensures all current branch changes are evaluated for debug code, dead code, and correctness risks before integration.

Related Skills

Explore More Software Engineering Skills→
QwenLMQwenLM
26.9k

docs-update-from-diff

Update docs/ directory files based on git diff code changes.

Official
Intermediate
CodySwannGTCodySwannGT
3

plan-lower-code-complexity

Lower cognitive complexity thresholds and identify functions exceeding the new limit.

Community
Intermediate
LuisSambranoLuisSambrano
7

code-review

Perform systematic code review and static analysis across multiple programming languages.

Community
Advanced
zizzfizzixzizzfizzix

code-review

Automate code review for architectural, security, and quality compliance.

Community
Advanced