🤯 OMG — Oh My GitHub

🚀 One Prompt In. A Full Game or App Out. 🚀

╔══════════════════════════════════════════════════════════════╗
║  DESCRIBE IT  →  BUILD IT  →  TEST IT  →  PLAY IT           ║
║                                                              ║
║  One GitHub issue. One prompt. A complete project.           ║
╚══════════════════════════════════════════════════════════════╝

No API keys to configure. No server to maintain. No local setup maze.

---

🤯 What Is OMG?

Your GitHub issue becomes the product brief.

OMG (Oh My GitHub) is an automated GitHub Actions workflow for creating complete browser games and app projects from one natural-language prompt.

Write what you want in an issue and add the OpenCode label. OpenCode checks out the project, uses the shared skills, builds the experience, runs tests, verifies the result, and publishes an immutable OmGithub project link from the finished commit.

Yes, it creates the code. Yes, it runs the verification loop. Yes, it can expose the result in a temporary browser URL.

🧠 TL;DR

1. Open a GitHub issue.
2. Describe the game or app you want.
3. Add the OpenCode label to the issue.
4. Let GitHub Actions build, test, verify, and propose the result.

Your idea → GitHub issue → OpenCode → tests → immutable OmGithub project

⚡ Quick Start

Create an issue in your repository with a concrete request:

Build a neon asteroid game.

Requirements:
- Arrow-key movement
- Score and restart button
- Win and lose states
- Responsive browser layout
- Run tests and verify it in a browser

That is the whole user-facing workflow. GitHub Actions handles the runner, OpenCode handles implementation, and the workflow handles verification plus the immutable project commit.

To run against an existing non-default branch, end the issue title with a branch: <name> directive. The directive selects the checkout and is removed before the issue body is sent to OpenCode:

gh issue create \
  --repo AgentsLoop/OhMyGithub \
  --title "Custom branch smoke test branch: codex/omgithub-site" \
  --body "Build a tiny browser page." \
  --label Goal \
  --label OpenCode

The GitHub App validates the branch before dispatching. If the directive is absent, the repository default branch remains the target.

🌍 What Can You Build?

🎯 Use case	✨ Example
🎮 Arcade games	Breakout, Space Invaders, Asteroids, Match-3
🧩 Puzzle games	Word games, logic puzzles, card games
🏃 Interactive demos	Physics experiments, simulations, visual toys
📊 Dashboards	Filters, charts, status panels, analytics views
🛠️ Internal tools	Trackers, generators, small workflow apps
🌐 Landing pages	Product pages, portfolios, interactive showcases
🧪 Prototypes	Turn a product idea into a runnable proof of concept
📱 Browser apps	Responsive tools that work on desktop and mobile

🧰 What Happens Automatically?

The workflow is the product.

• 📥 Checks out your repository and the shared OpenCode skills.
• 🏷️ Synchronizes model/* and skill/* labels.
• 🧭 Reads issue labels to select the model and requested skills.
• 🤖 Runs OpenCode against the current project.
• 🧪 Runs a second verification prompt after implementation.
• 🌐 Starts the app and checks the local runtime.
• 🔗 Creates a temporary public preview URL when verification passes.
• 🔀 Creates and pushes an opencode/<run-id> branch.
• 🕹️ Adds an Open Project link backed by the repository path, with full-commit links retained for compatibility.
• 💬 Posts progress and access details back to the issue.
• 🧹 Cleans up temporary tunnels and runner processes.

🏷️ Model and Skill Labels

Labels let you control the workflow without editing YAML.

model/opencode/muse-spark-1.3-contributor-free
skill/load-sketchfab-threejs
skill/gauntlet-loop

The workflow validates the selected labels, passes them into OpenCode, and records the resolved model and skills in the run logs. Shared skills are discovered from:

.agents/skills/<skill-name>/SKILL.md

🔄 OpenCode Workflow

flowchart TD
    A[Trigger] --> B[Prepare project]
    B --> C[Run build.md]
    C --> D[Run verify.md]
    D --> E{Public app works?}

    E -- No --> F[Run public-app-fix.md]
    F --> E

    E -- Yes --> G[Run completion-report.md]
    G --> H{Screenshots exist?}

    H -- No --> I[Run screenshot-evidence.md]
    I --> H

    H -- Yes --> J[Commit and push]
    J --> K[Create immutable project link]
    K --> L[Publish report]
    L --> M[Complete]

Loading

🏗️ Architecture

┌──────────────┐     ┌─────────────────┐     ┌──────────────┐
│ GitHub issue │ ──▶ │ GitHub Actions  │ ──▶ │   OpenCode   │
│ + issue text │     │ runner + labels │     │ + .agents    │
└──────────────┘     └─────────────────┘     └──────┬───────┘
                                                    │
                              ┌─────────────────────┼─────────────────────┐
                              ▼                     ▼                     ▼
                         Build code           Run tests             Verify app
                              │                     │                     │
                              └─────────────────────┼─────────────────────┘
                                                    ▼
                                      ┌────────────────────────┐
                                      │ Commit store + preview │
                                      └────────────────────────┘

🔐 Security and Access

• 🔑 You do not need to create or store a project-specific AI API key.
• 🖥️ You do not need to operate a dedicated build server.
• ☁️ Execution happens in GitHub Actions.
• 🔒 Temporary SSH and preview access exists only for the workflow run.
• 👀 Review the generated commit before integrating it.
• 🛡️ Restrict who can apply the OpenCode label in repositories that accept public issues.

“No servers needed” means no servers for you to provision or maintain. The workflow still uses GitHub-hosted Actions infrastructure and temporary workflow services.

📁 Project Structure

📦 OMG
 ├─ .github/workflows/opencode.yml  # 🤖 Main issue-to-project workflow
 ├─ wiki/opencode.md                # 📖 Workflow and session notes
 ├─ wiki/testing.md                 # 🧪 Verification guidance
 └─ AGENTS.md                       # 🧭 Repository instructions

🧪 Local Validation

Validate the workflow definition before pushing changes:

actionlint .github/workflows/opencode.yml
git diff --check

🐛 Troubleshooting

Problem	What to check
The workflow did not start	Confirm the OpenCode label is applied to the issue.
A skill was not selected	Add a matching skill/<name> label.
The app URL is missing	Check the local app verification step and runner log.
The PR was not created	Confirm OpenCode produced a diff and the workflow reached the PR step.
The workflow ran unexpectedly	Tighten the trigger condition and trusted-user policy.

🤝 Contributing

Ideas, skills, game templates, verification improvements, and workflow fixes are welcome.

1. Open an issue describing the improvement.
2. Add the OpenCode label when you want the workflow to prototype it.
3. Review the generated commit and Open Project page carefully.
4. Add tests and runtime proof for workflow changes.

⭐ The Pitch

The old workflow was: idea → tickets → scaffolding → setup → implementation → debugging → deployment.

The OMG workflow is: idea → issue → playable project.

If you believe software should start with a sentence instead of a sprint plan, ⭐ star the repository and try it.

Built with GitHub Actions, OpenCode, shared skills, and unreasonable optimism. 😏