Document 7 GitHub issues for codebase cleanup

[Copilot]

Created comprehensive documentation for systematic cleanup of repository structure, addressing duplicate scripts, unclear content organization, missing files, and outdated references.

Files Added

• ISSUES_TO_CREATE.md (1,581 lines) - 7 detailed issues ready to copy to GitHub:

  1. Consolidate duplicate build_book.sh scripts (2 conflicting implementations)
  2. Evaluate Content/ folder purpose (368KB, unclear relationship to book-src)
  3. Decide on week directory structure (30 files deleted, no replacement strategy)
  4. Address 9 empty/placeholder report files (0 bytes or minimal content)
  5. Update documentation references (broken links to deleted structure)
  6. Enhance SUMMARY.md generation (minimal TOC, poor navigation)
  7. Comprehensive audit roadmap (meta-issue for tracking)

• HOW_TO_CREATE_ISSUES.md - Manual and automated creation methods

• CLEANUP_SUMMARY.md - Executive overview with dependencies

• README_ISSUES.md - Quick reference with priority matrix

• .github/ISSUE_TEMPLATE.md - Reusable template

Issue Structure

Each issue contains:

• Current state analysis with file references
• Impact assessment
• Multiple solution options (pros/cons)
• File checklists
• Definition of done
• Cross-references

Total effort estimate: 20-31 hours

Creation Order

1. Build scripts (quick win, unblocks #5)
2. Content folder (strategic decision for #3, #6)
3. Week directories (depends on #2)
4. Report files (parallel work)
5. Documentation (depends on #1-3)
6. SUMMARY.md (depends on #2, #3, #4)
7. Audit epic (tracks all)

Usage

# Manual: Copy from ISSUES_TO_CREATE.md to GitHub Issues
# Automated: Use script in HOW_TO_CREATE_ISSUES.md
./create_issues.sh  # Creates all 7 issues with labels

Note: Issues designed to be created sequentially due to dependencies. Each is self-contained with full context.

Original prompt

create the issues one at a time

[Chronological Review: The conversation began with the user requesting a review of a 30-day syllabus and updates to bash files. The user then asked for a detailed updated layout of the project. Following that, the user attempted to run a script (`build_book.sh`) which resulted in multiple errors due to missing files. The user inquired about the usage of a content folder and requested a full review of the codebase to identify unnecessary files. The conversation progressed with the user asking to create detailed issues on GitHub, and finally, the user requested to create issues one at a time.]

[Intent Mapping:

1. "review the 30 day syllabus and update the bash files accordingly" - User wants to ensure the bash files reflect the syllabus.
2. "create a detailed updated layout of the project" - User seeks an organized overview of the project structure.
3. "is the content folder used?" - User is checking the relevance of a specific folder.
4. "to a full review of the code base, and flag and identify files no longer needed" - User wants to clean up the codebase.
5. "create the issues on github, providing extrema details" - User wants to document issues in detail on GitHub.
6. "create the issues one at a time" - User prefers a step-by-step approach to issue creation.]

[Technical Inventory:

• Bash scripts: build_book.sh for building project documentation.
• Markdown files: Various reports and curriculum files referenced in the copy commands.
• GitHub: User intends to create issues for project management.]

[Code Archaeology:

• build_book.sh: Script that failed to copy several files due to missing paths.
• Files mentioned in the copy command: main_curriculum.md, ab_test_analysis.md, etc., which are crucial for project documentation.]

[Progress Assessment:

• Completed Tasks: User has attempted to run the build script and has made requests for project organization.
• Partially Complete Work: The review of the syllabus and bash files is pending, as well as the creation of GitHub issues.]

[Context Validation: All user requests and commands are captured, ensuring continuity in the project management and codebase review.]

[Recent Commands Analysis:

• Last Agent Commands: User executed chmod +x ./scripts/build_book.sh and ./scripts/build_book.sh.
• Tool Results Summary: The script execution failed with multiple "cannot stat" errors indicating missing files.
• Pre-Summary State: The agent was actively working on executing the build script when the token budget was exceeded.
• Operation Context: The user was trying to build project documentation, which is a critical part of project management and organization.]

1. Conversation Overview: - Primary Objectives: - "review the 30 day syllabus and update the bash files accordingly" - "create a detailed updated layout of the project" - "is the content folder used?" - "to a full review of the code base, and flag and identify files no longer needed" - "create the issues on github, providing extrema details" - "create the issues one at a time" - Session Context: The conversation has focused on reviewing and updating project documentation, managing the codebase, and creating detailed issues on GitHub. - User Intent Evolution: The user started with requests for updates and reviews, then moved towards issue creation and project organization.

2. Technical Foundation:

• Bash Script: build_book.sh - Used for building project documentation.
• Markdown Files: Various reports and curriculum files referenced in the script.

3. Codebase Status:

• build_book.sh:
  • Purpose: Automates the building of project documentation.
  • Current State: Failed to execute due to missing files.
  • Key Code Segments: Copy commands that reference several important Markdown files.
  • Dependencies: Relies on the existence of specific curriculum and report files.

4. Problem Resolution:

• Issues Encountered: Multiple "cannot stat" errors indicating missing files during the execution of the build script.
• Solutions Implemented: None yet; the user is in the process of identifying and resolving these issues.
• Debugging Context: The user is assessing the relevance of folders and files in the project.
• Lessons Learned: The importance of verifying file paths before executing scripts.

5. Progress Tracking:

• Completed Tasks: User has attempted to run the build script.
• Partially Complete Work: Review of the syllabus and bash files, and the creation of GitHub issues is pending.

6. Active Work State:

• Current Focus: The user was working on executing the build script and addressing the resulting errors.
• Recent Context: The user has been troubleshooting the build process and assessing the project structure.
• Working Code: The build_book.sh script was the focus of recent discussions.
• Immediate Context: The user was trying to build documentation when the token budget was exceeded.

7. Recent Operations:
   ...

Created from VS Code via the GitHub Pull Request extension.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.