skills.rest
sssemil
sssemilCOMMUNITY
Explore all skills by this author →
GitHub

brutal-review

Identify and critique the latest code change in jj or git repositories.

2|Updated Feb 9, 2026
Search Tags:#git#quality#static-analysis#code-review#jj#pull-request#brutal-review
One-click install
npx skills add https://github.com/sssemil/SKILLS --skill brutal-review-sssemil
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brutal-review
Source: https://github.com/sssemil/SKILLS/tree/main/brutal-review
Command: npx skills add https://github.com/sssemil/SKILLS --skill brutal-review-sssemil

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill performs a ruthless, multi-perspective code review of the most recent change (jj @- or git HEAD), identifying flaws, risks, and improvement opportunities.

Core Features & Use Cases

  • Multi-perspective analysis: Core logic, reliability, maintainability, and security considerations for code changes.
  • Thorough findings: Generates actionable, evidence-based feedback with file/line references and concrete fixes.
  • Pre-merge readiness: Useful for pull requests, code audits, and post-commit reviews.

Quick Start

Initiate a brutal, multi-perspective review of the latest change and report actionable findings.

Frequently Asked Questions about brutal-review

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

FAQPage Schema
How do I perform a multi-perspective code review on my latest git commit?▼

A multi-perspective code review analyzes the latest git HEAD or jj @- change for core logic, reliability, and maintainability flaws. It generates evidence-based feedback with file references and concrete fixes for pre-merge readiness.

What is a brutal code review and how does it identify risks in a pull request?▼

A brutal code review ruthlessly critiques recent code changes to identify flaws and improvement opportunities. It assesses core logic, reliability, maintainability, and security, delivering findings with impact scores and actionable fixes.

Can I use static analysis to review code changes in repositories using jj?▼

Yes, you can review code changes in repositories using jj by analyzing the @- change. The review evaluates maintainability and reliability, providing actionable, evidence-based feedback with file and line references.

What's the best way to audit code quality before merging a pull request?▼

The best way to audit code quality before merging is a ruthless, multi-perspective review of the latest change. It evaluates security and reliability, generating findings with concrete fixes and impact scores for post-commit analysis.

Does multi-perspective code review work for post-commit analysis in git?▼

Yes, multi-perspective code review works for post-commit analysis in git by evaluating the HEAD change. It identifies maintainability risks and security considerations, delivering evidence-based feedback with file references.

Related Skills

Explore More Software Engineering Skills→
karithamkaritham
2

vcs

Automate version control workflows using JJ commands for history, diffs, and commits.

Community
Intermediate
Negentropy-LabyNegentropy-Laby
3

skill-improve

Identify skill gaps and apply test-fix-retest loops with keep or revert decisions.

Official
Advanced
samChang72samChang72
1

code-review

Automates code reviews to detect bugs, style violations, and performance issues in submissions via static analysis tools.

Community
Intermediate
mahg-esmahg-es
3

cicd-quality

Design and enforce CI/CD quality gates for code, tests, security, build, E2E, and performance.

Official
Advanced