verify

Run Maven verify to detect architecture test failures and dependency issues.

Updated Jan 3, 2026
One-click install
npx skills add https://github.com/nagashima-toru/sandbox-claude-code --skill verify-nagashima-toru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/nagashima-toru/sandbox-claude-code/tree/main/.claude/skills/verify
Command: npx skills add https://github.com/nagashima-toru/sandbox-claude-code --skill verify-nagashima-toru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maven-based verification ensures architectural integrity and code quality across a Java project by validating architecture rules and tests after changes to the application or domain layers.

Core Features & Use Cases

  • Run Maven verify to execute architecture tests and quality checks.
  • Detect and report ArchitectureTest failures, guiding developers to fix problematic imports and dependency directions.
  • Re-run verification to confirm clean architecture compliance after fixes.

Quick Start

Run the Verification Skill to execute the Maven verify phase and validate architecture boundaries.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I enforce clean architecture rules in a Java Maven project?

Running Maven verify executes architecture tests to validate module boundaries and check code quality after changes to Java application or domain layers.

Why does my Maven build fail during the verify phase?

Maven verify fails when ArchitectureTest rules detect architecture violations such as improper dependency directions or illegal imports between modules, requiring you to fix the violating imports before re-running.

How do I check for dependency direction violations across Java modules?

You check dependency direction violations by running Maven verify to execute ArchitectureTests, which detect problematic imports and guide developers to fix architectural boundary breaches across modules.

When should I run Maven verify to validate architecture boundaries?

You should run Maven verify after making changes to the application or domain layers to ensure clean architecture compliance across all modules before finalizing your code quality checks.

Can Maven verify detect specific imports that violate architecture rules?

Yes, Maven verify detects ArchitectureTest failures and points directly to violating imports, prompting developers to fix dependency directions before re-running verification to confirm compliance.