skills.rest
Hunt-Gather-Create
Hunt-Gather-CreateOFFICIAL
Explore all skills by this author →
WebsiteGitHub

pr-ready

Identify and summarize code quality changes needed to prepare a PR.

1|Updated Jan 24, 2026
Search Tags:#react#pr#quality-assurance#code-review#code-cleanup#dry-principles#javascript-typescript
One-click install
npx skills add https://github.com/Hunt-Gather-Create/_R1 --skill pr-ready
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-ready
Source: https://github.com/Hunt-Gather-Create/_R1/tree/main/.claude/skills/pr-ready
Command: npx skills add https://github.com/Hunt-Gather-Create/_R1 --skill pr-ready

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR readiness often suffers from leftover debug statements, duplicated logic, and poorly structured React components which slow reviews and introduce risk. This Skill provides a structured checklist and automated guidance to clean code before submitting a PR, reducing back-and-forth and rework.

Core Features & Use Cases

  • Debug statement cleanup: detect and propose removal or proper logging.
  • DRY analysis: identify duplicated logic and opportunities to extract utilities.
  • React component structure review: flag large components, prop drilling paths, and improper prop types.
  • Unused/imports checks: surface unused imports and dead code for removal.
  • Use Case: a feature branch with multiple UI components can be pruned to smaller, composable pieces before review.

Quick Start

Run pr-ready on your branch to scan changed files and generate a cleanup plan for the PR.

Frequently Asked Questions about pr-ready

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

FAQPage Schema
How do I prepare a React codebase for a pull request review?▼

Preparing a React codebase for a pull request review involves scanning changed branch files to detect debug statements, DRY violations, and prop drilling. The analysis enumerates findings and recommendations to guide code cleanup and reduce review rework.

What is the best way to find leftover debug statements before submitting a PR?▼

The best way to find leftover debug statements before submitting a PR is to scan changed files on your current branch. This process detects debug logs and proposes removal or proper logging integration to ensure clean code.

How do I identify DRY violations and duplicated logic in JavaScript and TypeScript files?▼

To identify DRY violations and duplicated logic in JavaScript and TypeScript files, run a DRY analysis on your current branch. This detects repeated patterns and recommends extracting duplicated blocks into shared utilities.

Can I detect React prop drilling and large component structures automatically?▼

Yes, you can detect React prop drilling and large component structures automatically by scanning changed branch files. The review flags oversized components, prop drilling paths, and improper prop types to guide component decomposition.

Does this PR cleanup check surface unused imports and dead code?▼

Yes, this PR cleanup check surfaces unused imports and dead code for removal. It enumerates these findings alongside debug statements and DRY violations to deliver a structured cleanup plan for your feature branch.

Related Skills

Explore More Software Engineering Skills→
farzanmrzfarzanmrz

feature-lint

Resolve residual Biome lint findings on changed feature branch files.

Community
Advanced
marcioaltoemarcioaltoe
14

git-pr-creation

Create a GitHub pull request from the current branch into dev with a structured body.

Community
Advanced
dsivovdsivov

clean-code-practices

Enforce KISS, DRY, and YAGNI standards during software development tasks.

Community
Intermediate
yun520-1yun520-1
38

code-analyzer

Analyze codebases for architectural patterns, code quality, and DDD elements.

Community
Advanced