skills.rest
YehudaFrankel
YehudaFrankelCOMMUNITY
Explore all skills by this author →
GitHub

code-review

Analyze source files for bugs, antipatterns, and quality issues.

16|3|Updated Mar 15, 2026
Search Tags:#quality#review#bugs#code#static-analysis#code-review#antipatterns
One-click install
npx skills add https://github.com/YehudaFrankel/clankbrain --skill code-review-yehudafrankel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/YehudaFrankel/clankbrain/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/YehudaFrankel/clankbrain --skill code-review-yehudafrankel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews are time-consuming and prone to missing issues. This Skill provides a structured, repeatable checklist to detect bugs, antipatterns, and quality gaps in a target file, improving consistency and code health.

Core Features & Use Cases

  • Structured findings: reports issues with File, Line, Issue, and Severity in a tabular format.
  • Broad coverage: checks backend APIs, frontend code, and general coding patterns for common pitfalls.
  • Use cases: suitable for pre-commit checks, PR reviews, and quality audits to guide fixes and improvements.

Quick Start

Describe the file you want reviewed and I will generate a structured report of issues and suggested fixes.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I spot bugs and antipatterns in a source file?▼

To spot bugs and antipatterns in a source file, you can use a code review tool that analyzes the file and generates a structured findings table with issues, line numbers, and severity levels.

Can I use static analysis for a pre-commit check on frontend and backend code?▼

Yes, static analysis can be used for pre-commit checks on both frontend and backend codebases, identifying common pitfalls and quality gaps before changes are committed.

What is the best way to generate a structured report for a PR review?▼

The best way to generate a structured report for a PR review is to analyze the target file, producing a table that lists the file, line, issue, and severity of each detected bug or antipattern.

Does this code review approach work for single-file audits or entire repositories?▼

This code review approach works specifically for single-file audits, analyzing individual source files rather than entire repositories, making it suitable for focused design audits.

How do I fix the quality issues found during a code review?▼

After a code review identifies quality issues, you can address them by prompting the tool to fix the detected issues immediately or flagging them for later resolution.

Related Skills

Explore More Software Engineering Skills→
thoreinsteinthoreinstein
5

data-model

Generate data-model documentation with ERDs, DTOs, and data-flow diagrams in Markdown.

Community
Advanced
InternLMInternLM
8.0k

resolve-review

Fetch GitHub PR review comments, apply fixes, run pre-commit linting, and stage changes.

Official
Intermediate
MomoDavilukeMomoDaviluke
2

coding-standards

Enforce universal coding conventions across frontend and backend codebases.

Community
Intermediate
danielctcdanielctc

repomix

Package entire repositories into AI-friendly single files in XML, Markdown, JSON, or Plain.

Community
Advanced