prepare-for-review

Scan modified files for dead code and verify Definition of Done.

1|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/gjalla/gjalla-plugin --skill prepare-for-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prepare-for-review
Source: https://github.com/gjalla/gjalla-plugin/tree/main/claude/skills/prepare-for-review
Command: npx skills add https://github.com/gjalla/gjalla-plugin --skill prepare-for-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers often finish a feature without ensuring that all dead code is removed and that the work meets the team's Definition of Done, leading to noisy codebases and delayed reviews.

Core Features & Use Cases

  • Dead Code Sweep: Scans changed files for unused functions, imports, commented‑out blocks, TODOs, empty catch blocks, and unreachable code, reporting and optionally removing clear‑cut issues.
  • Definition of Done Audit: Locates the project's DoD document or applies a sensible default, checks each criterion, and produces a pass/fail checklist with an attestation.
  • Readiness Verdict: Summarizes blockers, passes, and dead‑code removals, and indicates whether the change is ready for review.

Quick Start

Ask the assistant to run the prepare‑for‑review skill on your current branch to clean up dead code and verify readiness for a pull‑request review.

Frequently Asked Questions about prepare-for-review

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

FAQPage Schema
How do I clean up dead code before a pull request review?

To clean up dead code before a pull request review, scan modified files on your feature branch for unused functions, imports, TODOs, empty catch blocks, and unreachable code, then report and remove those issues to verify review readiness.

What is a Definition of Done audit for feature branches?

A Definition of Done audit for feature branches locates your project's DoD document or applies a sensible default, checks each criterion against your code changes, and produces a pass or fail checklist with a readiness attestation.

How do I verify code readiness and compliance with architecture rules before review?

Verify code readiness and compliance with architecture rules before review by scanning changed files in your pull request against project rules, summarizing blockers, dead-code removals, and passes to indicate if the change is ready.

Can I scan a git diff for unused functions and commented-out blocks?

Yes, you can scan a git diff for unused functions and commented-out blocks by applying a pre-review cleanup to code changes on your branch, which identifies and optionally removes clear-cut dead code issues.

What is the best way to automate a pre-review code cleanup for a feature branch?

The best way to automate a pre-review code cleanup for a feature branch is to run a skill that sweeps modified files for dead code, audits the Definition of Done, and outputs a readiness verdict summarizing blockers and passes.