clavix-verify

Audit code implementations against PRDs and task specifications with structured review comments.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/g5becks/oxlint-plugins --skill clavix-verify-g5becks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clavix-verify
Source: https://github.com/g5becks/oxlint-plugins/tree/main/.skills/clavix-verify
Command: npx skills add https://github.com/g5becks/oxlint-plugins --skill clavix-verify-g5becks

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that implemented code strictly adheres to the defined product requirements (PRD) and the architectural plan, preventing technical debt and ensuring feature completeness.

Core Features & Use Cases

  • Spec-Driven Audit: Compares code against full-prd.md and tasks.md.
  • Gap Analysis: Identifies discrepancies in Plan vs Code, PRD vs Code, and Code vs Standards.
  • Structured Reporting: Generates detailed review comments with severity levels.
  • Enforces Fix Loop: Mandates fixing identified issues and re-verification before proceeding.
  • Use Case: After a developer implements a new feature, this Skill acts as a quality gate, performing a thorough technical audit to catch any deviations from the requirements or plan before code merge.

Quick Start

Use clavix-verify to audit the implementation of the user authentication module against the project's PRD and tasks.

Frequently Asked Questions about clavix-verify

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

FAQPage Schema
How do I verify code against a PRD and task specifications?

To verify code against a PRD, perform a spec-driven technical audit analyzing source code for adherence to architectural plans and business logic, generating structured review comments to enforce a mandatory fix-and-re-verify loop.

What is spec-driven code verification and how does it work?

Spec-driven code verification is a technical audit process that compares source code against product requirement documents and tasks to identify discrepancies in plan versus code, generating structured review comments with severity levels to ensure feature completeness.

How do I perform a gap analysis between my implementation plan and source code?

Perform a gap analysis by auditing the code implementation against your tasks and PRD files to identify discrepancies in plan versus code, PRD versus code, and code versus quality standards, outputting detailed review comments with severity levels.

Do I need specific files to run a compliance audit on my code?

Yes, running a compliance audit requires access to tasks.md and full-prd.md files to provide architectural and business context, alongside the source code files that need to be inspected for adherence to the defined plan.

How do I enforce a fix-and-re-verify loop during code review?

You can enforce a fix-and-re-verify loop by mandating that all identified issues from the structured review comments are resolved before proceeding, acting as a quality gate to prevent technical debt prior to code merge.

What is the best way to audit code for adherence to architectural plans?

The best way to audit code for architectural adherence is to perform a technical audit comparing the implementation against product requirements and task specifications, generating structured reports with severity levels to catch deviations before merging.