code-review

Enforce klabis code-review standards across backend and frontend pull requests.

2|2|Updated Sep 20, 2023
One-click install
npx skills add https://github.com/zabiny/klabis --skill code-review-zabiny
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/zabiny/klabis/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/zabiny/klabis --skill code-review-zabiny

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, repeatable code-review process for the klabis project, ensuring adherence to project best practices, testing standards, and the removal of dead or unused code to improve maintainability.

Core Features & Use Cases

  • Code review areas: enforce project best practices, identify architectural concerns, and ensure consistency across backend and frontend changes.
  • Testing & coverage: evaluate test presence and quality, review tests for new features and changes, and flag unnecessary or missing tests.
  • Refactoring discipline: identify dead or unused code and encourage simplification via KISS.
  • API & frontend criteria: ensure HAL responses include necessary links; frontend resources avoid exposing sensitive data and follow safe data-fetch patterns.
  • Use Case: during a PR review, automatically guide the reviewer through a checklist aligned with klabis standards.

Quick Start

Run a review pass on the incoming PR using the defined checklist to validate against klabis coding standards.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I enforce code review standards for a pull request?

Code review standards are enforced by running a structured checklist pass against the incoming PR to validate best practices, test coverage, and dead-code removal. This provides reliable, repeatable validation to maintain code quality and consistency across backend and frontend changes.

What is the best way to identify dead code during a PR review?

The best way to identify dead code during a PR review is to apply refactoring discipline checks based on KISS principles. This process flags unused code and encourages simplification, directly improving the overall maintainability of the software engineering project.

How do I check test coverage and quality for new frontend features?

Test coverage and quality for new frontend features are checked by evaluating test presence and flagging missing or unnecessary tests. The review ensures frontend resources avoid exposing sensitive data and follow safe data-fetch patterns while validating HAL responses include necessary links.

Does this code review process work for both backend and frontend changes?

Yes, the code review process works for both backend and frontend changes. It scopes the review to enforce project best practices, architectural consistency, and specific API criteria like HAL responses across the entire pull request.

When should I use a checklist-based code review instead of manual inspection?

A checklist-based code review should be used when you need repeatable validation of project best practices and refactoring standards. Manual inspection often misses dead-code removal and test coverage gaps, whereas a structured checklist ensures reliable quality assurance for every PR.