bdfinst/agentic-dev-team
Grade a repo

75

/ 100

GradeC

Good shape overall. A few tweaks would push it into the top tier.

Top 39% of 5,156 graded repos
Documentation84
Engineering67
Health78
Shell213MIT1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

16 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  2. 2
    CI/CD14pt

    Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  3. 3
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  4. 4
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

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

84

README12pt70

README is present.

Contributing guide5pt72

Contributing guide is detailed and thorough.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

67

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.

CI/CD14pt57

CI is configured (.github/workflows/plugin-tests.yml).

Tests18pt80

Test files detected (evals/codebase-recon/tests).

Reproducibility6pt92

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

Linting and formatting5pt100

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

Project health

78

Repository metadata5pt40

No repository description set on GitHub (−60 pts).

→ Add a one-line description in the repo Settings → About. It appears in search results and social previews.

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (package.json).

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • 285 / 485
    Commits (30d / 90d)
  • 27
    Forks
  • 57
    Releaseslatest 3mo ago

Community

  • 42% - Weak
    Community health
  • -
    authors own >50% of commits
  • 213
    Watchers

Responsiveness

  • 3h
    Median issue response
  • <1h
    Median PR merge time
  • 2
    Open issues
Repository files36 root entries
  • .claude
  • .claude-plugin
  • .codegraph
    Good: .gitignore present.
  • .github
    Good: CI is configured (.github/workflows/plugin-tests.yml).
  • .husky
  • .prompts
  • docs
  • evals
    Good: Test files detected (evals/codebase-recon/tests).
    Good: Environment pinned via evals/comparative/fixture-repo/services/auth-gateway/Dockerfile.
    Issue: Build artifacts or local files may be committed (evals/codebase-recon/fixtures/non-git-basic/.venv/lib) (−40 pts).Fix: Remove them and add to .gitignore.
  • memory
  • metrics
  • plans
  • plugins
  • scripts
  • tests
    Good: Dependabot is configured. Dependencies update automatically.
  • .adr-dir
  • .gitignore
  • .npmrc
  • .nvmrc
  • .release-please-manifest.json
  • CHANGELOG.md
  • CLAUDE.md
  • commitlint.config.js
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Good: Contributing guide explains how to run tests.
    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.
  • eslint.config.mjs
    Good: Linter or formatter configured (eslint.config.mjs).
  • GETTING-STARTED.md
  • init-dev-team-linux.sh
  • LICENSE
    Good: Licensed under MIT.
  • mkdocs.yml
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • 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.
    Issue: No live demo link in the README (−20 pts).Fix: Link to a deployed version, docs site, or demo video. Users want to see it running.
    Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • release-please-config.json
  • renovate.json
  • requirements-dev.txt
  • requirements-docs.txt
  • review-config.json
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/bdfinst/agentic-dev-team)](https://www.repo-grade.com/report/bdfinst/agentic-dev-team)

More graded Shell repos