bmad-os-audit-file-refs

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

8|2|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/bmad-code-org/bmad-utility-skills --skill bmad-os-audit-file-refs-bmad-code-org
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-os-audit-file-refs
Source: https://github.com/bmad-code-org/bmad-utility-skills/tree/main/skills/bmad-os-audit-file-refs
Command: npx skills add https://github.com/bmad-code-org/bmad-utility-skills --skill bmad-os-audit-file-refs-bmad-code-org

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves broken file links and inconsistent pathing conventions across the BMAD codebase, preventing runtime errors caused by incorrect file references.

Core Features & Use Cases

  • Automated Auditing: Scans source files to identify non-compliant path references like relative paths or absolute system paths.
  • Standardization: Enforces the use of canonical project-root and installed-path variables to ensure cross-environment compatibility.
  • Use Case: Use this skill during a repository maintenance sprint to verify that all workflow and task files adhere to the strict BMAD pathing conventions before a major release.

Quick Start

Ask the assistant to audit file references in the current project to identify and report any pathing convention violations.

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?▼

Auditing markdown and yaml files for broken file references involves scanning source code to identify relative or absolute path violations and validating them against canonical project-root and installed-path variables.

What is the best way to enforce strict file pathing conventions in a codebase?▼

Enforcing strict file pathing conventions requires automated auditing that targets core, utility, and bmm directories to identify non-compliant path references and ensure cross-environment compatibility.

How do I check for relative or absolute path violations across project files?▼

Checking for relative or absolute path violations involves utilizing parallel subagent processing to validate references within markdown and yaml files against canonical project-root standards.

When should I run a file-reference integrity audit during a release cycle?▼

Run a file-reference integrity audit during a repository maintenance sprint before a major release to verify that all workflow and task files adhere to strict pathing conventions and prevent runtime errors.

Can I use automated path validation to prevent runtime errors from incorrect file references?▼

Automated path validation resolves broken file links and inconsistent pathing conventions across the codebase, preventing runtime errors caused by incorrect file references using canonical installed-path standards.