New Module: auto-bmad

[bramvera]

New Module Submission

Module: auto-bmad
Category: software-development / dev-tools
Repository: https://github.com/bramvera/auto-bmad
Version: 0.9.2
License: MIT

Description

Automated BMAD pipeline orchestration plugin for Claude Code. Runs structured SDLC sprints with quality gates at every step.

• Quick mode: 3 steps per story (create, develop, code review) — no TEA required
• Full mode: 11 steps per story (create, validate, adversarial review, ATDD, develop, edge-case hunt, 3x code review, trace, test automate) — requires TEA
• Resumable sprints with per-story git checkpoints and rollback
• Brownfield pipelines for existing codebases

Checklist

• Module built with BMad Builder
• .claude-plugin/marketplace.json present
• Tagged release (v0.9.2) on GitHub
• Registry YAML added to registry/community/

Summary by CodeRabbit

• New Features
  • Added the "auto-bmad" community module (v0.9.2) to the registry, expanding available modules.
  • Module is not selected by default and is listed with an unverified trust tier.
  • Includes metadata (display name, description, repository reference, author/license) to help identify and evaluate the module.

[coderabbitai]

Warning

Rate limit exceeded

@bramvera has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 22 minutes and 55 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 22 minutes and 55 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: a681479c-f4c0-4953-9c10-31419546b3c0

📥 Commits

Reviewing files that changed from the base of the PR and between 697261d and ae85884.

📒 Files selected for processing (1)

• registry/community/auto-bmad.yaml

Walkthrough

Added a new community registry YAML entry registry/community/auto-bmad.yaml defining the auto-bmad module's metadata, classification, default selection, and version 0.9.2 approval fields.

Changes

Cohort / File(s)	Summary
Community Registry Entry registry/community/auto-bmad.yaml	New YAML registry definition for the auto-bmad module: name/display_name/code, description, repository, module_definition path, author, license, type/category/subcategory, keywords, default_selected, and version 0.9.2 approval metadata (approved_tag, approved_sha, approved_date, reviewer, trust_tier).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐇 I hopped a small YAML tune today,
A module nestled in registry hay,
auto-bmad arrives with version cheer,
Approved tag tucked safely near,
— a happy rabbit, skipping away 🥕

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'New Module: auto-bmad' directly and clearly describes the main change—adding a new community registry entry for the auto-bmad module.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 3

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@registry/community/auto-bmad.yaml`:
- Line 26: The approved_date field in registry/community/auto-bmad.yaml is set
to a future date ("2026-04-13"); update the approved_date value to a valid
approval date (e.g., the PR creation or actual approval date "2026-04-12") or
remove the approved_date key until approval is finalized so the metadata does
not contain a future-dated approval timestamp.
- Line 27: Replace the placeholder reviewer value by setting the YAML "reviewer"
key from "pending" to a real GitHub handle (e.g., "reviewer: github-username")
so the registry has a verifiable reviewer; locate the "reviewer" field in this
auto-bmad.yaml manifest and update its value to an actual reviewer GitHub handle
that meets the registry's schema requirements.
- Line 6: The module_definition field currently contains a repository-prefixed
path which may break registry lookup; change the value of module_definition to a
repo-relative path (remove the leading repo-name prefix) so it points directly
to the module YAML inside the repo (e.g., reference the
skills/.../assets/module.yaml location instead of auto-bmad/skills/...). Update
the module_definition entry to the repo-relative path and verify the installer
can resolve the module.yaml via that key.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 21668cbe-ec40-490a-9677-7922fe2d943e

📥 Commits

Reviewing files that changed from the base of the PR and between 7992544 and f988c18.

📒 Files selected for processing (1)

• registry/community/auto-bmad.yaml

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Use an actual reviewer GitHub handle instead of placeholder

Line 27 uses reviewer: pending. Schema description calls for a reviewer GitHub handle; a placeholder weakens traceability and may violate registry policy.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@registry/community/auto-bmad.yaml` at line 27, Replace the placeholder
reviewer value by setting the YAML "reviewer" key from "pending" to a real
GitHub handle (e.g., "reviewer: github-username") so the registry has a
verifiable reviewer; locate the "reviewer" field in this auto-bmad.yaml manifest
and update its value to an actual reviewer GitHub handle that meets the
registry's schema requirements.