verify-architecture

Validate BioETL project architectures for design violations before merging.

1|Updated Dec 1, 2025
One-click install
npx skills add https://github.com/SatoryKono/BioactivityDataAcquisition --skill verify-architecture-satorykono
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-architecture
Source: https://github.com/SatoryKono/BioactivityDataAcquisition/tree/main/docs/skills/local/verify-architecture
Command: npx skills add https://github.com/SatoryKono/BioactivityDataAcquisition --skill verify-architecture-satorykono

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces BioETL architectural guidelines by automatically validating code, configurations, and workflows before changes are merged, preventing architectural drift.

Core Features & Use Cases

  • Quick checks: fast validation focusing on essential architectural rules to catch common issues.
  • Full checks: comprehensive analysis across modules, dependencies, and integrations for deeper quality.
  • Category checks: targeted validation tailored to specific architectural domains (e.g., data ingestion, governance).

Quick Start

Run a quick architecture check on your current branch to surface violations immediately.

Frequently Asked Questions about verify-architecture

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

FAQPage Schema
How do I validate BioETL project architecture before merging a pull request?

Validate BioETL architecture before merging by running quick, full, or category checks across code, docs, and configurations during pre-commit and pull request workflows to catch design violations and prevent architectural drift.

What architecture checks are available for BioETL configurations and code?

Available architecture checks include quick checks for essential rules, full checks for comprehensive module and dependency analysis, and category checks targeting specific architectural domains like data ingestion and governance.

How do I prevent architectural drift in BioETL workflows?

Prevent architectural drift in BioETL workflows by enforcing architecture rules automatically during pre-commit and pull request stages, collecting actionable failures, and outputting a report suitable for automation and developer feedback.

Can I run targeted architecture validation for specific BioETL domains?

Yes, you can run category checks to perform targeted architecture validation tailored to specific BioETL domains such as data ingestion or governance, ensuring focused compliance across project configurations.

Does BioETL architecture validation require any external dependencies?

No, BioETL architecture validation does not require external dependencies to run, allowing you to directly integrate pre-commit and pull request checks into your existing automation workflows without additional environment setup.

What is the best way to integrate BioETL governance checks into pull requests?

The best way to integrate BioETL governance checks into pull requests is by applying automated validation rules that surface actionable failures in a report format optimized for developer feedback and pipeline automation.