code-reviewer

Review Next.js and FastAPI code against specifications and BFF architecture standards.

Updated Nov 27, 2025
One-click install
npx skills add https://github.com/wtsi-hgi/llm-knowledge-base --skill code-reviewer-wtsi-hgi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/wtsi-hgi/llm-knowledge-base/tree/main/.github/skills/code-reviewer
Command: npx skills add https://github.com/wtsi-hgi/llm-knowledge-base --skill code-reviewer-wtsi-hgi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the rigorous process of reviewing code implementations to ensure they meet project specifications, architectural guidelines, and quality standards, preventing regressions and maintaining codebase integrity.

Core Features & Use Cases

  • Specification Verification: Checks if implemented code aligns with acceptance tests and design documents.
  • Architecture & Quality Audits: Enforces adherence to the project's Best-Fit Framework (BFF) pattern, contract integrity, and coding standards.
  • Test Coverage Validation: Confirms that all specified acceptance tests have corresponding, functional unit tests.
  • Use Case: Before merging a new feature, use this Skill to perform a comprehensive code review, verifying that all backend and frontend tests pass, the BFF pattern is respected, and contracts are correctly implemented.

Quick Start

Use the code-reviewer skill to verify the implementation of the new user authentication feature against its specification.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
How do I automate code review for a Next.js and FastAPI project?

Automate code review for a Next.js and FastAPI project by validating test coverage, enforcing BFF pattern adherence, and checking contract integrity against defined specifications. This ensures codebase quality and prevents regressions before merging new features.

What is the BFF pattern and how does code review enforce it?

The BFF (Best-Fit Framework) pattern structures backend-frontend interactions, and code review enforces it by auditing architectural adherence and verifying contract integrity. This ensures implemented code aligns with design documents and project guidelines.

How do I validate test coverage and acceptance tests before merging a feature?

Validate test coverage before merging by checking if implemented code aligns with acceptance tests and design documents. The review process confirms that all specified acceptance tests have corresponding, functional unit tests to prevent regressions.

Does automated code review check contract integrity between frontend and backend?

Automated code review does check contract integrity between frontend and backend by auditing architectural adherence to the BFF pattern. It validates that implementations respect defined contracts and coding standards to maintain integration stability.

What are the limitations of automated specification verification for code implementations?

Limitations of automated specification verification include relying heavily on referencing conventions and agent-conduct skills for detailed guidelines. It cannot replace manual review entirely, requiring defined specifications and design documents to function correctly.