build-review

Run build and test pipelines and fix detected failures in monorepos.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/xkazm04/personas --skill build-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-review
Source: https://github.com/xkazm04/personas/tree/main/.claude/skills/build-review
Command: npx skills add https://github.com/xkazm04/personas --skill build-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates a local pre-merge build review by running the full build and test pipeline, surfacing lint, type, test, and clippy failures, and guiding fixes so developers can validate a working codebase before committing.

Core Features & Use Cases

  • End-to-end pipeline execution: Execute frontend linting, TypeScript typechecks, unit tests, and Rust cargo tests and clippy in sequence to produce a consolidated report.
  • Error analysis and targeted fixes: Parse errors with file and line context, read source files for context, and apply corrective edits for lint, type, or test failures.
  • Iterative verification: Re-run the pipeline after fixes until all actionable, local issues are resolved; useful for pre-merge validation and local CI debugging.

Quick Start

Run the repository's build-review script, inspect build-review-report.txt, fix the reported issues in source files, and re-run the script until local checks pass.

Frequently Asked Questions about build-review

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

FAQPage Schema
How do I run a full build pipeline for a Tauri app with React and Rust?

To run a full build pipeline for a Tauri app, you execute the repository's build-review script to sequence frontend linting, TypeScript typechecks, unit tests, Rust cargo tests, and clippy, producing a consolidated report of any failures.

How do I fix lint and clippy errors automatically before committing?

To fix lint and clippy errors before committing, you parse the generated build-review report for file and line context, read the source files, apply corrective edits to the codebase, and re-run the checks until all local issues are resolved.

What is a local pre-merge build review for a monorepo?

A local pre-merge build review for a monorepo is the process of running all linting, type-checking, and testing pipelines sequentially to surface and fix failures, ensuring developers validate a working codebase before committing.

Can I use this build validation process for a local monorepo combining TypeScript and Rust?

Yes, this build validation process is specifically designed for local monorepos combining a React/TypeScript frontend and a Rust Tauri backend, applying linting, type-checking, unit tests, clippy, and cargo tests during developer validation.

Why does my iterative build verification keep failing after source edits?

Iterative build verification keeps failing if the applied source edits do not fully resolve the actionable issues parsed from the report, requiring you to read the updated build-review-report.txt and modify source files again until checks pass.

Does build-review require shell access to execute tests and modify code?

Yes, build-review requires shell access to execute the repository's build-review script, read the generated report files, modify source files to apply corrective fixes, and re-run the pipeline checks until resolved.