fix: remove stray closing quote in quick-spec step-04-review.md

[arcaven]

What

Remove errant closing quote on line 42 of step-04-review.md that creates malformed markdown output in the Quick Summary display block.

Why

The trailing " on line 42 doesn't properly close the multi-line quoted block and appears literally in workflow output, creating inconsistent formatting.

Fixes #1433

How

• Removed the trailing " from line 42: - {files_count} files to modify" → - {files_count} files to modify
• The opening quote on line 38 ("**Quick Summary:**) now stands alone as a display marker, consistent with other display patterns in the file

Testing

• Verified the change matches the expected fix described in issue [Bug] Stray closing quote in step-04-review.md breaks Quick Summary template #1433
• Confirmed no other references to this line exist that would break

[coderabbitai]

📝 Walkthrough

Walkthrough

Removes a stray closing quotation mark from the Quick Summary template in the review step that was breaking markdown output formatting.

Changes

Cohort / File(s)	Change Summary
Template text correction src/bmm/workflows/bmad-quick-flow/quick-spec/steps/step-04-review.md	Removes trailing " from line 42 (- {files_count} files to modify" → - {files_count} files to modify) to fix malformed markdown output in Quick Summary.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• refactor: convert create-tech-spec to sharded workflow with orient-first pattern #1185: Introduces the step-04-review.md file and initial review step structure that this PR corrects.
• refactor: standardize quick-flow menu patterns to newer format #1388: Modifies the same step-04-review.md file's menu and template handling logic.

Suggested reviewers

• pbean
• muratkeremozcan

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: removing a stray closing quote from step-04-review.md that was causing formatting issues.
Description check	✅ Passed	The description clearly relates to the changeset, explaining what was changed, why it was necessary, and how it was fixed.
Linked Issues check	✅ Passed	The pull request directly addresses issue #1433 by removing the errant closing quote on line 42, matching the exact fix specified in the linked issue.
Out of Scope Changes check	✅ Passed	The change is narrowly scoped to fixing the specific issue: removing a single trailing quote character from one line in the specified file.
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
• Post copyable unit tests in a comment

---

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.}

[bmadcode]

There is an opening quote than that should also be removed on line 38 @arcaven - or better yet we should not hard code exaclt output and instead give the model the intent for output. cc @alexeyv

[arcaven]

Thanks @bmadcode - good catch! I've pushed a follow-up commit to remove the orphaned opening quote on line 38 as well. Both quotes are now removed, so the Quick Summary displays as regular markdown without the enclosing quotes.

[arcaven]

I suppose it's more of a problem for my linters and isn't an actual bug now that I see the full context. In any case, it seems like a completely optional set of quotes, with little upside, and the potential for more reports. But I'm not at all offended with a declined PR. Thanks for sharing your hard work with BMAD.

[alexeyv]

@arcaven Before I know what to do with this, I'd like to understand exactly what does this look like in your session, and what LLM/platform are we talking. That pair of double quotes is supposed to mark the beginning and end of the output template. Is it getting into the output?

[arcaven]

@arcaven Before I know what to do with this, I'd like to understand exactly what does this look like in your session, and what LLM/platform are we talking. That pair of double quotes is supposed to mark the beginning and end of the output template. Is it getting into the output?

It parses fine as-is for LLM and in session, it is strictly a linter and LLM code review trap, false half-quote. I suggest the trap is not needed, entirely optional, as with and without quotes is semantically similar, but i’m not attached to this topic, I wouldn’t open it now if i understood it as I do now.

[alexeyv]

It parses fine as-is for LLM and in session, it is strictly a linter and LLM code review trap, false half-quote.
Gotcha. Stuff like this is borderline worth fixing because linter noise is bad. Is that Markdown linter or what kind of linter?

[arcaven]

It parses fine as-is for LLM and in session, it is strictly a linter and LLM code review trap, false half-quote.
Gotcha. Stuff like this is borderline worth fixing because linter noise is bad. Is that Markdown linter or what kind of linter?

i hit it with yamllint vs code yaml lint extension (shouldn't be highlighting in markdown anyways!) a qudo review using openai keys in our copy of the generated checked out versions, and my own dumb eyeballs and human context window failing to scroll back sufficiently to see the opening quote while being excited about the other issues I was overexcited to offer PRs about. My apologies. Then I realized: if i hit it someone else might, and, asked myself why bother with the multi-line quote? it’s not sprintf. It’s an LLM, save the bytes! it gets the intent both ways. shorter is better? happy to close the report, it’s false but well intended.

[arcaven]

withdrawing, not up to my standard

[alexeyv]

@arcaven for some hard to explain reasons, I actually love this PR, and how it ended up :) Thanks!