quality-assurance

Automate build, deployment, and code review checks for the Clarin CRM.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/ricardoalejandro/clarin --skill quality-assurance-ricardoalejandro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: quality-assurance
Source: https://github.com/ricardoalejandro/clarin/tree/main/.github/skills/quality-assurance
Command: npx skills add https://github.com/ricardoalejandro/clarin --skill quality-assurance-ricardoalejandro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that all code changes meet rigorous quality, self-testing, and verification standards, acting as a final gatekeeper before user presentation.

Core Features & Use Cases

  • Automated Build & Deployment: Compiles and deploys code changes using Docker.
  • Runtime Error Verification: Checks logs for any runtime errors post-deployment.
  • Code Review Checklist: Enforces strict coding standards and best practices.
  • Use Case: Before merging any new feature, this Skill automatically builds the backend and frontend, deploys them, checks logs for errors, and verifies against a comprehensive code review checklist, ensuring a high-quality release.

Quick Start

Run the quality assurance skill to build, deploy, and verify the latest code changes.

Frequently Asked Questions about quality-assurance

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

FAQPage Schema
How do I automate code review and deployment verification for my CRM project?▼

Automate code review and deployment verification by compiling backend and frontend changes, deploying via Docker, and checking logs for runtime errors to enforce code integrity before release.

What does a senior engineer's code review checklist verify during a build?▼

A senior engineer's code review checklist verifies build success, clean logs, error handling, parameterized SQL queries, correct TypeScript types, UI palette adherence, minimal code changes, and proper WebSocket broadcasts.

How do I check for runtime errors after deploying code changes with Docker?▼

Check for runtime errors after deploying code changes with Docker by reviewing the deployment logs for errors, ensuring the compilation and validation processes complete successfully without failures.

Can I enforce strict TypeScript types and parameterized SQL queries as a deployment gate?▼

Yes, you can enforce strict TypeScript types and parameterized SQL queries as a deployment gate by applying an automated verification checklist that blocks code changes failing these quality standards.

Does the quality assurance process work without additional dependencies?▼

Yes, the quality assurance process works without additional dependencies, using internal scripts and references to build, deploy, and validate code changes autonomously.

Why should I use automated verification before merging new features?▼

Use automated verification before merging new features to act as a final gatekeeper, ensuring code changes meet rigorous self-testing standards and preventing runtime errors from reaching users.