Skip to content

fix(commands): use standard markdown for bold in command output#58

Merged
WilliamBergamin merged 1 commit into
slackapi:mainfrom
sahil-tandon:fix/slack-commands-standard-markdown
Jun 22, 2026
Merged

fix(commands): use standard markdown for bold in command output#58
WilliamBergamin merged 1 commit into
slackapi:mainfrom
sahil-tandon:fix/slack-commands-standard-markdown

Conversation

@sahil-tandon

@sahil-tandon sahil-tandon commented Jun 21, 2026

Copy link
Copy Markdown
Contributor

What this fixes/addresses

The channel-digest, draft-announcement, and standup commands tell the
assistant to format bold with a single asterisk (*text*), Slack's older
mrkdwn 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-announcement writes a malformed-bold draft into Slack).

How I found it

I ran /slack:channel-digest and saved the output into a markdown file. The
digest's bold headers (the "Channel Digest" title and the #channel names)
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**") and standup as well,
so this PR fixes all three. This also aligns the commands with the
slack-messaging skill, which already documents standard markdown (**bold**).

How to reproduce

  1. Run /slack:channel-digest <channel> on main against any channel, and
    capture the output to a markdown file (or post it to Slack).
  2. The headers come out as *...* and render italic.
  3. On this branch, the same command emits **...** and renders bold.
  4. draft-announcement behaves the same: it writes the announcement as a Slack
    draft, 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 markdown
  • commands/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)

  • Before (single asterisk, renders italic):
channel-digest after
  • After (double asterisk, renders bold):
channel-digest before

Slack draft (draft-announcement)

  • Before (single asterisk, renders italic):
Screenshot 2026-06-20 at 11 17 00 PM
  • After (double asterisk, renders bold):
Screenshot 2026-06-20 at 11 11 08 PM

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.
@salesforce-cla

Copy link
Copy Markdown

Thanks for the contribution! Before we can merge this, we need @sahil-tandon to sign the Salesforce Inc. Contributor License Agreement.

@WilliamBergamin WilliamBergamin left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good find 💯 tested it on my end and this fixed the italic to bold issue

Thanks for your interest and contribution 🙏

@WilliamBergamin WilliamBergamin added bug Something isn't working semver:patch Changes trigger a patch version bump labels Jun 22, 2026
@WilliamBergamin WilliamBergamin merged commit b25488e into slackapi:main Jun 22, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working cla:signed semver:patch Changes trigger a patch version bump

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants