code-review

Audit C# and Vue.js codebases for architecture, standards, and test gaps.

Updated Jan 31, 2026
One-click install
npx skills add https://github.com/Kibbey/fyli --skill code-review-kibbey
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/Kibbey/fyli/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/Kibbey/fyli --skill code-review-kibbey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineering teams enforce quality and consistency by guiding comprehensive reviews that identify defects, subpar architecture, and deviations from agreed standards.

Core Features & Use Cases

  • Automated architectural and style checks across backend (C#) and frontend (Vue.js) codebases.
  • Comprehensive governance: ensures DI usage, DTO definitions, test coverage alignment, and documentation compliance.
  • Use Case: Before merging PRs, run a code review that highlights architectural risks, potential bugs, and style violations.

Quick Start

Activate the skill to initiate a code review on your repository and request a structured report on architecture, quality, and test readiness.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I check C# architecture constraints and coding standards before merging a PR?

You can check C# architecture constraints by running an automated code review that audits dependency injection usage, DTO definitions, and 3-tier compliance. The review produces a structured report highlighting architectural risks, style violations, and test coverage gaps before PR integration.

What is the best way to enforce code quality and consistency across frontend and backend codebases?

The best way to enforce code quality is to apply automated architectural and style checks across Vue.js and C# codebases. This governance process catches deviations from agreed standards, identifies subpar architecture, and ensures test readiness during maintenance tasks.

Can I use automated code review to detect architectural risks and missing documentation?

Yes, automated code review can detect architectural risks and missing documentation by auditing codebases for best practices. It evaluates test coverage alignment, coding standards compliance, and structural constraints, delivering actionable recommendations in a structured report format.

Does this code review approach work for both Vue.js frontend and C# backend projects?

Yes, this code review approach works for both Vue.js frontend and C# backend projects by applying unified governance rules. It enforces architecture constraints, dependency injection patterns, and documentation compliance across both environments during reviews and maintenance.

How do I audit test coverage and style violations during codebase maintenance?

You can audit test coverage and style violations by initiating a comprehensive code review that analyzes your repository. The review evaluates test readiness, checks coding standards, and identifies style deviations, outputting a structured report with actionable maintenance recommendations.

What limitations should I consider when running automated architectural checks on my codebase?

When running automated architectural checks, consider that the review focuses on predefined constraints like 3-tier architecture, DI usage, and DTO definitions. It generates a structured report of actionable recommendations, but does not automatically refactor code or execute fixes.