naming-check
Skill0 starsChanged 2 months agoMITView on GitHub
Check or fix names of Fabric workspaces, items, tables, columns, branches and repo folders against the team's naming conventions. Use when creating anything new in Fabric, reviewing a pull request, when the user asks "what should I call this", or before committing workspace changes.
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- business-glossarySkill
- skill-nameSkill
- workspace-bootstrapSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Before a commit from a workspace
- Distinctive: line 25
Read the standard: Do not answer from memory.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Naming Check
Enforces ../../standards/naming-conventions.md. That file
is the source of truth — this skill is how it gets applied.
When to use
- Anything new is being created in Fabric or in this repo
- Reviewing a PR that adds or renames items
- The user asks what to call something
- Before a commit from a workspace
When not to use
- Deciding whether the thing should exist — that's a design conversation
- Renaming items already in production without checking downstream dependencies first
Procedure
- Read the standard. Do not answer from memory; it is edited more often than you think.
- Classify what is being named: workspace, item, table, column, branch, or repo folder.
- Apply the pattern and produce a concrete proposal, not a description of the rule.
Run the hard checks — these are correctness, not style:
Check Applies to Why No " / : < > \ * ? |Item display names Fabric replaces the Git folder name with a GUID No trailing space or .Item display names Same ≤ 256 characters Item display names Same No [ ] , ; { } ( ) =Delta column names Illegal in Delta/Parquet; fails at write time No stage suffix ( _dev,_prod)Item names Breaks deployment-pipeline item matching across stages Unique within the workspace Item names Two items with one name make the Git folder ambiguous - If renaming an existing item, check what points at it first: reports referencing a semantic model, notebooks referencing a lakehouse, pipeline activities. Renaming the item renames its Git folder, and dependency paths do not update themselves.
- Report as a table:
current → proposed → reason. If everything passes, say so in one line.
Failure modes
| Symptom | Cause | Fix |
| Git folder is a GUID instead of a name | Forbidden character / trailing space / too long | Rename in Fabric, commit again |
| Report broken after a rename | Semantic model folder renamed, definition.pbir still points at the old path | Update the dependency path, or rename back |
| Deployment pipeline creates duplicates instead of updating | Item names differ between stages | Make names identical across stages |
| Spark write fails on a valid-looking column | Space or bracket in the column name | Rename the column upstream |
Related
../../standards/naming-conventions.md— the rules../../standards/review-checklist.md— naming in review- Git integration process — the platform limits behind the hard checks
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.