feat(bmad-help): llms.txt support for general questions#2230
Conversation
…tions Register llms.txt URLs in module-help.csv via _meta rows so bmad-help can fetch module documentation when users ask questions that don't map to a specific skill.
🤖 Augment PR SummarySummary: Adds llms.txt-based fallback answering for general questions in 🤖 Was this summary useful? React with 👍 or 👎 |
src/core-skills/bmad-help/SKILL.md
Outdated
|
|
||
| ## General Questions via llms.txt | ||
|
|
||
| When a user's question does not match any specific skill in the catalog, check for `_meta` rows. These rows have `_meta` in the `skill` column (or `phase` column in the merged CSV) and carry a module's documentation URL in `output-location`. |
There was a problem hiding this comment.
The note that _meta appears in the skill column “(or phase column in the merged CSV)” seems to conflict with the earlier “CSV Interpretation” section that defines the catalog schema; this ambiguity could cause the _meta detection to key off the wrong column name/order.
Severity: medium
🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.
src/core-skills/bmad-help/SKILL.md
Outdated
|
|
||
| **Behavior**: | ||
| 1. Identify which module(s) the question relates to. If ambiguous, prefer the active module or ask. | ||
| 2. Fetch the llms.txt URL for that module using WebFetch or equivalent. |
There was a problem hiding this comment.
Because this instructs the assistant to fetch and use external content, consider explicitly treating fetched llms.txt content as untrusted reference material (i.e., do not follow any embedded instructions) to reduce prompt-injection risk.
Severity: medium
🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.
| ] = columns; | ||
|
|
||
| // Pass through _meta rows as-is (module metadata, not a skill) | ||
| if (phase === '_meta') { |
There was a problem hiding this comment.
This _meta pass-through only executes inside the columns.length >= 12 guard; if a module provides a minimal _meta row (e.g., just module + _meta + output-location), it will be silently skipped and the llms.txt fallback won’t work for that module.
Severity: medium
🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThis pull request introduces support for general questions via module documentation. It adds a Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
_metarows to core and BMMmodule-help.csvfiles registeringhttps://docs.bmad-method.org/llms.txt_metarows through cleanly during CSV mergeTest plan