rework-rate

Calculate PR rework rate, review cycles, rejection rate, and rework time.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/Leep-GH/Lee-s-squad --skill rework-rate-leep-gh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rework-rate
Source: https://github.com/Leep-GH/Lee-s-squad/tree/main/templates/skills/rework-rate
Command: npx skills add https://github.com/Leep-GH/Lee-s-squad --skill rework-rate-leep-gh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rework rate tracks how often changes are revised after initial review, enabling teams to diagnose review bottlenecks and improve PR quality.

Core Features & Use Cases

  • Calculate rework rate from PR data across merged PRs to surface review inefficiencies.
  • Provide sub-metrics: Review Cycles, Rejection Rate, and Rework Time to guide coaching and process improvements.
  • Support dashboards and workflows for engineering health metrics and sprint planning.
  • Use Case: When a team wants to reduce cycle time and improve PR quality, analyze historical PRs to identify common revision patterns and target process changes.

Quick Start

Analyze the rework performance of your recent PRs to generate a coaching plan.

Frequently Asked Questions about rework-rate

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

FAQPage Schema
What is PR rework rate and how does it track code review inefficiencies?

Pull request rework rate measures how often code changes require revision after the initial code review. Tracking this metric helps teams identify review bottlenecks and diagnose inefficiencies in their engineering workflows.

How do I calculate rework rate from merged PRs to improve code quality?

You calculate PR rework rate by analyzing historical merged pull requests to count how many required post-review revisions. This Skill implements calculations for Review Cycles, Rejection Rate, and Rework Time to quantify rework and improve code quality.

Can I generate an engineering health dashboard tracking review cycles and rejection rate?

Yes, this Skill supports dashboards and workflows for engineering health metrics. It calculates Review Cycles, Rejection Rate, and Rework Time from PR data to provide structured outputs that track review efficiency across merged pull requests.

What metrics should I use to reduce PR cycle time and identify revision patterns?

To reduce PR cycle time, you should use Review Cycles, Rejection Rate, and Rework Time metrics. Analyzing these sub-metrics across historical PRs identifies common revision patterns and guides targeted coaching to improve pull request quality.

Does this tool work for sprint planning and engineering health tracking?

Yes, this Skill supports sprint planning and engineering health tracking workflows. By analyzing historical PR data to calculate rework metrics, it provides structured outputs and CLI prompts that guide coaching and process improvements for development teams.