bmad-os-audit-file-refs

Name: bmad-os-audit-file-refs
Availability: InStock
Author: GenEd

Audit BMAD markdown and YAML files for file-reference convention violations.

Updated Mar 30, 2026

Search Tags:#workflow #markdown #audit #yaml #file references #bmad

Ready to run

npx skills add https://github.com/GenEducation/GenedUIProject --skill bmad-os-audit-file-refs-geneducation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-os-audit-file-refs
Source: https://github.com/GenEducation/GenedUIProject/tree/main/.gemini/skills/bmad-os-audit-file-refs
Command: npx skills add https://github.com/GenEducation/GenedUIProject --skill bmad-os-audit-file-refs-geneducation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams catch broken or nonconforming file references in BMAD source files before they cause workflow failures or confusing documentation links.

Core Features & Use Cases

Convention audit: Scans workflow and task markdown or YAML files for forbidden relative paths, bare filenames, and absolute system paths.
Parallel review: Breaks large file sets into batches so multiple subagents can check them consistently.
Verified reporting: Summarizes each violation with file and line detail, then validates file coverage before finalizing results.

Quick Start

Ask the skill to audit the selected BMAD files for file-reference convention violations and return every offending line.

Frequently Asked Questions about bmad-os-audit-file-refs

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

FAQPage Schema

How do I audit markdown and YAML files for broken file references?▼

You can audit markdown and YAML files for broken file references by scanning BMAD workflow and task documents to detect forbidden relative paths, bare filenames, and absolute system paths, reporting exact line-level violations.

What file path conventions are required for BMAD workflow files?▼

BMAD workflow files require canonical {project-root}/_bmad paths or {installed_path}/ paths. The audit skips runtime variables and fenced code examples, flagging documents that violate these file-reference conventions.

Can I batch review large sets of source files for path violations?▼

Yes, you can batch review large sets of source files for path violations. The process breaks large file sets into batches, allowing multiple subagents to check markdown and YAML documents consistently in parallel.

How does file reference auditing handle runtime variables and code examples?▼

File reference auditing skips runtime variables and fenced code examples entirely. It focuses solely on identifying nonconforming path conventions in active workflow and task markdown or YAML documents.

What is the best way to catch nonconforming file paths before a release?▼

The best way to catch nonconforming file paths before a release is to run a convention audit on BMAD source files under src/bmm, src/core, and src/utility, validating file coverage and summarizing violations with file and line detail.