feat(slack): App Home quick-start tab

[izadoesdev]

Publishes a Home tab (the app's dashboard page in Slack) with a quick-start guide: what Databuddy can do, example questions, and the slash commands. Enabled via app_home_opened + views.publish.

Stacked on #595 (drill-downs) — will auto-retarget to staging when that merges.

Testing

• apps/slack suite: 73/73 pass (new app-home.test.ts). Typecheck + ultracite clean.
• View uses only Block Kit primitives already verified to render live in feat(slack): native Block Kit output, feedback buttons, rotating status #594 (header/section/divider/context). Not live-published to avoid writing to a real user's Home tab unprompted.

Follow-up

v1 is static guidance. Next: enrich with live data (open investigations count, connected sites) and quick-action buttons.

---

Summary by cubic

Publishes a Slack App Home tab with a quick-start guide to help users get started in Slack. The Home tab renders on open via app_home_opened and publishes the view with views.publish.

• New Features
  • Subscribes to app_home_opened in the manifest and registers a listener to publish the Home view.
  • Adds buildAppHomeView using Block Kit (header, sections, dividers, context) with suggested prompts and slash commands.
  • Extends Slack client types to include views.publish.

^{Written for commit 11f8c73. Summary will update on new commits.}

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
databuddy-status	Ready	Preview	Aug 6, 2026 6:16pm

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
dashboard	Skipped		Aug 6, 2026 6:16pm
documentation	Skipped		Aug 6, 2026 6:16pm

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 8b20291b-db3d-4b94-aa76-910bac08d696

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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

[unkey-deploy]

The latest updates on your projects. Learn more about Unkey Deploy

Name	Status	Preview	Inspect	Updated (UTC)
links (preview)	Ready	Visit Preview	Inspect	Aug 6, 2026 6:15pm

[greptile-apps]

Greptile Summary

The PR adds a static Slack App Home quick-start view and publishes it when users open the Home tab.

• Subscribes the Slack app to app_home_opened.
• Builds guidance from the existing suggested prompts and slash commands.
• Registers a listener that publishes the Home view to the opening user.
• Extends the Slack client contract with views.publish and adds view-builder tests.

Confidence Score: 4/5

The PR appears safe to merge, with a non-blocking typing issue in the new App Home view that should be cleaned up.

The manifest, command names, listener registration, and production Slack client path are aligned; the remaining concern is that generic unknown-based types bypass compile-time validation of the Block Kit payload.

Files Needing Attention: apps/slack/src/slack/app-home.ts, apps/slack/src/slack/listeners.ts, apps/slack/src/slack/app-home.test.ts

Important Files Changed

Filename	Overview
apps/slack/slack-app-manifest.json	Adds the app_home_opened bot event while retaining the existing enabled App Home configuration.
apps/slack/src/slack/app-home.ts	Builds the static Home view correctly, but uses a generic Record<string, unknown> instead of Slack's explicit view type.
apps/slack/src/slack/listeners.ts	Publishes the view for Home-tab events and logs API failures, but relies on an unchecked double assertion.
apps/slack/src/slack/types.ts	Extends the client abstraction with the production WebClient's views.publish method.
apps/slack/src/slack/app-home.test.ts	Covers the view's basic structure and prompt inclusion, while repeating the generic unknown-based block type.

Sequence Diagram

sequenceDiagram
  participant U as Slack user
  participant S as Slack
  participant L as App listener
  participant V as views.publish
  U->>S: Open Databuddy Home tab
  S->>L: app_home_opened
  L->>L: Build static quick-start view
  L->>V: Publish view for event.user
  V-->>U: Render App Home

Loading

_{Reviews (1): Last reviewed commit: "feat(slack): publish an App Home tab wit..." | Re-trigger Greptile}

[greptile-apps]

Use an explicit Slack view type

Returning Record<string, unknown> forces the listener to double-cast the result before publishing and prevents the compiler from validating future Block Kit changes. Type the builder with Slack's Home view contract and use the same concrete block types in the test.

Context Used: Basic guidelines for the project so vibe coders do... (source)

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!