Support bmad-automator runtime copy in BMAD installer - #3
Open
dickymoore wants to merge 4 commits into
Open
Conversation
dickymoore
marked this pull request as ready for review
May 2, 2026 06:39
bma-d
force-pushed
the
bma-d/add-automator
branch
2 times, most recently
from
May 8, 2026 21:10
373badb to
a3e0545
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Follow-up on
bma-d/add-automatorfor a gap in the Automator source-root packaging.BMAD-METHOD installs the Automator module from
payload/.claude/skills, but the story automator skill expects its Python helper runtime inside the installedbmad-story-automatorskill directory. This PR copies only the required Automator runtime directories from the cloned Automator repo into that installed skill:source/scripts->bmad-story-automator/scriptssource/src->bmad-story-automator/srcScope
Intentionally limited to
bmasource-root installs. This does not change:What this changes
After installing the bma module payload, checks whether bmad-story-automator/SKILL.md exists in the target.
If present, copies:
Adds a regression test covering the source-root layout.
What this does not do
Open question
Is this the desired place to handle the Automator runtime copy?
If bma is intended to be installable through the normal BMAD installer using the current bmad-automator package layout, this PR looks necessary.
If the marketplace package should instead be made install-shaped, with the runtime already included inside the module payload, then this special-case installer hook may be redundant.
Tests
node test/test-installation-components.jsnpm run test:refsnpm run test:installnpm run test:urlsnpm run test:channelsnpm run lintnpm run lint:mdnpm run format:check