More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Code Review Bottleneck Fix

    1

    Measure where reviews actually wait, then fix the queue, the size, or the ownership causing it.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Code Review Bottleneck Fix

    Code Review Bottleneck Fix

    Example session with this skill installed

    Apply the skill to a small test input and produce its core output. The script reads only a CSV export with the columns named in the skill; it does not connect to a review tool or measure review quality.

    • Read your context and instructions
    • Compiled the code review bottleneck

    A six-person team had a median pull request wait of 4.2 days and assumed reviewers were slow. Stage splits showed 3.1 days waiting for first review and only 0.6 days in discussion, so discussion was not the problem. Load data showed two senior engineers held 68 percent of open reviews, and the ten longest waits were all waiting on one of them during a holiday week. The fix was ownership: a rotating sweep owner, a second reviewer on every change, and a 48-hour maximum unreviewed age for routine changes. Two weeks later median first-review wait was 0.9 days, and post-merge defects did not rise. The team had not needed faster reviewers; it had needed the queue to stop depending on two people.

    Script demo (verified): running python3 scripts/review_bottleneck.py on a 3-row test file printed median first-review 3.0 days, reviewer load Sam 2 and Jo 1, and top-two share 100.0 percent.

    This is a worked example produced by applying the skill, not a claim about a live customer outcome.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    A diagnostic and repair workflow for slow code review: measure wait time by stage, find whether the bottleneck is queue, change size, reviewer load, or unclear ownership, and fix that cause instead of exhorting people to review faster. The skill provides a step-by-step protocol with decision points, a decision table, a fill-in template, a checklist, and a scoring rubric, plus a runnable script (review_bottleneck.py) that reads a pull request csv and reports median wait by stage and reviewer load concentration. It focuses on finding the bottleneck first and fixing in an order backed by evidence, rather than applying generic advice.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Code Quality & Review.

    It measures process, not review quality; a fast review can still be shallow. It needs timestamps from the review tool to work well.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 23 days ago

    Permissions

    Terminal / Shell
    Listed23 days ago
    Updated21 days ago

    What's inside

    Frequently Asked Questions

    No. It organises evidence and decisions so judgement is applied to the right question, with a record of why.

    Longer than a generic checklist, because measurement comes first. Later uses are faster once templates and scripts are in place.

    Yes, by narrowing scope explicitly and recording what was skipped. The quality gate still applies to the narrowed work.

    New in Code Quality & Review