libsync-validation-and-qa

Validate libsync code quality and tests against pre-push and CI requirements.

4|Updated Aug 15, 2025
One-click install
npx skills add https://github.com/arthursoares/libsync --skill libsync-validation-and-qa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: libsync-validation-and-qa
Source: https://github.com/arthursoares/libsync/tree/main/.claude/skills/libsync-validation-and-qa
Command: npx skills add https://github.com/arthursoares/libsync --skill libsync-validation-and-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a comprehensive checklist for validating code quality, testing, and QA processes in the libsync repository before merging changes.

Core Features & Use Cases

  • Test Inventory: Details all available backend and frontend tests, along with their scope and execution methods.
  • Pre-Push Checklist: Lists the necessary steps and commands to run before pushing code to ensure compliance with CI standards.
  • Ruff Lint Trap: Explains the discrepancy between local and CI linter results and provides guidelines for handling linter issues.
  • Frontend Check Traps: Highlights potential issues with local vs. CI builds and provides solutions for frontend checks.
  • CI vs. Local Delta Summary: Compares the checks and behaviors between local development and CI environments.
  • Evidence Standards: Defines the acceptance criteria for changes based on testing and proof of functionality.
  • Acceptance Thresholds and Pytest Behavior: Describes the success criteria for downloads and the configuration of pytest.

Quick Start

Run the pre-push checklist to ensure code quality and test suite integrity before merging your changes into the libsync repository.

Frequently Asked Questions about libsync-validation-and-qa

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

FAQPage Schema
How do I ensure code quality and test suite integrity before merging changes?

Validate code quality before merging by running a pre-push checklist that enforces code linting standards, assesses backend and frontend test coverage, and ensures adherence to CI requirements.

What is included in the pre-push checklist for CI integration?

A pre-push checklist for CI integration includes running specific commands to verify backend and frontend tests, enforce code linting, and meet acceptance thresholds before pushing code.

Why does Ruff linting show different results locally versus CI?

Ruff linting discrepancies between local and CI environments arise from configuration differences. The Skill identifies this trap and provides guidelines for resolving linter issues to align local and CI results.

How do I handle frontend check traps during local development?

Handle frontend check traps by identifying discrepancies between local and CI builds. The Skill highlights these potential issues and provides solutions to align frontend checks across environments.

What are the acceptance thresholds and pytest behaviors for validating code?

Acceptance thresholds for validating code define success criteria for downloads and pytest configuration. The Skill describes these thresholds to ensure test suite integrity before merging.