marciobisognin/squads-genius
Grade a repo

59

/ 100

GradeF

Getting some notice. Tests and CI would be the fastest wins.

Higher than 43% of 5,156 graded repos
Documentation39
Engineering62
Health84
Python341mo ago

A low grade is a to-do list, not a judgment of your code

Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to C (70).

See your top fixes
Now
F
59
Potential
C
70

Top fixes

Highest-impact changes first, ranked by point weight

17 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 lint step to catch style issues automatically.

  3. 3
    CI/CD14pt

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

  4. 4
    CI/CD14pt

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

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

39

Install and run instructions9pt0

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

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.

README12pt55

README is present.

License6pt100

A license file is present.

Engineering

62

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 (IFFar-Squads/squads/farol-contratos-licitacoes-iffar/requirements.txt). Installs are reproducible.

Tests18pt80

Test files detected (IFFar-Squads/squads/farol-contratos-licitacoes-iffar/scripts/smoke_test.py).

CI/CD14pt85

CI is configured (.github/workflows/farol-iffar-ci.yml).

Project health

84

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.

Dependency manifest6pt100

Dependency manifest found (IFFar-Squads/squads/farol-contratos-licitacoes-iffar/requirements.txt).

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)
  • 15
    Forks
  • 1
    Releaseslatest 1mo ago

Community

  • 14% - Weak
    Community health
  • -
    authors own >50% of commits
  • 34
    Watchers

Responsiveness

  • -
    Median issue response
  • <1h
    Median PR merge time
  • 0
    Open issues
Repository files13 root entries
  • .claude
  • .github
    Good: CI is configured (.github/workflows/farol-iffar-ci.yml).
  • backup
  • docs
  • IFFar-Squads
    Good: A license file is present.
    Good: Test files detected (IFFar-Squads/squads/farol-contratos-licitacoes-iffar/scripts/smoke_test.py).
    Good: Lockfile present (IFFar-Squads/squads/farol-contratos-licitacoes-iffar/requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (IFFar-Squads/squads/farol-contratos-licitacoes-iffar/requirements.txt).
  • media
  • squads
    Good: Security policy present.
  • .gitignore
    Good: .gitignore present.
  • CLAUDE.md
  • 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.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    Good: README links to a live demo or deployed app.
    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.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • SELECTED_SQUADS_MANIFEST.json
  • SQUAD_INDEX.md
  • Universal_Obsidian_Knowledge_Squad_PRD_revisado.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/marciobisognin/squads-genius)](https://www.repo-grade.com/report/marciobisognin/squads-genius)

More graded Python repos