grill-me

Review code changes for risks and suggest improvements before merging.

2|1|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/bongrealty/skillcraft --skill grill-me
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/bongrealty/skillcraft/tree/main/grill-me
Command: npx skills add https://github.com/bongrealty/skillcraft --skill grill-me

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill acts as an AI-powered code reviewer, rigorously questioning your changes before you submit a Pull Request, ensuring higher code quality and catching potential issues early.

Core Features & Use Cases

  • Adversarial Code Review: Asks challenging questions about edge cases, security, performance, and maintainability.
  • Elegant Rewrites: Can scrap existing code and reimplement based on a deeper understanding of the problem.
  • Spec-Driven Development: Helps define clear requirements and acceptance criteria before implementation begins.
  • Use Case: Before merging a critical feature, use this Skill to ensure your code is production-ready by having it subjected to a thorough, critical review.

Quick Start

Initiate an adversarial code review by asking Claude to grill you on your current changes.

Frequently Asked Questions about grill-me

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

FAQPage Schema
How do I run an adversarial code review before submitting a pull request?

Adversarial code review is performed by analyzing your git diff and asking targeted questions about edge cases, security, and error handling to ensure your code is production-ready before integration.

Can I use spec-driven development to define acceptance criteria before implementation?

Spec-driven development helps define clear requirements and acceptance criteria before implementation begins, ensuring the resulting code rewrites and refactoring meet the expected quality and security standards.

Does automated code review work for catching security vulnerabilities and performance issues?

Automated code review focuses on identifying security vulnerabilities, performance issues, and missing error handling by rigorously questioning your changes and analyzing diffs within your git repository context.

What is the best way to catch edge cases and missing error handling during development workflow?

Catching edge cases and missing error handling is best achieved through adversarial questioning that challenges your code changes, supporting rewrites and refactoring to improve overall code quality.

Can I scrap existing code and reimplement it based on a deeper problem understanding?

You can scrap existing code and trigger elegant rewrites that reimplement the solution based on a deeper understanding of the problem, ensuring robust logic before merging critical features.

Do I need a git repository to perform diff analysis for code refactoring?

A git repository context is required because the review operates by utilizing diff analysis to track your current changes and question you on them before user-approved code integration.