refactor: simplify violation message format, remove redundant line numbers

- Remove '1:1' prefix from all violation message templates
- Use simple '<code> - <message>' format for frontmatter violations
- Add SPEC clarification: line numbers only included when actually known
- Frontmatter is always at line 1, so '1:1' prefix is redundant

Generated by Mistral Vibe.
Co-Authored-By: Mistral Vibe <vibe@mistral.ai>
This commit is contained in:
nvaldez
2026-09-24 22:13:37 +02:00
parent 15caca081f
commit 86b0dc9948
2 changed files with 11 additions and 10 deletions
+4 -3
View File
@@ -452,10 +452,11 @@ Requirements:
- Support configurable required fields via `fiona-settings.json` for
different file types (e.g., `type: toc` files may have different requirements).
- Report violations in AI-friendly format: file path, missing fields, and
line number (if frontmatter exists but is incomplete).
line number (if known). Violation messages use the format `<code> - <message>`.
For frontmatter violations, line numbers are omitted as frontmatter is always
at the start of the file (line 1), so `1:1` prefix is redundant.
- Handle files without frontmatter (report as missing all required fields).
- Handle files with malformed YAML frontmatter (report as parse error with
line number).
- Handle files with malformed YAML frontmatter (report as parse error).
- Respect `.gitignore` and read-only zones (`personal/`, `raw/`).
Acceptance criteria:
+7 -7
View File
@@ -69,37 +69,37 @@ VIOLATION_CODES = {
"FML001": {
"rule_name": "Frontmatter Parse Error",
"description": "Failed to parse YAML frontmatter",
"message_template": "1:1 FML001 - {error}"
"message_template": "FML001 - {error}"
},
"FML002": {
"rule_name": "Missing Frontmatter",
"description": "Markdown file is missing YAML frontmatter",
"message_template": "1:1 FML002 - No frontmatter found"
"message_template": "FML002 - No frontmatter found"
},
"FML003": {
"rule_name": "Missing Name Field",
"description": "Required frontmatter field 'name' is missing",
"message_template": "1:1 FML003 - Missing required field: name"
"message_template": "FML003 - Missing required field: name"
},
"FML004": {
"rule_name": "Missing Description",
"description": "SKILL.md files must have a description field in frontmatter",
"message_template": "1:1 FML004 - SKILL.md files must have a description field"
"message_template": "FML004 - SKILL.md files must have a description field"
},
"FML005": {
"rule_name": "Invalid Skill Name",
"description": "Skill name must contain only lowercase letters, numbers, and hyphens (a-z, 0-9, -)",
"message_template": "1:1 FML005 - Skill name must contain only lowercase letters, numbers, and hyphens"
"message_template": "FML005 - Skill name must contain only lowercase letters, numbers, and hyphens"
},
"FML006": {
"rule_name": "Skill Name Mismatch",
"description": "Skill name in frontmatter must match the parent folder name",
"message_template": "1:1 FML006 - Skill name must match parent folder name (expected: {expected}, got: {actual})"
"message_template": "FML006 - Skill name must match parent folder name (expected: {expected}, got: {actual})"
},
"FML007": {
"rule_name": "Missing Version Field",
"description": "Required frontmatter field 'version' is missing",
"message_template": "1:1 FML007 - Missing required field: version"
"message_template": "FML007 - Missing required field: version"
}
}