How subset-ucsd/commit-challenge-2025 works
Project type and purpose
• This is a single “Commit-Challenge-2025” monorepo containing a collection of small web-based games, utilities, and bots. It’s not one cohesive full-stack app but rather a set of independent front-end static sites, real-time servers, CI-driven workflows (GitHub Actions), and hosted services (Discord bots, reminder daemons). Its overall purpose is to host “daily commit” mini-projects and automate their builds, tests, and deployments.
File structure
• Top-level directories each correspond to a sub-project:
• murder-game (TypeScript Canvas + Node server)
• qrbox (static JS game)
• escape (TypeScript CYOA)
• cave-game (WebGL client + WebSocket server + physics)
• remind (Rust Discord reminder service)
• 🍴💩 (TypeScript Discord bot RPG)
• 👑 (React puzzle)
• plus a bunch of standalone HTML/JS “toy” pages at the root.
• .github/workflows/ defines CI pipelines: compile, lint, test, nightly-release (using Gemini), auto-close (purr), etc.
• Shared configs: tsconfig.json, package.json, Cargo.toml for Rust, various README.md per project.
README for additional insights
• The README enumerates each sub-project, its URL, tech stack, and key files.
Essential architectural elements
• Don’t try to map every single tiny script—group similar static pages together.
• How code flows from developer commit to live user experience.
• Unique LLM-driven workflows in “actions game” and “release” pipelines.