fix(commands): use standard markdown for bold in command output#58
Merged
WilliamBergamin merged 1 commit intoJun 22, 2026
Merged
Conversation
Capturing a /slack:channel-digest into a markdown file, the digest's bold headers (the Channel Digest title and the #channel names) rendered as italic. The commands emit single-asterisk bold (*text*), which is Slack's older mrkdwn convention, but standard markdown reads a single asterisk as italic and needs double asterisks for bold. This affects every standard-markdown surface the output lands in: markdown files and the Slack MCP server, which expects standard markdown (so draft-announcement writes a malformed-bold draft into Slack). While fixing channel-digest, found the same single-asterisk bold pattern in draft-announcement and standup, so all three commands are corrected to standard markdown.
|
Thanks for the contribution! Before we can merge this, we need @sahil-tandon to sign the Salesforce Inc. Contributor License Agreement. |
WilliamBergamin
approved these changes
Jun 22, 2026
WilliamBergamin
left a comment
Contributor
There was a problem hiding this comment.
Good find 💯 tested it on my end and this fixed the italic to bold issue
Thanks for your interest and contribution 🙏
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.
What this fixes/addresses
The
channel-digest,draft-announcement, andstandupcommands tell theassistant to format bold with a single asterisk (
*text*), Slack's oldermrkdwn convention. Standard markdown reads a single asterisk (or underscore) as italic and
requires double asterisks for bold. So wherever the command output lands in a
standard-markdown surface, the intended bold renders as italic. That includes
markdown files and the Slack MCP server, which expects standard markdown
(so, for instance,
draft-announcementwrites a malformed-bold draft into Slack).How I found it
I ran
/slack:channel-digestand saved the output into a markdown file. Thedigest's bold headers (the "Channel Digest" title and the
#channelnames)showed up italic instead of bold. Tracing it to the command template, it emits
single-asterisk bold. Found the same pattern in
draft-announcement(which even explicitly says to use
*bold*"not**bold**") andstandupas well,so this PR fixes all three. This also aligns the commands with the
slack-messagingskill, which already documents standard markdown (**bold**).How to reproduce
/slack:channel-digest <channel>onmainagainst any channel, andcapture the output to a markdown file (or post it to Slack).
*...*and render italic.**...**and renders bold.draft-announcementbehaves the same: it writes the announcement as a Slackdraft, so the malformed bold shows up directly in Slack (see screenshots).
The fix
commands/channel-digest.md— digest header lines to**...**commands/draft-announcement.md— formatting instruction to standard markdowncommands/standup.md— standup header lines to**...**Screenshots & verification
I verified end to end: created throwaway test channels, posted test messages, and ran
the affected commands both before and after the fix (reloading the plugin in
between). Before rendered italic; after rendered bold.
Markdown file (
channel-digest)Slack draft (
draft-announcement)