standardize-naming-conventions

Audits and renames tables, columns, and measures in TMDL-based Power BI semantic models.

887|131|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/data-goblin/power-bi-agentic-development --skill standardize-naming-conventions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: standardize-naming-conventions
Source: https://github.com/data-goblin/power-bi-agentic-development/tree/main/plugins/semantic-models/skills/standardize-naming-conventions
Command: npx skills add https://github.com/data-goblin/power-bi-agentic-development --skill standardize-naming-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Power BI semantic models often accumulate inconsistent naming—CamelCase, snake_case, abbreviations, and technical prefixes like DIM_ or FACT_—making them hard for business users to understand. This Skill audits and standardizes naming conventions across TMDL-based models while keeping all DAX references intact.

Core Features & Use Cases

  • Interactive Audit Workflow: Scans all TMDL table files, detects anti-patterns (abbreviations, programming conventions, inconsistent period/unit syntax), and presents a proposed rename table for user approval before changing anything.
  • Cross-File Reference Updates: Renames measures and columns while updating every DAX reference across all table files and relationships.tmdl, preventing broken models.
  • Business-Aligned Naming: Gathers organizational terminology from the user first, then applies rules from references/naming-rules.md covering measure name construction, display folder hierarchy, and descriptions.
  • Use Case: A model contains measures like NetSls, T.O. Qty PY, and tables like FACT_Invoices. The Skill proposes Net Sales, Turnover 1YP (Quantity), and Invoices, then applies the renames and warns about downstream report rebinding via pbir.

Quick Start

Ask the agent to standardize naming conventions in your semantic model by pointing it to the .SemanticModel/definition/ directory.

Frequently Asked Questions about standardize-naming-conventions

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

FAQPage Schema
How do I standardize naming conventions in a Power BI semantic model?

Point the Skill at your .SemanticModel/definition/ directory containing TMDL files. It scans all tables, proposes renames in an audit table for your approval, then applies changes while updating every DAX reference across the model.

How to rename measures in TMDL without breaking DAX references?

Rename the measure declaration, then search the entire definition directory for references using patterns like [Old Name] and update them to [New Name] across all table files and relationships.tmdl. The Skill automates this cross-file search and replacement.

Does renaming Power BI model fields break existing reports?

Yes, renaming model objects breaks downstream report visuals that reference those fields. After renaming, connected reports must be repaired using pbir fields replace or pbir fields replace-table rather than editing report JSON directly.

What naming convention should Power BI measures follow?

Use the construction order [Aggregation] [Base Name] [Period] ([Unit]), such as Turnover 1YP (Quantity). Names should be human-readable with spaces, spelled-out words, consistent period syntax like 1YP, and units in parentheses.

Can naming rules be customized for my organization's terminology?

Yes, the Skill asks about your business terminology, existing conventions, and period/unit preferences before renaming. The default rules in references/naming-rules.md are overridden whenever your organization has established standards.