Adding Leetcode and /eightball responses

[mbti0n]

Why

Adding new prompts to TK's daily Leetcode reminders and /eightball responses.

What

Added new prompts inside the 2 arrays DAILY_MESSAGES (5 new prompts) and EIGHTBALL_RESPONSES (11 new responses) of forge/apps/tk/src/consts/index.ts.

Test Plan

Since the prompts of daily Leetcode reminders and /eightball responses are randomized (and I failed to set up the appropriate environment to start TK on my end), I want to have the bot tested in the Knight Hacks Discord server.

Checklist

• No schema changes.
• No environment variables changed.

Summary by CodeRabbit

• New Features
  • Added more daily message variations to keep prompts feeling fresh.
  • Expanded the eight-ball response list with additional playful, “yes/no” style options and themed one-liners.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: CHILL

Plan: Pro

Run ID: 6dc6fc3c-a847-4ffd-a02e-4c8ec2e83f2f

📥 Commits

Reviewing files that changed from the base of the PR and between 2d0602e and 6f0aeba.

📒 Files selected for processing (1)

• apps/tk/src/consts/index.ts

✅ Files skipped from review due to trivial changes (1)

• apps/tk/src/consts/index.ts

---

📝 Walkthrough

Walkthrough

apps/tk/src/consts/index.ts extends DAILY_MESSAGES with seven strings and EIGHTBALL_RESPONSES with additional response strings.

Changes

Bot Message Constants Update

Layer / File(s)	Summary
New daily and eightball message strings apps/tk/src/consts/index.ts	Seven new prompt strings are inserted into DAILY_MESSAGES, and additional response strings are appended to EIGHTBALL_RESPONSES.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Suggested labels: T.K, Feature, Minor

🚥 Pre-merge checks | ✅ 7 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title matches the change, but it does not start with an issue number in brackets as required.	Prefix it with an issue key, e.g. "[#123] Add Leetcode and /eightball responses", and keep the description concise.

✅ Passed checks (7 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
No Hardcoded Secrets	✅ Passed	Scanned the changed file and repo for key/token/password-like string literals; no hardcoded secrets were present.
Validated Env Access	✅ Passed	The PR only edits apps/tk/src/consts/index.ts constants; no raw process.env usage appears in the touched file.
No Typescript Escape Hatches	✅ Passed	Touched file only adds string literals; scans found no any, @ts-ignore/@ts-expect-error, or non-null assertions.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@apps/tk/src/consts/index.ts`:
- Around line 19-23: The LeetCode reminder is still using a separate
DAILY_MESSAGES list instead of the shared constants, so the new strings in the
shared export are never picked up. Update the LeetCode cron logic in leetcode.ts
to import and use the shared daily-message export from consts/index.ts, and
remove the duplicate DAILY_MESSAGES definition so there is a single source of
truth.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: CHILL

Plan: Pro

Run ID: efb1a21b-782b-4920-b378-3de2e1152f32

📥 Commits

Reviewing files that changed from the base of the PR and between e43730e and 2d0602e.

📒 Files selected for processing (1)

• apps/tk/src/consts/index.ts

[coderabbitai]

🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf '\n== apps/tk/src/consts/index.ts ==\n'
wc -l apps/tk/src/consts/index.ts
sed -n '1,240p' apps/tk/src/consts/index.ts

printf '\n== apps/cron/src/crons/leetcode.ts ==\n'
wc -l apps/cron/src/crons/leetcode.ts
sed -n '1,240p' apps/cron/src/crons/leetcode.ts

printf '\n== Search DAILY_MESSAGES / EIGHTBALL_RESPONSES usage ==\n'
rg -n "DAILY_MESSAGES|EIGHTBALL_RESPONSES" apps -g '!**/node_modules/**'

Repository: KnightHacks/forge

Length of output: 11275

---

Use the shared daily-message list

apps/cron/src/crons/leetcode.ts still has its own DAILY_MESSAGES, so these new strings in apps/tk/src/consts/index.ts never reach the LeetCode reminder. Move the cron to the shared export (or remove the duplicate) so there’s one source of truth.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@apps/tk/src/consts/index.ts` around lines 19 - 23, The LeetCode reminder is
still using a separate DAILY_MESSAGES list instead of the shared constants, so
the new strings in the shared export are never picked up. Update the LeetCode
cron logic in leetcode.ts to import and use the shared daily-message export from
consts/index.ts, and remove the duplicate DAILY_MESSAGES definition so there is
a single source of truth.

[DVidal1205]

lgtm lol

blah blah