docs(build-agent): add mcp_requirements frontmatter convention #51
Conversation
Add documentation for declaring MCP tool requirements in agent frontmatter. This prepares agents for future OpenCode includeTools support while documenting intent for human reviewers. - Add mcp_requirements YAML frontmatter pattern - Reference OpenCode issue #7399 for includeTools feature request - Link to Amp's lazy-load MCP approach as prior art - Explain token savings potential (e.g., 17k → 1.5k for chrome-devtools) Related: anomalyco/opencode#7399
|
Warning Rate limit exceeded@marcusquinn has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 6 minutes and 19 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📒 Files selected for processing (1)
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 of ChangesHello @marcusquinn, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request introduces a new documentation convention for Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
|
🔍 Code Quality Report�[0;35m[MONITOR]�[0m Code Review Monitoring Report �[0;34m[INFO]�[0m Latest Quality Status: �[0;34m[INFO]�[0m Recent monitoring activity: 📈 Current Quality Metrics
Generated on: Sun Jan 11 05:38:00 UTC 2026 Generated by AI DevOps Framework Code Review Monitoring |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request adds documentation for a new mcp_requirements frontmatter convention in agent files. The documentation is clear, well-structured, and effectively explains the purpose and future use of this convention for tool filtering. I have one minor suggestion to improve the consistency of code block language specifiers in the markdown file.
| augment-context-engine_*: true # Augment codebase search | ||
| wordpress-mcp_*: true # WordPress MCP tools | ||
| ```text | ||
| ``` |
There was a problem hiding this comment.
For consistency with the yaml block you've added below and for better syntax highlighting, it would be clearer to specify the language of this code block as yaml since its content is a YAML snippet.
| ``` | |
| ```yaml |
1 participant
Summary
Document the MCP tool filtering convention using YAML frontmatter in agent files.
Changes
mcp_requirementsfrontmatter documentation to build-agent.md