Skip to content

docs: Document notification customization via Long-Term Context#315

Open
promptless[bot] wants to merge 4 commits intomainfrom
promptless/notification-customization-via-ltc
Open

docs: Document notification customization via Long-Term Context#315
promptless[bot] wants to merge 4 commits intomainfrom
promptless/notification-customization-via-ltc

Conversation

@promptless
Copy link
Contributor

@promptless promptless bot commented Mar 23, 2026

Open this suggestion in Promptless to view citations and reasoning process

Adds a new documentation page explaining how customers can customize Promptless notification behavior.

What's new:
PR #2611 introduced customer-editable notification customization via Long-Term Context (LTC). Customers can now customize notification defaults, templates, tone, and delivery preferences by editing doc_workflow/notification_skill.md in their organization's LTC.

Changes:

  • Added new page at /docs/configuring-promptless/customizing-notifications explaining:
    • What Long-Term Context is and how to access it
    • The notification configuration file (doc_workflow/notification_skill.md)
    • What can be customized (defaults, templates, tone, delivery preferences)
    • Example customizations
    • Slack-specific notification features (interactive buttons, diff attachments, channel support)
  • Updated sidebar navigation to include the new page under "Configuring Promptless"

Revision (Mar 20): Updated button label from "Open PR" to "Create PR" to reflect the change in PR #2681, which replaced raw Slack Block Kit JSON with a fixed button enum.

Why this matters:
This is a new user-facing feature that was previously undocumented. Customers now have the ability to customize how Promptless notifies them about documentation suggestions, but without documentation they wouldn't know this capability exists or how to use it.

Related triggers:

promptless bot and others added 4 commits March 19, 2026 03:54
Introduces a new page explaining how customers can customize Promptless
notification behavior by editing doc_workflow/notification_skill.md in
their organization's Long-Term Context. Covers notification defaults,
templates, tone, delivery preferences, and Slack-specific features.
Reflects the button label change introduced in Promptless PR #2681.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…e": "CommitterType.USER", "files_deleted": [], "files_updated": ["src/lib/generated/sidebar.json"]}
@@ -0,0 +1,70 @@
---
Copy link
Contributor Author

Choose a reason for hiding this comment

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

PR #2611 introduced customer-editable notification customization via Long-Term Context. Customers can customize notification defaults, templates, tone, and delivery preferences by editing doc_workflow/notification_skill.md in their organization's LTC.

Source: https://github.com/Promptless/promptless/pull/2611

- **Channel support**: Receive notifications in specific channels by name, not just by ID

<Tip>
Promptless automatically detects protected branches in your documentation repository. When detected, Slack notifications show "Create PR" or "View PR" buttons instead of "Publish" to prevent merge errors.
Copy link
Contributor Author

Choose a reason for hiding this comment

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

PR #2681 changed the button label from "Open PR" to "Create PR"

Source: https://github.com/Promptless/promptless/pull/2681

@vercel
Copy link

vercel bot commented Mar 23, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
promptless-docs Ready Ready Preview, Comment Mar 23, 2026 6:19pm

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants