code-style

Align code naming, packaging, and bean wiring to nearby Remittance patterns.

Updated Jan 4, 2026

Search Tags:#refactoring #coding-standards #naming-conventions #code-review #code-style #package-structure #remittance

Ready to run

npx skills add https://github.com/YeaChan05/Remittance --skill code-style-yeachan05

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Align code naming, packaging, and wiring to Remittance's nearby patterns, reducing drift during reviews and onboarding.

Core Features & Use Cases

Align file naming, package structure, class suffix, and bean wiring to nearby patterns.
Document style drift during code reviews and propose consistent changes.
Use Case: When a change introduces mismatched naming, run this skill to align it with existing references.

Quick Start

Align the recently changed files' naming, packaging, and bean wiring to match nearby Remittance patterns.

Frequently Asked Questions about code-style

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

FAQPage Schema

How do I align code naming and package structure during a code review?▼

To align code naming and package structure during a code review, compare recently changed files against 1–3 nearby reference implementations to enforce naming consistency, package alignment, and class suffix normalization.

What is the best way to fix naming convention drift in Remittance code?▼

Fixing naming convention drift in Remittance code involves comparing mismatched file naming, package structure, and bean wiring against nearby reference implementations to propose consistent changes.

How do I normalize bean wiring patterns and class suffixes for new code changes?▼

Normalize bean wiring patterns and class suffixes by comparing the new code against 1–3 established reference implementations within the same nearby Remittance package structure.

Can I use this approach to document style drift during onboarding?▼

Yes, you can document style drift during onboarding by running the alignment check on recently changed files to identify mismatches in naming, packaging, and bean wiring against established conventions.

When do I need to compare against reference implementations for code refactoring?▼

You need to compare against 1–3 reference implementations for code refactoring when changes introduce mismatched naming, packaging, or bean wiring that drift from established Remittance conventions.