libragent-quality

Validate TypeScript/React and Rust/Tauri code with linting, formatting, type checks, and builds.

8|3|Updated Jul 14, 2025
One-click install
npx skills add https://github.com/fritzprix/libr-agent --skill libragent-quality
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: libragent-quality
Source: https://github.com/fritzprix/libr-agent/tree/main/.github/skills/libragent-quality
Command: npx skills add https://github.com/fritzprix/libr-agent --skill libragent-quality

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

LibrAgent code quality validation ensures frontend and backend code adheres to project standards, preventing regressions and maintaining consistency across the TypeScript/React frontend and Rust/Tauri backend.

Core Features & Use Cases

  • End-to-end validation: Linting, formatting checks, type checking, build verification, and dead code detection for both frontend and backend.
  • Refactor safety: Enforces standard conventions during code changes to minimize introducing issues.
  • Use Case: Before merging a PR, run the full validation to guarantee high-quality, production-ready code.

Quick Start

Use the refactor:validate pipeline to run all checks on the LibrAgent repository. pnpm refactor:validate pnpm lint pnpm format:check pnpm build pnpm dead-code pnpm test:run

Backend checks

pnpm rust:fmt:check pnpm rust:clippy pnpm rust:check pnpm rust:check:all pnpm rust:test pnpm rust:validate

Frequently Asked Questions about libragent-quality

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

FAQPage Schema
How do I run end-to-end code quality validation for a TypeScript and Rust project?

End-to-end code quality validation is executed via the refactor:validate pipeline, orchestrating ESLint, Prettier, Vitest, Rustfmt, Clippy, and cargo checks to enforce frontend and backend standards before merging changes.

What does comprehensive frontend and backend linting include for a Tauri application?

Comprehensive linting for a Tauri application includes TypeScript and React checks using ESLint and Prettier, alongside Rust backend validation using Rustfmt and Clippy to ensure formatting and code quality standards.

Can I use this validation pipeline to ensure refactor safety before a pull request?

Yes, you can use this validation pipeline to ensure refactor safety by running type checking, build verification, and dead code detection to minimize regressions and maintain consistency before integrating code changes.

What is the best way to automate continuous quality gates for TypeScript and Rust?

The best way to automate continuous quality gates is running the refactor:validate script, which sequentially executes linting, formatting checks, builds, and tests across both the TypeScript and Rust tech stacks.

Why does my code quality validation fail when formatting checks pass but the build breaks?

Code quality validation fails because the pipeline enforces multiple layers independently; passing Prettier formatting checks does not prevent build failures if TypeScript type checking or Rust cargo check detects compilation errors.