verify-adoption

Name: verify-adoption
Availability: InStock
Author: Foomakers

Validate code and configuration against project adoption files for specified scopes.

6|Updated Aug 3, 2025

Search Tags:#architecture #code review #security #compliance #standards #adoption

Ready to run

npx skills add https://github.com/foomakers/pair --skill verify-adoption

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verify-adoption
Source: https://github.com/foomakers/pair/tree/main/packages/knowledge-hub/dataset/.skills/capability/verify-adoption
Command: npx skills add https://github.com/foomakers/pair --skill verify-adoption

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automatically checks your code, configuration, or a Pull Request against your project's established adoption files, ensuring compliance with technical standards, architecture, security, and coding practices. It provides a clear report of conformity or non-conformity without attempting to fix issues itself.

Core Features & Use Cases

Compliance Auditing: Detects deviations from defined tech-stack, architecture, security, coding-standards, and infrastructure requirements.
Detection-Only: Reports findings without modifying code, empowering developers or reviewers to address issues.
Use Case: Before merging a Pull Request, run /verify-adoption with $scope=all to get a comprehensive report on whether the changes adhere to the project's established guidelines and architecture.

Quick Start

Run verify adoption for the entire project scope.

Frequently Asked Questions about verify-adoption

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

FAQPage Schema

How do I check if my code aligns with project architecture and security standards?▼

To check if code aligns with project standards, validate code and configuration against project adoption files. This detects non-conformities by scanning the codebase against defined architecture, security, and coding guidelines.

How do I verify a Pull Request against established tech-stack and infrastructure requirements?▼

To verify a Pull Request, scan the changes against your project's adoption documents for specified scopes like tech-stack and infrastructure. This compliance audit reports deviations without modifying the code.

What is the best way to audit codebase compliance without automatically modifying files?▼

The best way to audit codebase compliance without modifying files is to use a detection-only validation process. It scans configurations against adoption guidelines and reports findings per area, routing resolution to developers.

Can I scan my codebase for non-conformities across multiple scopes like coding-standards and infrastructure?▼

Yes, you can scan your codebase for non-conformities across multiple scopes. By specifying scopes like coding-standards and infrastructure, the validation process detects deviations and reports them per area for manual developer action.

Does code compliance validation fix non-conformities automatically or just report them?▼

Code compliance validation only reports non-conformities and does not fix issues automatically. It detects deviations from adoption documents and routes the resolution to appropriate skills or manual developer action.

When should I run a full project scope compliance audit before merging changes?▼

You should run a full project scope compliance audit before merging to ensure changes adhere to established guidelines and architecture. Scanning with all scopes provides a comprehensive conformity report without altering the code.