chad-tools

(chad-tools) Request a new feature

(chad-tools) Audit all marketplace plugins for accuracy

(chad-tools) Rebase conflict-blocked PRs, fix conflicts, review, push, verify CI

(chad-tools) Batch merge PRs with cascade rebase

(chad-tools) Multi-agent code review — local diff or PR

(chad-tools) Strip AI code slop from branch diff

(chad-tools) Mark worktree done for cleanup

(chad-tools) Update Rails review agents from upstream compound-engineering

(chad-tools) Plugin help

(chad-tools) Rewrite prose to remove AI writing patterns

(chad-tools) Report a bug

(chad-tools) Pick next issue and launch worktree

(chad-tools) Prep GitHub issues for autonomous AI execution

(chad-tools) Fix PR review findings, push, resolve threads, verify CI

Reviews code for efficiency issues — unnecessary work, missed concurrency, hot-path bloat, memory leaks, and overly broad operations. Runs when the diff contains non-trivial logic in any language.

Reviews code for duplication and missed reuse opportunities. Searches the codebase for existing utilities that could replace newly written code. Runs when non-trivial new functions or logic are added.

General-purpose code reviewer. Always runs on every PR review. Checks security, correctness, architecture, and style.

Reviews code comments and docstrings for accuracy and maintainability. Runs when the diff adds or modifies comments or documentation.

Preps a single GitHub issue for autonomous AI execution. Posts a structured execution plan as a comment with goal, success criteria, steps, context, and constraints.

Catches platform lock-in patterns that make future cross-platform support expensive. Runs when the diff contains Rust, Swift, C, or systems-level code. Flags one-way gates for Windows, iOS, and Android portability.

Reviews test files for coverage gaps, correctness issues, and flaky patterns. Runs when test files are in the diff.

Opinionated Rails convention reviewer. Runs when the diff contains Ruby/Rails files. Checks for Rails Way violations, unnecessary abstractions, and JS-world patterns creeping into Rails code.

Reviews database migrations and data model code for safety. Runs when the diff contains db/migrate/ files or ActiveRecord model changes.

Watches for architectural decisions that make future layered extraction painful. Runs when the diff contains Ruby/Rails files. Flags one-way gates and quantifies the cost of reversing them later.

Rails performance reviewer. Runs when the diff contains Ruby/Rails files. Checks for N+1 queries, missing indexes, unbounded queries, and memory-heavy patterns.

Rails security auditor. Runs when the diff contains Ruby/Rails files. Checks for auth/authz issues, mass assignment, CSRF, SQL injection, and secrets exposure.

Detects unrelated schema.rb changes by cross-referencing against included migrations. Runs when the diff contains db/schema.rb or db/migrate/ files.

Finds silent failures, swallowed errors, and misleading error handling. Runs when the diff contains try/catch/except/rescue/error patterns.

Reviews type, interface, struct, class, and enum definitions for design issues. Runs when the diff adds or modifies type definitions.

Create a new Claude Code skill from a repeated pattern or workflow. Use when you notice a recurring task that should be codified, or when the user says "make this a skill" or "save this pattern".

Generate a standalone utility script (bash, python, or JS/TS). Use when asked to write a quick script for a one-off task. Saves to a sensible location and makes it executable.

Add branch protection hooks to the current repo. Blocks pushes to main/master and force pushes via Claude Code. Use when setting up a production repo or when the user says "protect this repo" or "add branch guardrails".

Reply to GitHub PR review comments explaining how each was addressed, then resolve the conversations. Use when the user says "address review feedback", "resolve conversations", "reply to review comments", or after pushing fixes for PR review findings.

Resume work on a feature branch. Checks rebase status, shows recent commits, and orients to current state. Use when starting or resuming work on any non-default branch, or when the user says things like "where was I", "pick up where I left off", "continue working on this branch".

1 hook across 1 event