kevinpbuckley/vibeue

0

/ 100

Documentation74
Engineering38
Health100
C++350MIT1d ago
Grade a repo

Popular for its size, but the engineering basics lag behind the interest.

Unreal Engine Vibe Coding tool

Documentation

74

Contributing guide5pt0

No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).

→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.

README12pt80

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

38

CI/CD14pt0

No CI configuration detected in this repository.

→ If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.

Linting and formatting5pt0

No linter or formatter config found.

→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.

Issue and PR templates6pt0

No issue or PR templates found (−100 pts).

→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.

Reproducibility6pt70

Lockfile present (Source/VibeUE/Tests/MapBlockout/reference/requirements.txt). Installs are reproducible.

Tests18pt80

Test files detected (Source/VibeUE/Tests).

Project health

100

Dependency manifest6pt100

Dependency manifest found (Source/VibeUE/Tests/MapBlockout/reference/requirements.txt).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 80
    Forks
  • 0
    Releases

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 350
    Watchers

Responsiveness

  • 23h
    Median issue response
  • <1h
    Median PR merge time
  • 18
    Open issues
Repository files17 root entries
  • .github
  • Config
  • Content
  • docs
  • Resources
  • Source
    Good: Test files detected (Source/VibeUE/Tests).
    Good: Lockfile present (Source/VibeUE/Tests/MapBlockout/reference/requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (Source/VibeUE/Tests/MapBlockout/reference/requirements.txt).
  • test_prompts
  • .gitignore
    Good: .gitignore present.
  • BuildAndLaunchGame.ps1
  • BuildPlugin.bat
  • FAB_Tech_Details.md
  • FAB-Checklist.md
  • FAB-DESCRIPTION.md
  • LICENSE
    Good: Licensed under MIT.
  • MakePlugin.ps1
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • VibeUE.uplugin