API and Naming Conventions — refactor-chain · Java lane · step 07/09

Bundle: refactor-chain (orchestrated, self-healing refactor chain-of-skills). Lane: Java layered-architecture (Maven) · Position: step 07 of 09 · Prerequisite: refactor-java-06-dependency-guard · Next: refactor-java-08-common-extract. Adaptivity: Selects the product-line ruleset from pom.xml <groupId> (grp.pt, grp.budget, gfmis.bgtex / com.ctjsoft.gfmis).

Purpose

This step enforces API and naming conventions across a Java microservice as the final code-level refactoring pass that renames symbols and adjusts code content. It scans interface path structure, class names, property names, request parameters, response wrappers, and Bean name conflicts, then repairs the fixable findings without altering business logic. Because naming rules differ between product lines, the skill first detects the product line from pom.xml and loads the matching ruleset. It targets a consistency rate of at least 95% across repeated runs on identical code.

When to use

• The user wants to verify or repair interface and naming conventions after Controller-layer governance is complete.
• Trigger phrases: "check API naming", "fix naming conventions", "Step7 check", "Step7 fix", "standardize interface paths", "resolve Bean name conflict", "check and fix naming".

Rules enforced

Detect the product line first (Step 0, non-skippable): read the module's pom.xml, extract <groupId> (falling back to <parent>'s <groupId>), and map it to a product-line directory. Exact match takes priority over prefix match: grp.pt → products/技术中台/; grp.budget → products/预算/; gfmis.bgtex, com.ctjsoft.gfmis, grp.gfmis → products/执行/; grp.gfmis.* prefix → products/执行/; com.ctjsoft.gfmis.v3 → products/指标/; any other groupId falls back to the default products/技术中台/.