Each day (ideally) we'll attempt the daily leetcode problem. We'll make a new folder for each day's problem. Anyone who wants can submit a markdown file, iPython notebook, etc. with their notes, questions, solutions, test cases, or other problem-related files.

As of November 5, 2025, we've added an automatic solver that uses OpenAI's GPT-5-mini to generate solutions for each day's problem! Every day at 00:01 UTC, the system automatically:

• Fetches the daily LeetCode problem
• Generates a thoughtful solution with explanations
• Commits the solution as gpt5-mini.md in the problem's folder

This means you'll always find an AI-generated solution to compare with or learn from!

If you're a member of our lab and/or a Dartmouth community member, feel free to join our Slack channel to discuss daily leetcode problems!

1. Start by forking this repository. Or if you've already forked this repository, you should visit your fork and make sure to click the button to sync it up with this (source) repository.
2. In your fork, in the menu near the top click on Actions to open up the GitHub Actions list. Then click on Create New Note for Daily LeetCode Problem and then click Run workflow to create your new notes file for today's problem. Click the link to the notes on today's problem in the last row of the table above and you should see a markdown (.md) file named for your GitHub username. Edit that to add your notes!

• If you're the "build-it-yourself" type, it's also OK to create your notes file manually. Just navigate to the problems folder and click the Add file button on the right. Choose the Create new file option:
  • File name: problems/<PROBLEM NUMBER>/<your name>.md (where you should replace <PROBLEM NUMBER> with the leetcode problem ID code, and <your name> with either your first name or your GitHub username (your choice!), in lowercase letters. E.g., Jeremy's solution to problem 350 would be named problems/350/jeremy.md
  • Contents: Any format is fine, but we suggest starting with our template file. Then add your notes/solution as you solve the problem! Make sure to commit your changes (and it's fine to make multiple commits as you're working on the problem).

3. Once you've added your file(s), start a pull request to add your changes to the ContextLab repository so that others can see how you approached the problem.

The table listing each day's problems and links to our solutions should be updated automatically via this action (run each day at 00:01 UTC, which is 1 minute after the daily problems are released). Sometimes it's a little late.

You can work through problems "live" in our Slack channel. To make comments on a specific solution, make suggestions for this repository in general, etc., consider filing an issue.