Skip to content

Conversation

Copy link

Copilot AI commented Oct 2, 2025

  • Analyze repository structure and problem statement
  • Clarify tree structure requirements with user
  • Understand what "learning component" means for each category
  • Determine which categories to include
  • Create folder structure for categories
  • Add learning documentation for each category
  • Update README with tree structure

Clarification Questions:

  1. What specific tree structure should be added to the README? Should it organize LeetCode problems by:

    • Topic/Category (Arrays, Strings, Trees, Graphs, Dynamic Programming, etc.)?
    • Difficulty (Easy, Medium, Hard)?
    • Data Structure type?
    • Algorithm pattern?
  2. What should the "learning component" include for each category? For example:

    • Overview of the category/topic?
    • Common patterns and techniques?
    • Tips and tricks for solving problems in that category?
    • Example problems and their solutions?
    • Resources for learning?
  3. You mentioned "create a pr for each folder" - should I:

    • Create separate folders for each category in this PR?
    • Just document the structure in this PR (since I can only work on one PR at a time)?
  4. Should the learning components be:

    • Markdown files in each category folder?
    • Part of the README?
    • Separate documentation files?

Please provide guidance on the desired structure and content.

Original prompt

following the tree in the readme, create a pr for each folder.
focus on the learning component of each category. ask follow up questions if you need any addditional info


✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

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.

2 participants