pair-capability-verify-adoption

Name: pair-capability-verify-adoption
Availability: InStock
Author: Foomakers

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

6|Updated Aug 3, 2025

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

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that code and configurations adhere to established project adoption files, preventing drift and maintaining consistency across the development lifecycle.

Core Features & Use Cases

Compliance Checking: Scans code, dependencies, and configurations against defined standards for tech stack, architecture, security, coding style, and infrastructure.
Detection-Only: Reports conformity or non-conformity without attempting to fix issues, empowering developers or other agents to resolve them.
Use Case: Before merging a pull request, use this Skill to automatically verify that all new dependencies are approved, architectural patterns are followed, and security best practices are implemented.

Quick Start

Use the pair-capability-verify-adoption skill to check the 'all' scope for compliance with project standards.

Frequently Asked Questions about pair-capability-verify-adoption

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

FAQPage Schema

How do I verify code compliance against project architecture and security standards?▼

Code compliance verification scans code and configurations against project adoption files to detect non-conformities in tech stack, architecture, security, coding standards, and infrastructure, reporting findings without resolving issues.

What is the best way to check code for non-conformities before a pull request merge?▼

Checking code for non-conformities before a merge involves scanning dependencies and configurations against defined project standards, reporting violations in architectural patterns or security best practices for developers to resolve.

Can I use this verification approach to scan infrastructure configuration and coding style?▼

Yes, scanning infrastructure configuration and coding style is supported by verifying them against project adoption files for specified scopes, detecting non-conformities across tech stack, architecture, security, and infrastructure without applying fixes.

Does this code review verification automatically fix architectural pattern violations?▼

No, this code review verification does not automatically fix architectural pattern violations; it is a detection-only process that reports conformity or non-conformity, delegating all issue resolution to developers or other skills.

When do I need to run adoption file compliance checks during the development lifecycle?▼

You need to run adoption file compliance checks to prevent drift and maintain consistency across the development lifecycle, such as before merging pull requests, by verifying that all new dependencies and configurations are approved.