tough-review

Name: tough-review
Availability: InStock
Author: Will

Review current branch code changes against the base with round tracking.

Updated Mar 18, 2026

Search Tags:#git #documentation #quality-assurance #code-review #pull-request #pr-summary #comment-tracking

Ready to run

npx skills add https://github.com/willnordnet/dotfiles --skill tough-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tough-review
Source: https://github.com/willnordnet/dotfiles/tree/main/claude/skills/tough-review
Command: npx skills add https://github.com/willnordnet/dotfiles --skill tough-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ruthless code review accelerates and systematizes the feedback loop for code changes by comparing the current branch against the base, surfacing issues, and tracking comment status across rounds to ensure fixes are verified.

Core Features & Use Cases

Phase-driven review: Phase 1 analyzes diffs, commits, and changed files for issues.
PR round tracking: Maintains a cumulative PR summary and tracks open vs. fixed comments across rounds.
Verification of fixes: Checks whether issues tied to comments are addressed in subsequent commits.
Use Case: A maintainer uses this skill on a feature branch to ensure every change is reviewed, discussed, and validated before merge.

Quick Start

Run the tough-review command on your repository to begin the current-branch review and PR summary workflow.

Frequently Asked Questions about tough-review

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

FAQPage Schema

How do I track code review comments across multiple pull request rounds?▼

Tracking code review comments across multiple pull request rounds involves maintaining a cumulative PR summary that logs open versus fixed comments, ensuring issues raised in previous rounds are verified against subsequent commits before merging.

What is the best way to automate rigorous code review on a feature branch?▼

Automating rigorous code review on a feature branch requires a tool that compares the current branch against the base, analyzes file diffs and commits to surface issues, and enforces deterministic task execution to guarantee quality before merge.

How does a phase-driven code review workflow identify issues in a pull request?▼

Phase-driven code review identifies pull request issues by analyzing branch diffs, commit history, and changed files during its initial phase, then tracking the status of those issues across subsequent review rounds until verified.

Does this automated review process work with any Git workflow?▼

This automated review process is applicable to any Git workflow where rigorous, round-by-round pull request analysis is required, including tracking review comments, round status, and code fixes.

How do I verify if code review issues are actually fixed in later commits?▼

To verify if code review issues are fixed in later commits, you need a comment tracking system that checks subsequent commits on the branch to see if the changes address the specific issues tied to each open review comment.