thefrederiksen/devthrottle
Grade a repo

73

/ 100

GradeC

Solid engineering. The biggest lever is test coverage.

Top 45% of 5,156 graded repos

The orchestration tool for command-line coding agents

Documentation80
Engineering57
Health92
C#110MIT2d ago

Top fixes

Highest-impact changes first, ranked by point weight

15 to address
  1. 1
    Tests18pt

    Set scripts.test in package.json to your actual test command, e.g. "vitest" or "jest".

  2. 2
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  3. 3
    CI/CD14pt

    Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.

  4. 4
    Install and run instructions9pt

    Add a section showing how to start or use the project.

Working through the fixes? Let every push regrade itself.

The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

80

Install and run instructions9pt45

README documents how to install the project.

Contributing guide5pt70

Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

README12pt100

README is present.

License6pt100

Licensed under MIT.

Engineering

57

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.

Tests18pt35

Test files detected (apps/cc-assistant/src/assistant/echoGuard.test.ts).

Reproducibility6pt80

Lockfile present (package-lock.json). Installs are reproducible.

CI/CD14pt85

CI is configured (.github/workflows/ci.yml).

Linting and formatting5pt100

Linter or formatter configured (eslint.config.js).

Project health

92

Dependency manifest6pt75

Dependency manifest found (cc-director.sln).

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)
  • 12
    Forks
  • 184
    Releaseslatest 5mo ago

Community

  • 71% - Fair
    Community health
  • -
    authors own >50% of commits
  • 110
    Watchers

Responsiveness

  • 33d 21h
    Median issue response
  • <1h
    Median PR merge time
  • 442
    Open issues
Repository files57 root entries
  • .brief
  • .claude
  • .claude-plugin
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
  • apps
    Good: Test files detected (apps/cc-assistant/src/assistant/echoGuard.test.ts).
  • docs
  • mission
  • missions
  • packages
  • phone
  • plugins
  • research
  • scripts
  • src
  • tools
  • _setup.bat
  • .dockerignore
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitleaks.toml
  • .nvmrc
  • ARCHITECT-HANDOVER.md
  • cc-director.sln
    Good: Dependency manifest found (cc-director.sln).
  • CLAUDE.md
  • CONTRIBUTING.md
    Issue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    Good: Contributing guide includes setup/install instructions.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Good: Contributing guide includes code examples.
  • DESIGN-2818.md
  • Directory.Build.props
  • Directory.Build.rsp
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • eslint.config.js
    Good: Linter or formatter configured (eslint.config.js).
  • global.json
  • INSPECTION-3-7.md
  • INSPECTION-3-FIX-REPORT.md
  • LICENSE
    Good: Licensed under MIT.
  • MISSION-PLAN.md
  • MISSION.md
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
  • PHASE-1B-REPORT.md
  • PHASE-2-REPORT.md
  • PHASE-2B-REPORT.md
  • PHASE-3-REPORT.md
  • PHASE-4-MACOS-REPORT.md
  • PHASE-4-REPORT.md
  • PHASE-5-REPORT.md
  • PHASE-6-REPORT.md
  • PROOF.md
  • QA-REPORT-DRAFT.md
  • QA-REPORT-REQUIREMENTS.md
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    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.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • release.bat
  • REVIEW-2768-round2.md
  • REVIEW-2768.md
  • REVIEW-2818-code.md
  • REVIEW-2818-design.md
  • SECURITY.md
    Good: Security policy present.
  • SPEC.md
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/thefrederiksen/devthrottle)](https://www.repo-grade.com/report/thefrederiksen/devthrottle)

More graded C# repos