qa-library-validation

Validates third-party library API usage in code against Context7 documentation.

3|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/gabrielnsmnto/kord-aios --skill qa-library-validation-gabrielnsmnto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-library-validation
Source: https://github.com/gabrielnsmnto/kord-aios/tree/main/src/features/builtin-skills/kord-aios/qa/qa-library-validation
Command: npx skills add https://github.com/gabrielnsmnto/kord-aios --skill qa-library-validation-gabrielnsmnto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes often use third-party libraries with incorrect signatures, deprecated methods, or version-incompatible APIs that slip past review. This Skill automatically validates every imported library in modified files against official Context7 documentation, catching API misuse before it reaches production. ## Core Features & Use Cases - Import Extraction and Resolution: Parses JavaScript, TypeScript, and Python imports from modified files, then resolves each library to its Context7 documentation ID. - API Usage Validation: Checks function signatures, parameter types, return values, and deprecated methods against official docs, flagging issues with severity levels from CRITICAL to MINOR. - Structured QA Reports: Generates a JSON validation report saved to the story's QA folder, integrating directly into the review-build pipeline as Phase 6.0. - Use Case: During a story review, run validation on changed files to discover that useQuery({ cacheTime: 5000 }) uses a deprecated option and should be migrated to gcTime, with a suggested fix and docs link included. ## Quick Start Ask the QA agent to validate the libraries used in story 6.3 by running validate-libraries with the story ID.

Frequently Asked Questions about qa-library-validation

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

FAQPage Schema
How do I validate library API usage in a code review?▼

Run the validate-libraries command with a story ID to extract imports from modified files, resolve each library via Context7, and check API usage against official documentation. Issues are reported with severity levels and suggested fixes.

How to detect deprecated API methods in JavaScript dependencies?▼

The validation workflow queries Context7 documentation for each imported library and flags deprecated APIs, distinguishing between methods removed in the next major version (CRITICAL) and those still functional (MAJOR), with migration suggestions included.

Does library validation support Python imports?▼

Yes, the import extraction phase includes regex patterns for Python import and from-import statements alongside JavaScript and TypeScript patterns. Relative imports and standard library modules are filtered out unless explicitly included.

What happens when a library is not found in Context7?▼

Unresolvable libraries are logged as unvalidated and the process continues without blocking, following a continue-on-error strategy. These libraries are listed in the report's unresolved section for manual review.

Can library validation run in CI/CD pipelines?▼

Yes, YOLO mode provides autonomous validation with logging and minimal interaction, suited for CI/CD integration. Interactive mode with decision checkpoints is the default, and a pre-flight planning mode handles large PRs with many dependencies.