consistency-reviewer

Audit Rust code for cross-module naming and pattern inconsistencies.

1|Updated Jul 2, 2025
One-click install
npx skills add https://github.com/jeickmeier/rfin --skill consistency-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: consistency-reviewer
Source: https://github.com/jeickmeier/rfin/tree/main/.cursor/skills/consistency-reviewer
Command: npx skills add https://github.com/jeickmeier/rfin --skill consistency-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures your codebase maintains a high degree of internal consistency, preventing pattern drift and making maintenance easier.

Core Features & Use Cases

  • Pattern Auditing: Identifies inconsistencies in naming conventions, error handling, and API design across modules.
  • Drift Detection: Catches deviations from established patterns, ensuring uniformity.
  • Use Case: Before a major release, use this Skill to audit the entire finstack library for any new naming inconsistencies or duplicated logic that has crept in during development.

Quick Start

Review the finstack/core module for naming convention inconsistencies.

Frequently Asked Questions about consistency-reviewer

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

FAQPage Schema
How do I check for pattern drift and naming inconsistencies in Rust code?

You can unify code patterns by auditing your modules for naming convention violations, pattern drift, and duplicated logic. This process identifies deviations from established patterns and missed Rust std-lib opportunities to boost overall maintainability.

What is the best way to find duplicated logic across code modules?

Finding duplicated logic requires cross-module consistency reviews to catch deviations and repeated functionality. Detecting these inconsistencies helps unify API design conventions, error handling, and structural patterns across the entire codebase.

Can I use this consistency review to unify code patterns before a major release?

Yes, you can audit your codebase before a major release to find new naming inconsistencies or duplicated logic that appeared during development. This ensures your modules maintain a high degree of internal consistency and pattern uniformity.

How do I detect missed Rust std-lib opportunities during a code review?

Detecting missed Rust std-lib opportunities involves reviewing your code against standard library functionalities to identify duplicated logic. This audit checks whether existing standard library patterns are utilized rather than maintaining redundant implementations.

Does this consistency auditing approach work for checking API design conventions?

Yes, consistency auditing evaluates API design conventions alongside naming and error handling patterns across modules. This detects pattern drift and convention violations, ensuring your library maintains uniform API design throughout development.