Add slack-summarizer extension

[zahassanyum]

Description

Summarize any Slack channel, thread, or message directly from Raycast using OpenAI.

Perfect for catching-up after vacations, keeping stakeholders in the loop, or turning noisy discussions into succinct, bullet-point briefs.

Screencast

Raycast.extension.mp4

Checklist

• I read the extension guidelines
• I read the documentation about publishing
• I ran npm run build and tested this distribution build in Raycast
• I checked that files in the assets folder are used by the extension itself
• I checked that assets used by the README are placed outside of the metadata folder

[raycastbot]

Congratulations on your new Raycast extension! 🚀

You can expect an initial review within five business days.

Once the PR is approved and merged, the extension will be available on our Store.

[greptile-apps]

PR Summary

This PR introduces a comprehensive Slack summarizer extension that leverages OpenAI to generate concise summaries of Slack channels and threads directly within Raycast.

• Implements robust rate limiting and pagination handling in slackApi.js with exponential backoff for large channel histories
• Uses PKCE OAuth flow for secure Slack authentication with proper scoping and token management
• Includes intelligent caching strategies for channel lists (24h) and user data (14 days) to minimize API calls
• Provides customizable OpenAI prompts through preferences while maintaining sensible defaults
• Properly handles thread URL parsing and message formatting with user mention replacements

Note: The implementation follows Raycast's best practices and includes all necessary documentation and configuration files. The CHANGELOG.md correctly uses the {PR_MERGE_DATE} template.

_{💡 (2/5) Greptile learns from your feedback when you react with 👍/👎!}

_{13 file(s) reviewed, 13 comment(s)
Edit PR Review Bot Settings | Greptile}

[greptile-apps]

logic: Title 'Slack Summaries' in CHANGELOG.md doesn't match 'Slack Summarizer' in package.json title field

Suggested change

	# Slack Summaries Changelog
	# Slack Summarizer Changelog

[greptile-apps]

syntax: Grammar issue in description: 'Summarize a Slack channel threads' should be 'Summarize Slack channel threads' or 'Summarize a Slack channel's threads'

Suggested change

	"description": "Summarize a Slack channel threads",
	"description": "Summarize Slack channel threads",

[greptile-apps]

syntax: Inconsistent spelling: 'summarising' should be 'summarizing' to match American English used elsewhere

Suggested change

	"description": "Custom prompt used when summarising a channel",
	"description": "Custom prompt used when summarizing a channel",

[greptile-apps]

logic: gpt-4.1 is not a valid OpenAI model. Should use gpt-4 or gpt-3.5-turbo as placeholder and default

Suggested change

	"placeholder": "gpt-4.1",
	"default": "gpt-4.1",
	"placeholder": "gpt-4",
	"default": "gpt-4",

[greptile-apps]

style: Consider using showFailureToast from @raycast/utils instead of manually setting toast properties

Suggested change

	} catch (error) {
	toast.style = Toast.Style.Failure;
	toast.title = "Couldn't generate summary";
	if (error instanceof Error) {
	toast.message = error.message;
	}
	} catch (error) {
	showFailureToast(error, { title: "Couldn't generate summary" });
	if (error instanceof Error) {
	toast.message = error.message;
	}

[greptile-apps]

style: cachedApp should be declared as let cachedApp: App | undefined to ensure proper typing

Suggested change

	let cachedApp;
	let cachedApp: App | undefined;

[greptile-apps]

logic: slackOAuth.authorize() should be wrapped in try/catch to handle potential auth failures gracefully

Suggested change

	const accessToken = await slackOAuth.authorize(); // PKCE flow
	try {
	const accessToken = await slackOAuth.authorize(); // PKCE flow
	} catch (error) {
	showFailureToast(error, { title: "Could not authorize with Slack" });
	throw error;
	}

[greptile-apps]

logic: API call not wrapped in try-catch block. Could fail silently if API errors occur.

Suggested change

	async function callOpenAIChatCompletion(messages, model = defaultModel) {
	const res = await openai.chat.completions.create({
	model,
	temperature: 0.2,
	messages,
	});
	return res.choices?.[0]?.message?.content?.trim() || "[No summary]";
	}
	async function callOpenAIChatCompletion(messages, model = defaultModel) {
	try {
	const res = await openai.chat.completions.create({
	model,
	temperature: 0.2,
	messages,
	});
	return res.choices?.[0]?.message?.content?.trim() || "[No summary]";
	} catch (error) {
	showFailureToast(error, { title: "Could not get OpenAI completion" });
	return "[Error getting summary]";
	}
	}

[greptile-apps]

logic: Using a global mutable userMap could cause race conditions if multiple summarizations run concurrently. Consider making this scoped to each summarization request.

[greptile-apps]

style: Verify that days is a positive number to avoid invalid timestamp calculations

Suggested change

	const oldestTs = Math.floor(Date.now() / 1000) - days * 24 * 60 * 60;
	const result = await getThreadsForChannel(channelId, oldestTs);
	if (days <= 0) throw new Error("Days must be a positive number");
	const oldestTs = Math.floor(Date.now() / 1000) - days * 24 * 60 * 60;
	const result = await getThreadsForChannel(channelId, oldestTs);