rule-checker

Verify code compliance against standardized rule references for architecture and conventions.

Updated Jan 4, 2026

Search Tags:#static-analysis #naming-conventions #code-review #module-architecture #dependency-direction #rule-checking

Ready to run

npx skills add https://github.com/YeaChan05/Remittance --skill rule-checker

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rule-checker
Source: https://github.com/YeaChan05/Remittance/tree/main/.codex/skills/rule-checker
Command: npx skills add https://github.com/YeaChan05/Remittance --skill rule-checker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Check whether implemented code follows the copied references/rule/** rule documents for module structure, dependency direction, naming, and Spring Boot/JPA/RabbitMQ/Liquibase conventions. Use when reviewing a diff, module, package, build.gradle.kts, or implementation for compliance with the copied rule references.

Core Features & Use Cases

Validates module boundaries and architecture against the rule references.
Checks dependency directions to prevent illegal cross-domain coupling.
Ensures naming consistency and alignment with the prescribed conventions.
Use during diffs, module reviews, package audits, and implementation assessments.

Quick Start

Run the checker against the target module to identify grounded rule violations.

Frequently Asked Questions about rule-checker

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

FAQPage Schema

How do I check code diffs against module architecture and naming conventions?▼

The rule checker validates code compliance by verifying module structure, dependency direction, and naming conventions against standardized rule references. It checks diffs, packages, and implementations during review to identify violations.

Can I validate Gradle build scripts for dependency direction violations?▼

Yes, you can validate Gradle scripts. The checker applies to build.gradle.kts files, verifying dependency directions and module boundaries to prevent illegal cross-domain coupling during your build configuration review.

Does this static analysis tool support Spring Boot and JPA convention checks?▼

Yes, this static analysis tool supports Spring Boot and JPA convention checks. It verifies implementation compliance against copied rule references covering Spring Boot, JPA, RabbitMQ, and Liquibase conventions during code review.

What is the best way to audit package structure for illegal cross-domain coupling?▼

The best way to audit package structure is running a rule-compliance check that validates module boundaries and dependency directions. This ensures package audits identify illegal cross-domain coupling against your architecture guidelines.

Do I need copied rule reference documents to perform implementation assessments?▼

Yes, you need copied rule reference documents. The checker grounds its implementation assessments by comparing code against copied references/rule/** documents to verify compliance with prescribed module and framework conventions.